agentleFS
agentmemoiragentmemoir/skills/template/SKILL.md

my-skill-name

Skill2 starsChanged 22 days agoMITView on GitHub

What this skill does plus when the agent uses it. Use when <trigger> or when I mention <keywords>. Keep under 1024 chars, third person.

10 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 3

    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. Distinctive:

    Use when: <concrete trigger 1>.

    line 19
  2. Distinctive:

    Do not use for: <near-miss to avoid false triggers>.

    line 21
  3. Distinctive:

    Verify: <checklist the agent ticks off before finishing>.

    line 27
  4. Very specific:

    Run scripts/<name>.py to <purpose> (execute, do not read into context).

    line 33
  5. Very specific:

    Read references/<name>.md when <specific condition>.

    line 34
  6. Very specific:

    Use assets/<name> as <template or data> for <output>.

    line 35

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

My Skill Name

One or two sentences: what this does and why it matters.

When to Use

  • Use when: <concrete trigger 1>.
  • Use when: <concrete trigger 2>.
  • Do not use for: <near-miss to avoid false triggers>.

Workflow

  1. Step one: <exact action>.
  2. Step two: <exact action, with command if fragile>.
  3. Verify: <checklist the agent ticks off before finishing>.

Resources

List each bundled file with when to load it. Keep links one level deep.

  • Run scripts/<name>.py to <purpose> (execute, do not read into context).
  • Read references/<name>.md when <specific condition>.
  • Use assets/<name> as <template or data> for <output>.

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.