Build a Skill
A Skill packages instructions and supporting files. Start with one task: when to use it, what to do, and what a good result looks like.
Declare supported platforms
To publish, extension.json must declare a non-empty supportedHosts array containing web, desktop, or both. These values identify the product host: the desktop app remains desktop even when Electron renders its interface in a browser engine. Each MCP or Skill contribution may narrow supportedHosts to a subset of the extension’s platforms; omitting it inherits the top-level declaration. Every MCP listed in a Skill’s requiresMcp must be available on every platform that Skill supports. Web and Desktop each select the latest published release compatible with their own host, so they may use different versions.
1. Download and unpack the starter
The starter contains a manifest, a README, and a writing skill. Keep this structure; do not wrap it in another folder when packaging.
extension.json
README.md
skills/
writing-guide/
SKILL.md2. Customize the manifest
Replace your-name with your intended publisher namespace and edit the name and description. Both parts of the ID must be 2–48 lowercase letters, digits, or hyphens, starting with a letter. The extension slug new is reserved.
{
"schemaVersion": 1,
"id": "your-name/writing-guide",
"version": "1.0.0",
"name": "Writing guide",
"description": "A reusable checklist for clear writing.",
"supportedHosts": [
"web",
"desktop"
],
"tags": [
"writing"
],
"license": "MIT",
"contributes": {
"mcp": [],
"skills": [
{
"id": "writing-guide",
"path": "skills/writing-guide/SKILL.md",
"requiresMcp": []
}
]
}
}3. Write the skill
SKILL.md requires YAML frontmatter. Its name must match the skill ID in the manifest; description explains when to use it. Write task steps below, with reference files inside the skill directory.
---
name: writing-guide
description: Use when the user asks to rewrite a paragraph for clarity.
---
# Clear writing
1. Identify the intended audience and main point.
2. Rewrite the supplied text using short, concrete sentences.
3. Preserve facts and meaning. Ask about ambiguous claims.
4. Return the revised text and a brief explanation of material changes.
4. Review and package
Check the trigger, inputs, outputs, and dependencies. Exclude credentials and private data. Run this command inside the folder containing extension.json, then upload for preview.
zip -r extension.zip extension.json README.md skillsLocal development: current support
The client currently installs published marketplace extensions; importing a local extension package is not yet available. Validate your service with MCP development tools and review Skill instructions and example outputs first. Website checks validate package format, not execution in PrivateBot. Do not publish an unverified extension just to debug it.