agentleFS
Sign inStart free
YehudaFrankelYehudaFrankel/clankbrain/.claude/skills/skill-creator/SKILL.md

skill-creator

Skill16 starsChanged 7 months agoMITView on GitHub

Create a new reusable skill from scratch. Triggers on "create a skill", "new skill", "make a skill called", "add a skill for", "/skill-creator".

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

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

  • 0

    Common

    Most of the 185 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read any close matches. If a duplicate exists, report it and ask: "Update existing or create new?"

    line 28
  2. Distinctive:

    Use the Write tool

    line 65
  3. Distinctive:

    Add to CLAUDE.md skill map: if it belongs in a workflow — find the relevant row and insert it.

    line 67
  4. Distinctive:

    After creating, push via your memory sync script so the skill is available on all machines

    line 77

“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: skill-creator

Trigger: /skill-creator or "create a skill" or "make a skill called" or "add a skill for"

Description: Builds a new SKILL.md from scratch by gathering requirements, writing the step-by-step instructions, creating the file, and wiring it into the workflow map.

Steps

  1. Gather requirements — ask the user (if not already clear):
    • What is the skill called? (slug, e.g. fix-bug, new-endpoint)
    • What phrase(s) should trigger it?
    • What does it do — one sentence?
    • What are the steps? (ask for a rough description; you will formalize them)
    • Which tools does it need? (Read, Write, Edit, Bash, Grep, Glob, Agent, etc.)
  2. Check for duplicates — glob existing skills for similar names or trigger phrases:
    Glob pattern="**/SKILL.md" path=".claude/skills"
    Read any close matches. If a duplicate exists, report it and ask: "Update existing or create new?"
  3. Draft the SKILL.md using this template:
    ---
name: skill-name
description: One-line description — used for skill discovery. Include trigger phrases.
allowed-tools: Read, Edit, Write, Glob, Grep
---

# Skill: skill-name

**Trigger:** `/skill-name` or "trigger phrase A" or "trigger phrase B"

**Description:** What this skill does in one sentence.

**Allowed Tools:** Read, Edit, Write, ...

---

## Steps

1. **Step one** — what to do first
2. **Step two** — next action
3. ...

---

## Notes

- Any caveats, edge cases, or project-specific rules
  4. Show the draft to the user and ask: "Does this look right, or any changes before I write it?"
  5. Write the file once approved:
    • Path: .claude/skills/<skill-name>/SKILL.md
    • Use the Write tool
  6. Add to CLAUDE.md skill map if it belongs in a workflow — find the relevant row and insert it.
  7. Report: "Skill /<skill-name> created at .claude/skills/<skill-name>/SKILL.md. Trigger: [phrases]. Added to workflow: [yes/no]."

Notes

  • Skill slugs must be lowercase kebab-case
  • allowed-tools in frontmatter controls what the skill can use — be conservative; only list tools the steps actually need
  • After creating, push via your memory sync script so the skill is available on all machines

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.

Check your setup, free