writing-for-agents

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

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill writing-for-agents-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/writing-for-agents
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill writing-for-agents-cyrus-pinto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: agents miss referenced material, rush steps, or drown in bloated files. This Skill provides a systematic reference for writing agent-facing documents (skills, AGENTS.md, CLAUDE.md) so the agent follows the intended process reliably on every run. ## Core Features & Use Cases - Context pointer design: Rules for writing descriptions and pointer lines that reliably trigger the agent to reach out-of-context material, with branch-based trigger wording. - Information hierarchy guidance: A ladder model (in-file steps, in-file reference, disclosed reference) plus progressive disclosure and co-location principles to keep documents legible and focused. - 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 agent skill, use this reference to write a sharp description, structure steps with clear completion criteria, push reference material behind pointers, and choose between model-invoked and user-invoked invocation via SKILL-MECHANICS.md. ## Quick Start Ask the agent to review your draft SKILL.md or AGENTS.md using the writing-for-agents guidance and suggest improvements to its description, structure, and step 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?

Write the description as a context pointer: front-load the leading trigger word, list one trigger per distinct branch the skill handles, and cut any identity the body already carries. Every word stays loaded in context, so prune aggressively.

How should I structure an AGENTS.md or CLAUDE.md file?

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

When should I split one skill into multiple skills?

Split by sequence when visible later steps tempt the agent to rush the current one, or 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 can fire it autonomously, paying permanent context load. A user-invoked skill sets disable-model-invocation: true, removing agent discovery so only a human typing its name can trigger it.

Why does my agent skip steps or finish tasks prematurely?

Premature completion happens when a step's completion criterion is vague and later steps are 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.