Submit a Skill
Share your AI agent skill with developers across the entire ecosystem.
Verification Tiers
How to Submit
Create your skill directory
Create a directory for your skill with a SKILL.md file. This is the core of every TrustedSkills skill โ readable by OpenClaw, and exportable to MCP, Claude, and OpenAI formats.
---
name: my-skill-name
description: "One-line description of what your skill does (10-500 chars)"
version: 1.0.0
metadata: {"openclaw":{"emoji":"๐ง"},"platforms":["openclaw","mcp"]}
---
## Instructions
Describe how the agent should use this skill. This text is injected
into the system prompt when the skill is active.
## Tools
### `my_tool_name`
What this tool does.
**Parameters:**
- `param1` (string, required): Description of the parameter
**Returns:** What the tool returnsDeclare platform support
Set the platforms field to list which AI platforms your skill supports. Skills that support multiple platforms get wider exposure.
Supported values: openclaw mcp claude openai cursor huggingface
Add tool implementations (optional)
If your skill uses custom tools, add handler files in a tools/ directory.
Publish to GitHub
Push your skill to a public GitHub repository and add the openclaw-skill topic tag so it's auto-discoverable.
git init my-skill && cd my-skill git add . git commit -m "Initial skill" gh repo create my-skill --public --push gh repo edit --add-topic openclaw-skill
Create a GitHub Release
Create a tagged release with your skill as a zip artifact. The scraper uses release metadata for versioning.
git tag v1.0.0 git push origin v1.0.0 gh release create v1.0.0 \ --title "v1.0.0" \ --notes "Initial release" \ my-skill.zip
Submit a PR to the registry
Open a pull request to add your skill to the sources.json file in the TrustedSkills registry repository.
{
"type": "github_repo",
"repo": "yourusername/my-skill",
"skills_path": ".",
"official": false
}Or wait up to 6 hours โ if your repo has the openclaw-skill topic, it will be auto-discovered by the scraper.
Submission Requirements
- โSKILL.md with all required fields: name, description, version
- โSlug format: lowercase letters, numbers, hyphens only (e.g. my-skill-name)
- โValid semantic version (e.g. 1.0.0)
- โNo hardcoded API keys or secrets in any file
- โAll tool files referenced in SKILL.md must exist
- โPublic GitHub repository with the skill code
- โLicense file (MIT, Apache-2.0, or similar OSS license)
- โplatforms field set to at least one supported platform value
FAQ
How long until my skill appears?
If you add the openclaw-skill GitHub topic, auto-discovery runs every 6 hours. Manual PR submissions are reviewed within 5 business days.
Can I submit skills for Claude Desktop, Cursor, or OpenAI?
Yes! Set the platforms field in your SKILL.md to include mcp, claude, cursor, openai, or huggingface. Multi-platform skills get wider exposure and show platform-specific install instructions on their detail page.
How do I reach Verified status?
After your skill passes automated scans and merges (Community tier), request a human review by commenting on the PR or opening a review request issue.
Can I update my skill?
Yes. Create a new GitHub Release with a higher version number. The scraper will pick it up automatically.
Does my skill need to support all platforms?
No โ you can support just one. Most skills start with OpenClaw or MCP and expand. The registry will show the right install instructions based on what you declare in the platforms field.