agentleFS
1second11second1/personal-research-skills/AGENTS.md

personal-research-skills

AGENTS.md1 starsChanged 37 days agoMITView on GitHub

This project composes research methodology profiles and Skill contracts into portable Markdown contexts. It does not execute a model or learn automatically. - Core: research_skills/dna.py and research_skills/compose.py. - CLI: research_skills/cli.py (research-skills); scripts/run_skill.py is the compatibility wrapper. - Evaluation: research_skills/evaluation.py, run_records.py, and blinding.py. - Install: python -m pip install -e . - Verify: python -m unittest discover -s tests -v, then research-skills validate. - Keep source facts, inferences, and unsupported claims distinct. - A deterministic format check is not proof of…

  • Installs packages
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository4 other files it gives its agents.

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:

    Verify: python -m unittest discover -s tests -v, then research-skills validate.

    line 10
  2. Distinctive:

    Keep source facts, inferences, and unsupported claims distinct.

    line 12
  3. Very specific:

    Keep handoff context in docs/AGENT-HANDOFF-PLAN.md.

    line 14

≈ “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

Project instructions

This project composes research methodology profiles and Skill contracts into portable Markdown contexts. It does not execute a model or learn automatically.

  • Core: research_skills/dna.py and research_skills/compose.py.
  • CLI: research_skills/cli.py (research-skills); scripts/run_skill.py is the compatibility wrapper.
  • Evaluation: research_skills/evaluation.py, run_records.py, and blinding.py.
  • Install: python -m pip install -e .
  • Verify: python -m unittest discover -s tests -v, then research-skills validate.
  • Keep source facts, inferences, and unsupported claims distinct.
  • A deterministic format check is not proof of factual or research quality.
  • Keep handoff context in docs/AGENT-HANDOFF-PLAN.md; do not add weekly logs.

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.