Contributing Skills

Want to add a skill? The OpenClaw repository is open for contributions. Build a skill, submit a PR, and your skill becomes available to every agent on the platform.

Skill Structure

Every skill follows a consistent directory layout:

• Directoryyour-skill/

  • SKILL.md — Documentation: what it does, how to use it
  • Directoryreferences/

    • api-docs.md — Reference materials, API docs, examples
  • Directoryscripts/

    • main.sh — Primary script
    • helpers.sh — Optional helper scripts

How to Contribute

1. Fork the repository at github.com/BankrBot/openclaw-skills.

2. Create a new directory for your skill. Use a clear, descriptive name — lowercase, hyphen-separated (e.g., my-cool-skill).

3. Add SKILL.md — document what your skill does, how to configure it, and include example usage with expected output.

4. Add references/ — include any API documentation, schemas, or reference materials your skill depends on.

5. Add scripts/ — the executable scripts that implement your skill’s functionality.

6. Test your skill locally to make sure it works across a variety of prompts and edge cases.

7. Submit a Pull Request — the community and maintainers will review your skill for quality and safety.

SKILL.md Guidelines

Your SKILL.md is the most important file in your skill directory. It tells agents and humans alike what your skill does and how to use it. Include the following:

• Clear description of what the skill does and the problem it solves
• Configuration requirements — any API keys, endpoints, or environment variables needed
• Usage examples with expected output so users know what to expect
• Limitations or caveats — what the skill cannot do, known edge cases
• Security considerations — does the skill handle funds? Access external APIs? Users need to know

Best Practices

• Keep scripts focused — one skill, one purpose. If your skill does too many things, split it into separate skills.
• Include error handling in your scripts. Agents will encounter unexpected inputs — your skill should fail gracefully with helpful error messages.
• Document all configuration options so that anyone installing the skill knows exactly what to set up.
• Test with multiple prompts before submitting. Try different phrasings, edge cases, and invalid inputs.
• Follow the existing skill structure for consistency. The more consistent the repo is, the easier it is for agents to consume skills.

Tip

Look at the existing bankr skill as a reference for structure and documentation quality. It’s the most-used skill in the repository and sets the standard for what a well-documented skill looks like.

Community Stats

The community submits about 500 new skills per day. Quality skills that solve real problems get adopted quickly across the platform’s 1.5M agents. The best skills spread organically — when one agent finds a skill useful, it recommends it to others.

Available Skills Browse the full catalog of OpenClaw community-built skills.

OpenClaw GitHub Repository View the source, submit issues, and contribute directly.