agentleFS
Sign inStart free
tofusitotofusito/multi-agents/skills/skill-creator/SKILL.md

skill-creator

Skill0 starsChanged 6 months agoMITView on GitHub

Create or update skills (SKILL.md files) with correct frontmatter, naming rules, and well-structured content for OpenCode and Claude Code.

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use a skill when:

    line 15
  2. Distinctive:

    Use an agent instead when:

    line 21
  3. Distinctive:

    Must match the directory name exactly

    line 55
  4. Very specific:

    Write frontmatter: name, description, compatibility, version, optional metadata.

    line 94
  5. Distinctive:

    Write the body. Lead with "What I do" and "When to use me".

    line 95
  6. Very specific:

    Place at skills/<name>/SKILL.md.

    line 96

“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

What is a skill

A skill is a reusable instruction set that an agent loads on demand. Unlike agents, skills have no model, permissions, or lifecycle — they are pure content injected into the active agent's context when called.

Use a skill when:

  • The behavior is reusable across multiple agents.
  • The instructions are too long or specific to live in the agent prompt.
  • The content should only be loaded when relevant, not on every message.
  • You want to share domain knowledge without creating a full agent.

Use an agent instead when:

  • The task requires a different model, temperature, or permission set.
  • The behavior needs to run independently with its own tool access.

File placement

One folder per skill, one SKILL.md inside it. Folder name must match the name field in frontmatter.

ScopePath
Global (all projects)~/.config/opencode/skills/<name>/SKILL.md
Project-local.opencode/skills/<name>/SKILL.md

In this repo, skills live at skills/<name>/SKILL.md and are synced by distribute.sh.

Frontmatter spec

---
name: my-skill-name          # required — must match directory name
description: One sentence.   # required — 1-1024 chars, specific enough for discovery
compatibility: opencode
version: "1.0.0"
metadata:
  audience: workers
  workflow: release
---

Naming rules

  • 1–64 characters
  • Lowercase alphanumeric with single hyphen separators only
  • No --, no leading/trailing -
  • Must match the directory name exactly

Valid: git-workflow, code-review, claude-api Invalid: Git-Workflow, code--review, -starts-dash

Description rules

  • 1–1024 characters
  • Specific enough for the agent to choose the right skill
  • One-sentence action statement: what the skill does and when to use it

Good: Create consistent release notes from merged PRs following the team versioning scheme. Bad: Helps with releases.

Body content

Free-form Markdown. Structure it so the loading agent can act immediately.

Recommended sections:

## What I do
Bullet list of concrete actions this skill enables.

## When to use me
Conditions that should cause an agent to load this skill.

## Workflow / Steps
Numbered steps if the skill describes a process.

## Templates
Paste-ready templates.

## Rules
Non-negotiable rules when this skill is active.

Creation workflow

  1. Confirm the skill name is valid (lowercase, no consecutive hyphens, matches directory).
  2. Write frontmatter: name, description, compatibility, version, optional metadata.
  3. Write the body. Lead with "What I do" and "When to use me".
  4. Place at skills/<name>/SKILL.md. distribute.sh will sync it.
  5. Tell the user how to verify it loaded.

Review checklist

Before finishing, verify:

  • Directory name matches name frontmatter exactly.
  • name is lowercase alphanumeric with single hyphens only.
  • description is specific, actionable, and ≤ 1024 characters.
  • Body leads with what the skill does and when to use it.
  • No secrets, credentials, or environment-specific values are hardcoded.
  • File is spelled SKILL.md (all caps).
  • File is at skills/<name>/SKILL.md, not inside opencode/ or agents/.

Download now (ZIP)

  • Other versions188 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 188

    1. moltbot/moltbot★ 394ksame name
    2. clawdbot/clawdbot★ 394ksame name
    3. steipete/clawdis★ 394ksame name
    4. openclaw/openclaw★ 394ksame name
    5. steipete/warelay★ 392ksame name
    6. moltbot/clawdbot★ 392ksame name
    7. molt-bot/clawdbot★ 391ksame name
    8. anthropics/skills★ 186ksame name
    9. openai/codex★ 133ksame name
    10. google-gemini/gemini-cli★ 109ksame name

    178 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use taskflow-inbox-triage, community-led-growth and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • AtomicBot-aiSkill

      taskflow-inbox-triage

      Also in 5 projects that use this

    • nicepkgSkill

      community-led-growth

      Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

      Also in 5 projects that use this

    • nicepkgSkill

      ph-community-outreach

      Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

      Also in 5 projects that use this

    • seedprodSkill

      session-logs

      Search and analyze your own session logs (older/parent conversations) using jq.

      Also in 18 projects that use this

    • AnthropicSkill

      academy-guide

      Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

      Also in 5 projects that use this

    • ArogyaReddySkill

      skill-share

      A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

      Also in 23 projects that use this

    • +3 more from nicepkg
  • In this repository7 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free