Agent skill · writing content · pedronauck
writing-agents-md
Write or audit AGENTS.md/CLAUDE.md instructions. Use writing-skills for on-demand skills; excludes human-facing docs and READMEs.
Why this skill is useful
Provides domain-specific guidelines for writing efficient AGENTS.md files that enhance agent instruction clarity and effectiveness.
What it needs
About 2k tokens when loaded. Last updated 2026-08-01. 564 stars on the source repository.
What this skill does
Writing Agent Instructions Keep AGENTS.md/CLAUDE.md focused on project decisions the agent cannot reliably infer from nearby code or tooling. Instruction loading differs by harness; verify which root and nested files apply before counting their context cost. Keep, Move, or Remove Keep non-obvious commands, expensive tripwires, domain vocabulary, and project-specific ownership/compatibility decisions. Move a rule to the narrowest subtree or on-demand skill that needs it. Link long rationale or incident evidence instead of embedding it. Remove generic engineering advice, duplicated rules, stale model pins, rhetorical emphasis, fixed response ceremonies, and procedures already owned by the harness or toolchain. A rule must name when it applies. Availability of a skill does not justify requiring it for every task. Preserve concrete safety and product invariants while narrowing their procedure. For recurring workflows, make existing authorization concrete: name the work the agent may finish autonomously, the conditions that make it safe, the observable stopping condition, and any action requiring approval. Remove review stops that interrupt already authorized work before that result. Work 1. Read the relevant instructions, current repository contracts, and user decisions. Check recent changes before pruning policy; keep historical evidence separate from active rules. 2. Review rules by concern: keep, rewrite, relocate, or remove. Record material policy changes and relocations in a concise summary; a line-by-line public verdict table is unnecessary unless requested. 3. Resolve contradictions using the user's current direction and the repository's authoritative policy. Ask only if a remaining conflict changes the outcome and has no established owner. 4. Edit the canonical owning file and update its pointers. Preserve symlinks and tool-generated blocks; avoid parallel copies that drift. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pedronauck/writing-agents-md