writing-for-agents

Write and structure documents that AI agents consume, including skills and AGENTS.md files.

Updated Nov 10, 2013
One-click install
npx skills add https://github.com/bnferguson/dotfiles --skill writing-for-agents-bnferguson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/bnferguson/dotfiles/tree/main/.agents/skills/writing-for-agents
Command: npx skills add https://github.com/bnferguson/dotfiles --skill writing-for-agents-bnferguson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: weak descriptions never trigger, bloated files dilute attention, and vague steps invite premature completion. This Skill provides a systematic reference for writing agent-consumed documents so they behave predictably on every run. ## Core Features & Use Cases - Context pointer design: Rules for writing skill descriptions and AGENTS.md lines that reliably trigger the right material at the right branch. - Information hierarchy: A ladder model (in-file steps, in-file reference, disclosed reference) for deciding what to inline versus push behind a pointer, plus co-location and sprawl guidance. - Completion criteria and splitting: Techniques for writing checkable, exhaustive step boundaries and deciding when to split documents by sequence or invocation. - Use Case: When authoring a new skill or editing a CLAUDE.md file, apply the leading-word, pruning, and negation-avoidance rules to produce a document the agent follows consistently. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents guidelines and suggest improvements to its description 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 trigger word and list one trigger per distinct branch the skill handles. Cut synonyms and identity the body already carries, since every word of an always-loaded description costs context on every turn.

When should I split a skill into multiple documents?▼

Split by sequence when visible later steps tempt the agent to rush the current one, and split by invocation when a distinct trigger word should fire a skill on its own. Each split spends context 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 reach 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 toward being done. Sharpen the criterion's bound first; only hide later steps across a real context boundary if the rush persists.

Should I avoid negative instructions in agent prompts?▼

Yes. Negation drags the forbidden behavior into context and makes it more available, so the ban half-reads as an instruction. State the positive target behavior instead, reserving prohibitions for hard guardrails paired with the positive phrasing.