agentleFS
KushpawanKushpawan/kmp-mobile-skills/AGENTS.md

kmp-mobile-skills

AGENTS.md15 starsChanged 22 days agoApache-2.0View on GitHub

This file is for agents editing this repo (writing or fixing skills). It is not loaded by people who install the skills. - The rules for every skill are in docs/skill-authoring-guide.md. Read it before creating or editing anything under skills/. - One skill per folder: skills/<name>/SKILL.md, where name in the frontmatter equals the folder name. Use only the six portable frontmatter keys. - Every skill needs evals/<name>-trigger/prompt.md; run python3 scripts/scaffold_trigger_eval.py <name> after writing the prompt. - Never hand-edit the skill…

The file

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

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

  • 3

    Very specific

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

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

    Read it before creating or editing anything under skills/.

    line 7
  2. Very specific:

    Every skill needs evals/<name>-trigger/prompt.md.

    line 10
  3. Very specific:

    Never hand-edit the skill lists in .codex-plugin/plugin.json / .cursor-plugin/plugin.json or the README catalog.

    line 12
  4. Distinctive:

    Before you say a change is done, run and report:

    line 14
  5. Distinctive:

    Do not vendor third-party skills without following section 8 of the authoring guide.

    line 24

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

Instructions for AI agents working on this repository

This file is for agents editing this repo (writing or fixing skills). It is not loaded by people who install the skills.

  • The rules for every skill are in docs/skill-authoring-guide.md. Read it before creating or editing anything under skills/.
  • One skill per folder: skills/<name>/SKILL.md, where name in the frontmatter equals the folder name. Use only the six portable frontmatter keys.
  • Every skill needs evals/<name>-trigger/prompt.md; run python3 scripts/scaffold_trigger_eval.py <name> after writing the prompt.
  • Never hand-edit the skill lists in .codex-plugin/plugin.json / .cursor-plugin/plugin.json or the README catalog. Run python3 scripts/sync_manifests.py.
  • Before you say a change is done, run and report:

    python3 scripts/validate_skills.py --strict
    python3 scripts/sync_manifests.py --check
    python3 scripts/run_tests.py
  • Examples use com.example.app and neutral domains. Never add company, product or person names, internal hostnames, local paths, tokens or keys.
  • Do not vendor third-party skills without following section 8 of the authoring guide.

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.