agentleFS
Sign inStart free
HeyvhuangHeyvhuang/ship-faster/skills/skill-creator/SKILL.md

skill-creator

Skill337 starsChanged 10 months agoMITView on GitHub

Create or refactor Ship Faster-style skills (SKILL.md + references/ + scripts/). Use when adding a new skill, tightening trigger descriptions, splitting long docs into references, defining artifact-first I/O contracts, or packaging/validating 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

8 rules. 0 are common, 1 is distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 185 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    add scripts/ for deterministic steps

    line 30
  2. Very specific:

    add references/ for heavy documentation

    line 31
  3. Very specific:

    add assets/ for templates / boilerplate

    line 32
  4. Very specific:

    All scripts live in scripts/ in this skill folder.

    line 40
  5. Very specific:

    Prefer prefix naming: workflow-, tool-, review-, mcp-, skill-, publish-.

    line 74
  6. Distinctive:

    Keep side effects gated: write a plan first, ask for explicit confirmation, then execute, then verify.

    line 75
  7. Very specific:

    If you add/remove a skill, update the catalog: skills/manifest.json.

    line 76
  8. Very specific:

    Prefer creating skills going forward so you can bundle references/, scripts/, and use subagents

    line 84

“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

Build skills that behave like “mini senior engineers”: trigger correctly, run deterministically, and leave resumable artifacts on disk.

What good looks like (Ship Faster standard)

  • SKILL.md: short and triggerable (routing + safety + I/O + output contract). Avoid long tutorials here.
  • references/: deep docs loaded only when needed (progressive disclosure). Link directly from SKILL.md.
  • scripts/: deterministic helpers for repetitive/fragile work (prefer this over re-writing code in chat).
  • assets/: templates or files to copy (not meant to be loaded into context).

Deep guidance:

  • Progressive disclosure + authoring principles: references/skill-design-principles.md
  • Workflow structure patterns: workflows.md
  • Output templates/patterns: output-patterns.md

Creation flow (recommended)

  1. Collect trigger examples (real user phrases that should activate the skill).
  2. Define the I/O contract (paths only) + required artifacts:
    • What files does the skill read?
    • What files must it write (plans, evidence, summaries)?
  3. Implement reusable resources first:
    • add scripts/ for deterministic steps
    • add references/ for heavy documentation
    • add assets/ for templates / boilerplate
  4. Write SKILL.md last:
    • frontmatter description should include trigger phrases
    • body should be short and link out to the resources above
  5. Validate + package (optional) using the scripts below.

Scripts

All scripts live in scripts/ in this skill folder.

Initialize a new skill folder

python scripts/init_skill.py <skill-name> --path <output-directory>

Validate a skill (frontmatter + basic conventions)

python scripts/quick_validate.py /path/to/<skill-name>

Sync catalogs/assets (manifest, skills-map, docs catalog)

python scripts/sync_catalog.py

Lint skills (compat + quality gates)

python scripts/skill_lint.py --check-generated

Package a skill into a distributable .skill zip (optional)

python scripts/package_skill.py /path/to/<skill-name> [output-directory]

Notes for Ship Faster contributors

  • Prefer prefix naming: workflow-, tool-, review-, mcp-, skill-, publish-.
  • Keep side effects gated: write a plan first, ask for explicit confirmation, then execute, then verify.
  • If you add/remove a skill, update the catalog: skills/manifest.json.

Claude Code: Slash Commands merged into Skills

Claude Code now treats custom slash commands and skills as the same concept:

  • .claude/commands/<name>.md and .claude/skills/<name>/SKILL.md both create /<name>
  • Existing .claude/commands/ files keep working (no migration required)
  • Prefer creating skills going forward so you can bundle references/, scripts/, and use subagents

Useful frontmatter knobs (Claude Code):

  • disable-model-invocation: true - only user can invoke (good for side-effect workflows)
  • user-invocable: false - hide from users; Claude-only background knowledge
  • context: fork + agent: Explore|Plan|... - run skill in a subagent (good for research)
  • allowed-tools - restrict tool surface when this skill is active

Archived full guide

The previous (long-form) version of this skill is preserved at:

  • references/legacy-skill-creator.md

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