Submit a Skill

Share your OpenClaw skill with thousands of AI agent users.

Verification Tiers

๐Ÿ”“
Unverified
Submitted but not yet scanned or reviewed.
๐ŸŒ
Community
Passed all 6 automated security scans. Auto-assigned on merge.
โœ…
Verified
Human code review by the TrustedSkills team.
โญ
Featured
Editorially selected by the OpenClaw team.

How to Submit

1

Create your skill directory

Create a directory for your skill with a SKILL.md file. This is the core of every OpenClaw skill.

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":"๐Ÿ”ง"}}
---

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

Add tool implementations (optional)

If your skill uses custom tools, add handler files in a tools/ directory.

my-skill/
โ”œโ”€โ”€ SKILL.md
โ”œโ”€โ”€ tools/
โ””โ”€โ”€ my_tool.js
โ””โ”€โ”€ README.md
3

Publish to GitHub

Push your skill to a public GitHub repository and add the openclaw-skill topic tag so it's auto-discoverable.

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
4

Create a GitHub Release

Create a tagged release with your skill as a zip artifact. The scraper uses 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
5

Submit a PR to the registry

Open a pull request to add your skill to the sources.json file in the TrustedSkills registry repository.

Add to sources.json:
{
  "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)

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 other platforms (Claude, OpenAI)?

Yes! Set the platforms field in your SKILL.md to include mcp, openai, claude, or huggingface. Multi-platform skills get wider exposure.

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.