writing-for-agents

Guides writing skills, AGENTS.md files, and agent-consumed documentation using context pointers and progressive disclosure.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill writing-for-agents-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-extras/skills/writing-for-agents
Command: npx skills add https://github.com/toderian/project_template --skill writing-for-agents-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Documents written for AI agents often fail because agents under-trigger on weak pointers, rush steps with vague completion criteria, or drown in bloated files. This Skill provides a systematic reference for writing any document an agent consumes so it behaves predictably on every run. ## Core Features & Use Cases - Context pointer design: Teaches how to word skill descriptions and AGENTS.md lines so agents reliably reach the right material at the right branch. - Information hierarchy and progressive disclosure: Explains the ladder of in-file steps, in-file reference, and disclosed reference, plus co-location, sprawl, and when to split documents by sequence or invocation. - Completion criteria and pruning: Covers writing checkable, demanding step boundaries, using leading words, avoiding negation, and removing duplication, caches, no-ops, and sediment. - Use Case: When creating a new skill or editing an AGENTS.md file, apply these rules to sharpen the description's trigger branches, push branch-specific reference into a references/ file, and give every step a clear done condition. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents guidance and rewrite weak pointers and vague 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 word, list one trigger per branch the document handles, and name concrete contexts where it should fire. Agents under-trigger more than over-trigger, so include situations users may never phrase explicitly.

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

Keep always-loaded lines minimal since every word costs context each turn, and point to deeper docs behind context pointers. Inline what every branch needs and disclose material only some branches reach into separate referenced files.

What is progressive disclosure in agent skills?

Progressive disclosure moves reference material down the information hierarchy into separate files loaded only when a pointer fires. It keeps the main document legible so steps stay visible instead of being buried under flat reference content.

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

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

Why do agents skip steps or finish tasks prematurely?

Premature completion happens when a step's completion criterion is vague, letting attention slip toward being done. Sharpen the criterion to something checkable and demanding, or split the sequence across a real context boundary so later steps stay out of view.

What are the limitations of long instruction documents for agents?

Overly long documents cause sprawl: attention thins across the excess even when every line is relevant. The fix is splitting by branch or sequence and disclosing reference behind pointers so each run carries only what it needs.