Skip to content
This page is not yet translated. You are viewing the English version.

Create & Publish Skills

Build your own skill and share it on the Skill Marketplace

Anyone with a Claw Buff account can create and publish skills on the Skill Marketplace.

Creating a Skill

Navigate to the Skill Marketplace and click Publish Skill, or go directly to the Skill Editor.

The Editor

The skill editor has two panels:

Left panel — SKILL.md content:

Write your skill's instructions in Markdown. This is the core of your skill — the prompt document that teaches the agent how to perform a task. You can also upload optional script files (JS/TS) for advanced behaviors.

Right panel — Metadata:

FieldRequiredDescription
NameYesDisplay name (min 2 characters)
DescriptionYesShort summary shown on the card
CategoryYesOne of: Development, Productivity, Communication, etc.
TagsNoComma-separated labels for discovery
VersionYesSemantic version (e.g., 1.0.0)

Writing a Good SKILL.md

A skill's quality depends entirely on the clarity of its instructions. Follow this structure:

---
name: my-skill
description: What this skill does in one sentence
version: 1.0.0
---

# My Skill

## Overview
Brief explanation of what the agent can do with this skill.

## Commands / Workflows
Step-by-step instructions the agent should follow.
Be specific about which tools to use and in what order.

## Examples
Show concrete input/output examples so the agent
understands the expected behavior.

## Limitations
What this skill cannot do or shouldn't attempt.

The best skills are focused and specific. A skill that does one thing well is more useful than one that tries to cover everything. Think "GitHub PR reviewer" not "general coding helper."

Saving and Publishing

You have two options:

  • Save Draft — Saves the skill without publishing. Only you can see drafts. Useful for work-in-progress skills.
  • Publish — Submits the skill for review and makes it available on the marketplace once approved.

Review Process

When you publish a skill, the following happens:

  1. Automated security scan — Script files (if any) are scanned for known malicious patterns (reverse shells, data exfiltration, credential theft).
  2. Review status — Skills with scripts that pass the scan are set to "pending review." Skills without scripts (SKILL.md only) are auto-approved.
  3. Notification — You'll be notified when your skill is approved or rejected. Rejected skills include a review note explaining why.

Skills that contain only a SKILL.md (no script files) are automatically approved since they're pure prompt documents with no executable code. Adding scripts triggers the security review pipeline.

Managing Your Skills

My Skills

Click the My Skills tab on the marketplace page to see all your skills and their statuses:

StatusMeaning
Published (green)Live on the marketplace, visible to everyone
Pending Review (amber)Submitted, awaiting approval
Rejected (red)Rejected with a review note — edit and resubmit
Unpublished (gray)Draft or manually unpublished

Editing

Click any of your skills to open it in the editor. You can update:

  • SKILL.md content
  • Metadata (name, description, category, tags)
  • Version number
  • Script files

Changes to published skills take effect immediately after saving.

Unpublishing

To temporarily remove a skill from the marketplace without deleting it:

  1. Open the skill in the editor
  2. Click Unpublish in the danger zone

The skill becomes a draft. You can republish it at any time.

Deleting

To permanently delete a skill:

  1. Open the skill in the editor
  2. Click Delete in the danger zone
  3. Confirm the deletion

Deletion is permanent and cannot be undone. If users have already installed your skill, the installed copies remain on their agents, but no further updates will be available.

Best Practices

  1. Be specific in instructions. "Help the user with GitHub" is vague. "Use gh pr create to create a pull request with the staged changes" is actionable.
  2. Include examples. Show the agent what good input and output look like. This dramatically improves skill reliability.
  3. Declare dependencies. If your skill needs an API key or binary, mention it clearly in the SKILL.md frontmatter and description.
  4. Version meaningfully. Bump the version when you make changes. Users and the platform track version history.
  5. Test before publishing. Install your skill on your own agent and verify it works as expected before making it public.
  6. Write a clear description. This is what users see first. Make it concrete — what will this skill actually do for their agent?