agentleFS
Sign inStart free
maidepsmaideps/ai-harness-framework/skills/write-skill/SKILL.md

write-skill

Skill2 starsChanged 6 days agoMITView on GitHub

Authoring a new skill pack — the format, the rules, and how it is validated.

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use grill, write-docs and 7 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.
  • renatorozasSkill

    grill

    Adversarial code review. Don't let me ship until the changes pass your scrutiny.

    Also in 5 projects that use this

  • SentrySkill

    write-docs

    Create or update documentation pages for the Abacus docs site. Use when adding new documentation, updating existing pages, or ensuring docs stay in sync with code changes. Ensures pages follow Starlight patterns and build correctly.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 4 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 4 projects that use this

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 0

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

    Create a folder under skills/ named after the skill (kebab-case, one word or hyphenated).

    line 17
  2. Very specific:

    Run npm run lint — the runner validates every skill: SKILL.md exists, frontmatter present, name matches the folder, description present, …

    line 24
  3. Very specific:

    Keep the skill generic — no instance-specific content (no feature ids, dates, or machine paths from a specific project).

    line 25

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

Write Skill

The meta-skill: how to add a capability pack to this harness.

When to Use

  • Adding a reusable workflow the team repeats (deploy, migrations, reviews, on-call…)
  • Improving an existing skill
  • Onboarding a skill from another framework or project

Workflow

  1. Create a folder under skills/ named after the skill (kebab-case, one word or hyphenated).
  2. Write skills/<name>/SKILL.md with:
    • YAML frontmatter between --- lines: name (must match the folder name) and description (one line, what the skill does).
    • A ## When to Use section listing the triggering situations.
    • A ## Workflow section — numbered, concrete steps using real commands and file names.
    • A ## Quick Reference checklist of the must-do items.
  3. Optionally add a references/ subfolder for deep material and examples/ for worked examples; reference them from the workflow.
  4. Run npm run lint — the runner validates every skill: SKILL.md exists, frontmatter present, name matches the folder, description present, When to Use present.
  5. Keep the skill generic — no instance-specific content (no feature ids, dates, or machine paths from a specific project). Project-specific knowledge belongs in project skills, which adopters may add under skills/.

Rules

  • Skills are capability packs, not process law — AGENTS.md stays the operating manual.
  • One skill, one workflow. Split rather than bloat.
  • Ground every step in commands and files that actually exist in this harness.

Quick Reference

  • Folder skills/<name>/ with SKILL.md
  • Frontmatter: name matches folder, description present
  • ## When to Use, ## Workflow, ## Quick Reference sections
  • No instance-specific content
  • npm run lint passes skill validation

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