agentleFS
jajupmochijajupmochi/agent-harness/.claude/skills/new-skill/SKILL.md

new-skill

Skill1 starsChanged 4 months agoMITView on GitHub

Scaffold a new skill under skills/<bucket>/<kebab-name>/. Creates SKILL.md with proper frontmatter, plus updates INVENTORY.md and skills/README.md in the same edit batch.

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review-skill, commit and 1 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.
  • MongoDBSkill

    review-skill

    Review a proposed Agent Skill for structural validity and content quality before publishing. Runs the skill-validator CLI to check for structural issues, scores the skill with an LLM judge, and interprets results to advise SMEs on what to address. Use when a user wants to review, validate, or quality-check an Agent Skill.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 4 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 0

    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. Very specific:

    Verify skills/<bucket>/<kebab-name>/ does not already exist

    line 20
  2. Very specific:

    Verify <bucket> is one of: general/, research-pkg/, static-site/, productivity/, personal/ — or ask the user to add a new bucket if needed

    line 21

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

/new-skill

Scaffold a new skill following the Claude Code SKILL.md spec.

Usage

/new-skill <bucket>/<kebab-name>

E.g.: /new-skill general/find-duplicates or /new-skill research-pkg/new-experiment

Pre-flight

  • Verify skills/<bucket>/<kebab-name>/ does not already exist
  • Verify <bucket> is one of: general/, research-pkg/, static-site/, productivity/, personal/ — or ask the user to add a new bucket if needed

⚠️ Claude Code plugin discovery is TOP-LEVEL only. CC auto-discovers skills/<name>/SKILL.md one level deep — it does NOT scan skills/<bucket>/<name>/. So a skill you want Claude to auto-discover MUST live at the top level skills/<kebab-name>/ (like memory-flywheel, tui-installer, figma-design-fetch). The skills/general/* copies are reached by Codex (skills/ glob) and opencode (deploy-skills), NOT by the CC plugin. If the skill should be Claude-discoverable, create it at skills/<kebab-name>/ (bucket is then just an organizational tag in INVENTORY, not a path level).

Steps

  1. Create directory:

    mkdir -p skills/<bucket>/<kebab-name>
  2. Ask the user for:
    • One-line description (becomes description: frontmatter — this is what Claude reads to decide auto-invocation)
    • Trigger: auto (Claude invokes when matched) / slash-only (user must type /<name>) / both
    • Skill body content — what does the skill do?
  3. Write skills/<bucket>/<kebab-name>/SKILL.md:

    ---
    name: <kebab-name>
    description: <one-line — be specific; this is what Claude matches against>
    <if user-only:> disable-model-invocation: true
    ---
    
    # /<kebab-name>
    
    <opening summary line>
    
    ## Master TOC
    
    - [Pre-flight](#pre-flight)
    - [Steps](#steps)
    - [Notes for the agent](#notes-for-the-agent)
    - [Companion](#companion)
    
    ## Pre-flight
    
    <any verification, e.g. plugin-preflight checks>
    
    ## Steps
    
    1. <step>
    2. <step>
    ...
    
    ## Notes for the agent
    
    <gotchas, anti-patterns, things to avoid>
    
    ## Companion
    
    <related rules / skills / hooks>
  4. Update skills/README.md — add a row to the skill index table.
  5. Update INVENTORY.md AND INVENTORY.zh.md — add a row to the Skills section.
  6. Show the user the diff and ask for confirmation before committing.

Frontmatter conventions

  • name — kebab-case, matches the directory name
  • description — be specific about WHEN the skill fires. Claude uses this to decide auto-invocation. Vague descriptions cause both false positives and false negatives.
  • disable-model-invocation: true — set for skills with side effects (deploy, force-push, etc.) that should only fire on explicit user request

Companion

  • docs/CONTRIBUTING.md §"Adding a skill" — formal spec
  • skills/README.md — index of all skills + bucket conventions
  • Anthropic's skill-creator plugin — for more sophisticated skill authoring with evals

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.