writing-for-agents

Write skills, AGENTS.md, and CLAUDE.md documents that agents follow predictably.

1|Updated Sep 13, 2026
One-click install
npx skills add https://github.com/silentFellow/public-dotfiles --skill writing-for-agents-silentfellow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/silentFellow/public-dotfiles/tree/main/agents/skills/writing-for-agents
Command: npx skills add https://github.com/silentFellow/public-dotfiles --skill writing-for-agents-silentfellow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: agents skip steps, miss reference material, or rush to completion. 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: Write descriptions and pointer lines whose wording reliably triggers the agent to reach the right material at the right branch. - Information hierarchy: Place content on the ladder from in-file steps to disclosed reference, using progressive disclosure and co-location to prevent sprawl. - Completion criteria and splitting: Define clear, demanding done-conditions for every step, and split documents by sequence or invocation to prevent premature completion. - Use Case: When creating a new skill or editing an AGENTS.md file, apply the leading-word, pruning, and two-loads (context vs. cognitive) frameworks to produce a lean document the agent executes consistently. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents principles and suggest concrete revisions.

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 skill description that agents trigger reliably?▼

Write the description as a context pointer: front-load the leading word, state what the material is, and list one trigger per distinct branch. Cut synonyms that rename a single branch and remove identity the body already carries, since every word of an always-loaded pointer costs context on every turn.

How do I structure an AGENTS.md or CLAUDE.md file for agents?▼

Organize content on the information hierarchy: in-file steps first, in-file reference consulted on demand, and disclosed reference pushed behind pointers. Keep each concept's definition, rules, and caveats co-located under one heading, and prune lines that no longer bear on the document's task.

When should I split a skill into multiple skills?▼

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 or another skill must reach it. Each new model-invoked skill adds an always-loaded description, so the independent reach must be worth the context load.

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, removing the description from the agent's reach so only the human typing its name can invoke it, at zero context load.

Why do agents 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 if it is irreducibly fuzzy and the rush is observed, hide later steps by splitting the sequence across a real context boundary.