agentleFS
Sign inStart free
docxologydocxology/template/.agents/skills/AGENTS.md

template / skills

AGENTS.md20 starsChanged 2 months agoApache-2.0View on GitHub

Vendored Agent Skills from muratcankoylan/Agent-Skills-for-Context-Engineering, pinned by ../context-engineering.lock.json. - Load SKILL.md progressively when its trigger matches; do not preload every body into the context window. - Treat scripts/ and shell/Python snippets as examples. Never auto-execute them; several accept caller-controlled paths or demonstrate credentialed shell commands. - Preserve relative paths when updating a skill. - Do not place a skill from another upstream in this tree or absorb it by changing only the recorded counts/digest; that would misstate provenance. - Refresh…

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. Very specific:

    Treat scripts/ and shell/Python snippets as examples.

    line 11
  2. Distinctive:

    Do not place a skill from another upstream in this tree or absorb it by changing only the recorded counts/digest.

    line 15
  3. Distinctive:

    Run the upstream validators plus this repository's skill, runtime-sync, MCP, Ruff, mypy, and test gates before changing the pin.

    line 19

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

.agents/skills/

Vendored Agent Skills from muratcankoylan/Agent-Skills-for-Context-Engineering, pinned by ../context-engineering.lock.json.

Safety and maintenance

  • Load SKILL.md progressively when its trigger matches; do not preload every body into the context window.
  • Treat scripts/ and shell/Python snippets as examples. Never auto-execute them; several accept caller-controlled paths or demonstrate credentialed shell commands.
  • Preserve relative paths when updating a skill.
  • Do not place a skill from another upstream in this tree or absorb it by changing only the recorded counts/digest; that would misstate provenance.
  • Refresh through the audited installer at a pinned commit, reapply and record local overlays, then update both upstream and vendored hashes.
  • Run the upstream validators plus this repository's skill, runtime-sync, MCP, Ruff, mypy, and test gates before changing the pin.

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.

Reviews can't be read right now.

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