agentleFS
imMamdouhaboammarimMamdouhaboammar/matts-skills-into-chatgpt/AGENTS.md

matts-skills-into-chatgpt

AGENTS.md8 starsChanged 2 months agoMITView on GitHub

This repository is the public source for the matt-skills-curated ChatGPT/Codex plugin.

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

5 rules. About 0 are common, 3 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every Skill must have SKILL.md and agents/openai.yaml.

    line 6
  2. Distinctive:

    Every packaged Skill is model-invoked in this curated edition so the router can reach it automatically.

    line 7
  3. Distinctive:

    Keep upstream provenance and MIT attribution accurate.

    line 9
  4. Distinctive:

    Do not exclude a Skill solely because upstream called it misc or beta.

    line 10
  5. Very specific:

    Run python3 scripts/validate_plugin.py and deterministic double packaging before committing a release.

    line 11

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

Repository maintenance

This repository is the public source for the matt-skills-curated ChatGPT/Codex plugin.

  • skills/ is flat and contains only public, curated Skills.
  • Every Skill must have SKILL.md and agents/openai.yaml.
  • Every packaged Skill is model-invoked in this curated edition so the router can reach it automatically. Do not add manual-only invocation flags to public Skills.
  • engineering-workflow-guide is the model-invoked router and its catalog must cover every other packaged Skill exactly once.
  • Keep upstream provenance and MIT attribution accurate.
  • Do not exclude a Skill solely because upstream called it misc or beta. Promote useful capabilities after portability, safety, dependency, and quality review; exclude only duplicates, host-specific surfaces, deprecated material, telemetry, credentials, symlinks, or generated noise.
  • Run python3 scripts/validate_plugin.py and deterministic double packaging before committing a release.

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.