agentleFS
gonun13gonun13/agent-skills/skills/_template/SKILL.md

your-skill-name

Skill0 starsChanged 2 months agoMITView on GitHub

What this does. Use when <trigger, e.g. the user mentions X>.

49 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 1

    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:

    Don't guess — inspect the repo or state what's unknown.

    line 27

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

Goal

One sentence: the concrete outcome this produces.

Context

What to check first: relevant files, commands, or docs. Only what's not obvious.

Steps

  1. ...
  2. ...
  3. Validate: <the actual check/test command>.

In plan mode, stop at <step>; the plan is <what the operator reviews>.

Constraints

  • What's in scope and what must not change.
  • Don't guess — inspect the repo or state what's unknown.

Done when

Checkable criteria (tests pass, specific output produced, etc.).

Output

Exact structure the result should take. A skill that changes no code names the file its report is saved to.

Supporting files are referenced by their path inside the skill directory, e.g. principles/01-name.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.