agentleFS
SaKaNa-YSaKaNa-Y/skills/AGENTS.md

skills

AGENTS.md2 starsChanged 29 days agoMITView on GitHub

When adding or changing a skill or its supporting files, follow the metadata policy for author and date-version updates. When changing public Markdown, file paths, headings, or the reference checker, follow repository validation before reporting completion. Check the complete candidate tree, including unchanged reference sources. For skill evolution, renames, retirement, and history migration, follow the repository history policy. Detailed history stays local; selected summaries are tracked after publication review. Execution environments and migration quarantine stay ignored. Issues and specs are…

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When adding or changing a skill or its supporting files, follow the metadata policy for author and date-version updates.

    line 5
  2. Distinctive:

    When changing public Markdown, file paths, headings, or the reference checker, follow repository validation before reporting completion.

    line 9
  3. Very specific:

    Use the five canonical triage labels without overrides.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “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
AGENTS.md

Agent skills

Skill metadata

When adding or changing a skill or its supporting files, follow the metadata policy for author and date-version updates.

Repository validation

When changing public Markdown, file paths, headings, or the reference checker, follow repository validation before reporting completion. Check the complete candidate tree, including unchanged reference sources.

Evolution records

For skill evolution, renames, retirement, and history migration, follow the repository history policy. Detailed history stays local; selected summaries are tracked after publication review. Execution environments and migration quarantine stay ignored.

Issue tracker

Issues and specs are tracked in GitHub Issues using the gh CLI. See docs/agents/issue-tracker.md.

Triage labels

Use the five canonical triage labels without overrides. See docs/agents/triage-labels.md.

Domain docs

This repo uses the single-context layout: root CONTEXT.md and docs/adr/. See docs/agents/domain.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.