agentleFS
stacklokstacklok/toolhive-studio/.cursor/skills/skill-creator/SKILL.md

skill-creator

Skill173 starsChanged 5 months agoApache-2.0View on GitHub

Create new AI agent skills for Claude Code, Codex, and Cursor. Use when asked to create a skill, add a new agent capability, or set up a slash command.

190 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, mermaid-diagram-generator 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 6 projects that use this

  • shalombSkill

    mermaid-diagram-generator

    Guide on creating and editing Mermaid charts safely. Use when asked to draw a diagram, flowchart, or architecture chart. Triggers on: 'mermaid', 'diagram', 'flowchart', 'visualize'.

    Also in 5 projects that use this

  • naman10parikhSkill

    ecosystem-reference

    Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.

    Also in 5 projects that use this

  • naman10parikhSkill

    fractal-delegation

    Also in 5 projects that use this

  • Liang-MHSkill

    stock_analysis

    获取 A 股、基金和港股的实时行情和技术分析数据

    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

  • +6 more from naman10parikh

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 6 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 185 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create AI agent skills that work across Claude Code, Codex, and Cursor.

    line 8
  2. Very specific:

    Claude is canonical: - Always create/edit in .claude/skills/<name>/ first

    line 12
  3. Very specific:

    Format differences: - Use sed only if agent-specific tweaks are needed (rare)

    line 14
  4. Very specific:

    context: fork: Run in isolated subagent context

    line 52
  5. Distinctive:

    Ask the user what the skill should do

    line 56
  6. Distinctive:

    Create the Claude skill:

    line 58
  7. Very specific:

    Write .claude/skills/<name>/SKILL.md with proper frontmatter

    line 62
  8. Distinctive:

    Keep skills focused on a single capability

    line 80
  9. Distinctive:

    Write clear descriptions with keywords for auto-discovery

    line 81
  10. Very specific:

    Use references/ for lengthy documentation to keep SKILL.md concise

    line 82
  11. Distinctive:

    Test the skill by asking the agent to perform the task

    line 83

“Common” is measured: kept by at least 6 in 10 of the 185 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

Skill Creator

Create AI agent skills that work across Claude Code, Codex, and Cursor.

Workflow

  1. Claude is canonical - Always create/edit in .claude/skills/<name>/ first
  2. Replicate with CLI - Copy to .codex/skills/ and .cursor/skills/ using cp -r
  3. Format differences - Use sed only if agent-specific tweaks are needed (rare)

Directory Structure

.claude/skills/<skill-name>/
├── SKILL.md          # Required - instructions + metadata
├── references/       # Optional - supporting documentation
├── scripts/          # Optional - executable helpers
└── assets/           # Optional - templates, resources

.codex/skills/<skill-name>/   # Copy of Claude's
.cursor/skills/<skill-name>/  # Copy of Claude's

SKILL.md Format

---
name: skill-name # Required: lowercase, hyphens, max 64 chars
description: What it does... # Required: triggers auto-selection by agent
allowed-tools: Read, Grep, Bash # Optional: Claude-specific (ignored by others)
model: claude-opus-4-5-20251101 # Optional: Claude-specific (ignored by others)
---
# Skill Title

Instructions in markdown...

Required Fields

  • name: Lowercase with hyphens, must match directory name
  • description: Explains what the skill does and when to use it. Include keywords users would say to help the agent auto-select this skill.

Optional Fields (Claude-specific, ignored by other agents)

  • allowed-tools: Tools the agent can use without asking permission
  • model: Override the model for this skill
  • context: fork: Run in isolated subagent context

Creating a New Skill

  1. Ask the user what the skill should do
  2. Choose a descriptive name (lowercase, hyphens)
  3. Create the Claude skill:
    mkdir -p .claude/skills/<name>
  4. Write .claude/skills/<name>/SKILL.md with proper frontmatter
  5. Replicate to other agents:
    cp -r .claude/skills/<name> .codex/skills/
    cp -r .claude/skills/<name> .cursor/skills/

Modifying an Existing Skill

  1. Edit .claude/skills/<name>/SKILL.md (canonical source)
  2. Replicate changes:
    cp .claude/skills/<name>/SKILL.md .codex/skills/<name>/
    cp .claude/skills/<name>/SKILL.md .cursor/skills/<name>/

Best Practices

  • Keep skills focused on a single capability
  • Write clear descriptions with keywords for auto-discovery
  • Use references/ for lengthy documentation to keep SKILL.md concise
  • Test the skill by asking the agent to perform the task

Download now (ZIP)

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.