agentleFS
Sign inStart free
adhyayanrathi01adhyayanrathi01/product-manager-os/skills/AGENTS.md

product-manager-os / skills

AGENTS.md2 starsChanged 2 months agoMITView on GitHub

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Keep every skill provider-neutral and focused on a reusable process.

    line 3
  2. Distinctive:

    Prefer evidence-backed outputs over generic advice.

    line 5
  3. Distinctive:

    Stop for PM judgment when a workflow reaches prioritization or product decision-making.

    line 6
  4. Distinctive:

    Do not add provider-specific folders unless a future workflow genuinely cannot remain portable.

    line 7
  5. Very specific:

    Use skills/evidence/evidence-handoff.md whenever findings may be consumed by another skill or project workflow.

    line 11

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

Skill rules

  • Keep every skill provider-neutral and focused on a reusable process.
  • Discover available tools and data access at runtime.
  • Prefer evidence-backed outputs over generic advice.
  • Stop for PM judgment when a workflow reaches prioritization or product decision-making.
  • Do not add provider-specific folders unless a future workflow genuinely cannot remain portable.
  • Improve skills only with generalizable, non-sensitive, non-duplicative learnings.
  • Give each skill a concise contract covering required inputs, readiness checks, output or artifact, partial-result behavior, and blocking conditions.
  • Mark task-relevant capabilities ready, partial, or blocked from context.md instead of treating connection presence as readiness.
  • Use skills/evidence/evidence-handoff.md whenever findings may be consumed by another skill or project workflow.

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