writing-for-agents

Guides writing skills, AGENTS.md, and CLAUDE.md documents that agents consume predictably.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill writing-for-agents-fatih0234
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/Fatih0234/mattpocock-skills-pi/tree/main/skills/productivity/writing-for-agents
Command: npx skills add https://github.com/Fatih0234/mattpocock-skills-pi --skill writing-for-agents-fatih0234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: agents miss referenced material, rush steps, or get lost in bloated files. This Skill provides a systematic reference for writing any document an agent consumes so the agent follows the same process every run. ## Core Features & Use Cases - Context pointer design: Rules for writing descriptions and references that reliably trigger the agent to reach out-of-context material, with branch-based trigger wording. - Information hierarchy and progressive disclosure: A ladder model (in-file steps, in-file reference, disclosed reference) for deciding where each piece of content lives, plus co-location and sprawl guidance. - Completion criteria and splitting: Techniques for writing checkable, exhaustive step completion criteria and deciding when to split documents by sequence or invocation. - Use Case: When authoring a new skill or editing an AGENTS.md file, consult this reference to prune no-op instructions, choose leading words, and structure pointers so the agent behaves consistently. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents guidance and suggest improvements to its pointers and structure.

Frequently Asked Questions about writing-for-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a good skill description for an AI agent?▼

Write the description as a context pointer: front-load the leading word, list one trigger per distinct branch the skill handles, and cut anything the body already states. The description stays loaded at all times, so every word must earn its place.

How to structure an AGENTS.md or CLAUDE.md file?▼

Organize content along the information hierarchy: keep primary steps in-file, consult reference material on demand, and push branch-specific material behind pointers to separate files. Co-locate each concept's definition, rules, and caveats under one heading.

When should I split a skill into multiple skills?▼

Split by sequence when visible later steps tempt the agent to rush the current one, or split by invocation when a distinct trigger word should fire a skill independently. Each split costs context load or cognitive load, so the cut must earn it.

What is the difference between model-invoked and user-invoked skills?▼

A model-invoked skill keeps a description so the agent and other skills can fire it autonomously, paying permanent context load. A user-invoked skill sets disable-model-invocation so only a human typing its name can trigger it, costing zero context load.

Why does my agent skip steps or finish tasks prematurely?▼

Premature completion happens when a step's completion criterion is vague and later steps remain visible, pulling attention forward. Sharpen the criterion's bound first; if it stays fuzzy, hide later steps by splitting the sequence across a real context boundary.