Submit a skill

Add your skill to the index so it turns up when someone searches for what it does.

OpenClawMCPClaude DesktopOpenAICursor / VS Code

What the badges mean

Our scripts set Official (the publisher is the vendor's own GitHub organisation) and Checked (the automated safety scan passed). We pick Featured and Pinned by hand. Listed and Unverified come from the index itself. None of them can be applied for.

Official

Published by the vendor's own GitHub organisation.

Featured

Hand-picked by us as a good place to start.

Pinned

Install is pinned to one commit and served from a stored snapshot.

Checked

Passed every automated safety check at a pinned commit.

Listed

Indexed from a public source. Not reviewed.

Unverified

Listed with no additional signal recorded.

No badge on this site means a person has read your code. We record provenance and run machine checks; we don't audit skills.

How to submit

Create your skill directory

Every skill is a directory with a SKILL.md at its root. That one file is readable by OpenClaw and exportable to the MCP, Claude and OpenAI formats.

my-skill/SKILL.md

---
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 returns

2
Declare platform support
The platforms field decides which install snippets your detail page offers.
SKILL.md — frontmatter metadata
```
"platforms": ["openclaw", "mcp", "claude", "openai", "cursor"]
```
Accepted values: openclaw mcp claude claudecode openai cursor codex opencode
3
Add tool implementations (optional)
If your skill ships custom tools, put the handlers in a tools/ directory next to the manifest.
my-skill/
├── SKILL.md
├── tools/
└── my_tool.js
└── README.md

Publish to GitHub

Push to a public repository and add the openclaw-skill topic so the scraper can find it.

terminal

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

5
Create a GitHub release
Tag a release with your skill as a zip artifact — the scraper reads release metadata for versioning.
terminal
```
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
```
6
Nothing — the crawler takes it from here
There is no pull request to open. A public repository carrying the openclaw-skill topic is picked up on the next crawl, usually within six hours. The repository holding the crawl sources is private, so the topic is the submission.
Still not listed a day or two later? Open a listing request with the repository URL. We read every one; we don't promise a turnaround.

Submission requirements

SKILL.md with all required fields: name, description, version
Slug format: lowercase letters, numbers and 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
A public GitHub repository holding the skill code
A licence file (MIT, Apache-2.0 or a similar OSS licence)
A platforms field naming at least one supported platform

Questions

Before you submit

How long until my skill appears?

If your repository carries the openclaw-skill GitHub topic, auto-discovery picks it up on the next crawl — usually within six hours. If it hasn't appeared after a day or two, open a listing request on GitHub with the repository URL. There is no service-level commitment on either path.

Can I submit skills for Claude Desktop, Cursor or OpenAI?

Yes. Set the platforms field in your SKILL.md to include any of openclaw, mcp, claude, claudecode, openai, cursor, codex, opencode. The detail page then shows the install snippet for each platform you declare.

Will anyone review my code?

No. TrustedSkills indexes skills and records where they came from — nobody reads the code as part of listing it. Badges describe provenance and machine checks, never a human audit.

How do I get a stronger badge?

Official is assigned automatically when the publishing account matches a vendor's own GitHub organisation. Featured is an editorial pick. Pinned means we've recorded a commit and stored a snapshot of it. None of them can be requested.

Can I update my skill?

Yes. Cut a new GitHub release with a higher version number and the scraper picks it up. If your skill is pinned, the pinned commit is updated on the next sync, not instantly.

Does my skill need to support every platform?

No — one is enough. Most start with OpenClaw or MCP and expand later.