agentleFS
claude-worldclaude-world/claude-agent/.claude/skills/skill-creator/SKILL.md

skill-creator

Skill5 starsChanged 8 months agoMITView on GitHub

Create new Claude Code SKILL.md files from user descriptions. Generates correct frontmatter, command documentation, usage examples, and rules. Validates format and writes to .claude/skills/. Use when user says "create a skill for", "add new skill", "make a skill that", or "scaffold a skill".

189 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

12 rules. 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 185 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No external CLI needed. Uses Read, Write, Edit, Grep, and Glob tools.

    line 32
  2. Very specific:

    Every SKILL.md must follow this structure:

    line 36
  3. Very specific:

    Use Read tool on relevant examples (e.g., apple-notes/SKILL.md, github-ops/SKILL.md).

    line 96
  4. Very specific:

    Use Write tool to create .claude/skills/<skill-name>/SKILL.md.

    line 122
  5. Distinctive:

    After writing, re-read the file and verify:

    line 126
  6. Distinctive:

    Always read 2+ existing skills as format reference before generating

    line 159
  7. Distinctive:

    Never create a skill that duplicates an existing one — check first with Glob

    line 160
  8. Distinctive:

    If user provides a vague description, ask 3 clarifying questions before generating:

    line 162
  9. Distinctive:

    Should it be haiku (fast/simple) or sonnet (reasoning required)?

    line 165
  10. Distinctive:

    After writing, always re-read the file to confirm it was written correctly

    line 166
  11. Distinctive:

    If the skill requires env vars, always include a "Set up" section in Prerequisites

    line 168
  12. Distinctive:

    Keep the Rules section actionable — each rule should be a single clear directive

    line 169

“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

Generate well-structured SKILL.md files for Claude Code skills. Reads existing skills as reference, generates correct format, validates, and writes to .claude/skills/.

Prerequisites

No external CLI needed. Uses Read, Write, Edit, Grep, and Glob tools.

SKILL.md Format Reference

Every SKILL.md must follow this structure:

---
name: skill-name                    # kebab-case, matches directory name
description: >                      # Single paragraph, mentions trigger phrases
  What the skill does and when to use it.
allowed-tools:                      # Only tools actually needed
  - Bash
  - Read
  - Write
model: haiku|sonnet|opus            # haiku for simple, sonnet for complex
user-invocable: true                # Always true for user-facing skills
when_to_use: >                      # Explicit trigger phrases
  When to invoke. Triggers: "phrase 1", "phrase 2".
argument-hint: "<args>"             # CLI-style hint shown in autocomplete
---

# Title

Brief one-line description.

## Prerequisites

Install command or "No install needed."

## Commands

Key CLI commands in a table or code blocks.

## Usage Examples

Realistic examples with bash code blocks.

## Rules

- Bullet list of behavioral rules
- Check if CLI installed first
- Handle missing env vars gracefully
- Keep responses concise

Workflow

Step 1: Gather Requirements

From user input, extract:

  • Skill name: kebab-case identifier (e.g., my-skill)
  • CLI tool(s): what commands power it
  • Purpose: what task it accomplishes
  • Trigger phrases: natural language patterns that should invoke it
  • Model: haiku (simple/fast) or sonnet (complex/reasoning)

Step 2: Read Reference Skills

# Read 2-3 similar existing skills for pattern reference
ls /path/to/.claude/skills/

Use Read tool on relevant examples (e.g., apple-notes/SKILL.md, github-ops/SKILL.md).

Step 3: Check for Conflicts

# Check if skill already exists
ls .claude/skills/ | grep "<skill-name>"

Step 4: Generate SKILL.md

Generate the full SKILL.md content following the format reference above. Key rules:

  • name field must match the directory name exactly
  • description must include trigger phrases ("Use when user says...")
  • when_to_use must list explicit trigger phrases after "Triggers:"
  • allowed-tools must only include tools the skill actually uses
  • Prerequisites section must include exact install commands
  • Rules section must include: check CLI installed, handle missing env vars, keep output concise

Step 5: Create and Write

# Create the skill directory
mkdir -p .claude/skills/<skill-name>

Use Write tool to create .claude/skills/<skill-name>/SKILL.md.

Step 6: Validate

After writing, re-read the file and verify:

  • Frontmatter is valid YAML (no syntax errors)
  • name matches directory name
  • description is non-empty and mentions triggers
  • when_to_use has explicit trigger phrases
  • allowed-tools list is accurate
  • model is one of: haiku, sonnet, opus
  • argument-hint is present
  • Has all required sections: Prerequisites, Commands, Usage Examples, Rules
  • Rules include CLI-installed check and concise-output guidance

Usage Examples

Create a skill from description:

User: "create a skill for managing Docker containers — list, start, stop, exec"
→ Reads docker-related reference skills
→ Generates skill-name: docker-control
→ Creates .claude/skills/docker-control/SKILL.md
→ Validates format
→ Reports: "Created .claude/skills/docker-control/SKILL.md"

Create a skill with API key:

User: "create a skill for sending SMS via Twilio"
→ skill-name: twilio-sms
→ Includes TWILIO_ACCOUNT_SID + TWILIO_AUTH_TOKEN + TWILIO_FROM env vars
→ Creates .claude/skills/twilio-sms/SKILL.md

Rules

  • Always read 2+ existing skills as format reference before generating
  • Never create a skill that duplicates an existing one — check first with Glob
  • Skill directory name must match the name frontmatter field exactly
  • If user provides a vague description, ask 3 clarifying questions before generating:
    1. What CLI tool(s) power this skill?
    2. What are the 3 most common user requests?
    3. Should it be haiku (fast/simple) or sonnet (reasoning required)?
  • After writing, always re-read the file to confirm it was written correctly
  • Report the created file path in the final response
  • If the skill requires env vars, always include a "Set up" section in Prerequisites
  • Keep the Rules section actionable — each rule should be a single clear directive

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.