agentleFS
gohypergiantgohypergiant/agent-skills/skills/accelint-skill-manager/references/agents.md

agent-skills / references

AGENTS.md25 starsChanged 54 days agoApache-2.0View on GitHub

General rule of thumb is to follow guidance from Agents.md. At minimum try and provide concise and descriptive examples of what incorrect and correct. Consolidate examples as reasonably as possible to reduce token usage. The persona and target audience for this document is an AI Agent or LLM. ❌ Incorrect: repeated workflow details ✅ Correct: reference other skill ❌ Incorrect: verbose example (42 words) ✅ Correct: minimal example (20 words) Reference: https://agents.md/#examples

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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 repeat what's in cross-referenced skills

    line 52
  2. Distinctive:

    Don't explain what's obvious from skill

    line 53
  3. Distinctive:

    Don't include multiple examples of same pattern

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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

1.3 AGENTS.md

Overview

General rule of thumb is to follow guidance from Agents.md. At minimum try and provide concise and descriptive examples of what incorrect and correct. Consolidate examples as reasonably as possible to reduce token usage. The persona and target audience for this document is an AI Agent or LLM.

Token Efficiency (Critical)

Use cross-references:

❌ Incorrect: repeated workflow details

When searching, dispatch subagent with template...
[20 lines of repeated instructions]

✅ Correct: reference other skill

Always use subagents. REQUIRED: Use [other-skill-name] for workflow.

Compress examples:

# ❌ BAD: Verbose example (42 words)
your human partner: "How did we handle authentication errors in React Router before?"
You: I'll search past conversations for React Router authentication patterns.
[Dispatch subagent with search query: "React Router authentication error handling 401"]

# ✅ GOOD: Minimal example (20 words)
Partner: "How did we handle auth errors in React Router?"
You: Searching...
[Dispatch subagent → synthesis]

❌ Incorrect: verbose example (42 words)

your human partner: "How did we handle authentication errors in React Router before?"
You: I'll search past conversations for React Router authentication patterns.
[Dispatch subagent with search query: "React Router authentication error handling 401"]

✅ Correct: minimal example (20 words)

Partner: "How did we handle auth errors in React Router?"
You: Searching...
[Dispatch subagent → synthesis]

Eliminate redundancy

  • Don't repeat what's in cross-referenced skills
  • Don't explain what's obvious from skill
  • Don't include multiple examples of same pattern

Reference: https://agents.md/#examples

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.