writing-for-agents

Guides writing skills, AGENTS.md, and CLAUDE.md documents for agent consumption.

1|Updated Jul 25, 2026
One-click install
npx skills add https://github.com/zacgoodwin/AIBootstrap --skill writing-for-agents-zacgoodwin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/zacgoodwin/AIBootstrap/tree/main/.claude/skills/writing-for-agents
Command: npx skills add https://github.com/zacgoodwin/AIBootstrap --skill writing-for-agents-zacgoodwin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: weak descriptions never trigger, bloated files bury key steps, and vague completion criteria let agents stop early. This Skill provides a reference framework for writing any document an agent consumes so the agent follows the same process reliably every run. ## Core Features & Use Cases - Context pointer design: Rules for writing skill descriptions and AGENTS.md lines that front-load trigger words and list distinct branches so agents reach material reliably. - Information hierarchy and progressive disclosure: A ladder for deciding what stays inline versus what moves behind a pointer into disclosed reference files, controlling context load and cognitive load. - Completion criteria and splitting: Guidance on writing checkable, exhaustive step-completion criteria and deciding when to split documents by sequence or invocation, including model-invoked versus user-invoked skills and router skills. - Use Case: When authoring a new Claude Code skill, use this reference to write a description that triggers on the right branches, prune no-op sentences, and decide whether shared reference material belongs in a sibling file like SKILL-MECHANICS.md. ## Quick Start Ask the agent to review your draft skill or CLAUDE.md using the writing-for-agents reference and suggest improvements to its description, structure, and completion criteria.

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?

Front-load the leading trigger word and list one trigger per distinct branch the skill handles, since the description is always loaded and decides when the agent fires the skill. Cut synonyms that rename the same branch and remove identity the body already carries.

When should I split a skill into multiple files?

Split by sequence when visible later steps tempt the agent to rush the current one, and split by invocation when a distinct trigger word deserves its own model-invoked skill. Push reference material only some branches need into a disclosed sibling file reached by a pointer.

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: true, so only a human typing its name can trigger it, costing zero context load.

Why does my agent stop a task before finishing it?

Premature completion happens when a step's completion criterion is vague, letting attention slip toward being done. Sharpen the criterion into a checkable, exhaustive condition first; if the rush persists, hide later steps behind a real context boundary like a subagent dispatch.

Should I repeat conventions in CLAUDE.md that config files already show?

No. The environment, including package.json scripts, config files, and --help output, is a source of truth, and restating it creates a stale cache. Document only what the agent cannot find by looking, such as unwritten conventions and rationale.