writing-for-agents

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

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/MSC72m/DevForge --skill writing-for-agents-msc72m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/MSC72m/DevForge/tree/main/skills/writing-for-agents
Command: npx skills add https://github.com/MSC72m/DevForge --skill writing-for-agents-msc72m

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 of writing levers that make agent-consumed documents behave consistently across runs. ## 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: Guidance on progressive disclosure, co-location, and splitting documents by sequence or invocation to prevent sprawl. - Completion Criteria & Leading Words: Techniques for sharpening step boundaries, raising demand, and anchoring behavior with compact pretrained concepts. - Use Case: When authoring a new skill or editing CLAUDE.md, apply these rules to prune no-op sentences, collapse restatements into leading words, and decide what to inline versus disclose behind a pointer. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents reference and suggest pruning, pointer, and splitting improvements.

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, state what the material is, and list one trigger per distinct branch the document handles. Cut synonyms and identity the body already carries, since every word of an always-loaded description costs context on every turn.

How to structure AGENTS.md or CLAUDE.md files for agents?▼

Treat each line as a context pointer naming out-of-context material and the condition for reaching it. Keep steps inline, push branch-specific reference behind pointers, and prune lines that restate what the environment already shows.

When should a skill be model-invoked vs user-invoked?▼

Choose model-invoked when the agent or another skill must reach it autonomously, paying permanent context load for the description. Set disable-model-invocation: true for skills only fired by hand, trading discoverability for zero context load.

Why does my agent stop a task before finishing it?▼

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 split the sequence across a real context boundary if the rush persists.

When should I split one skill into multiple skills?▼

Split by sequence when visible post-completion steps tempt the agent to rush the current one, or by invocation when a distinct trigger word deserves independent reach. Each split spends context or cognitive load, so the cut must earn it.