writing-for-agents

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

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/juanjaragavi/utilities-manager --skill writing-for-agents-juanjaragavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/juanjaragavi/utilities-manager/tree/main/.agents/skills/writing-for-agents
Command: npx skills add https://github.com/juanjaragavi/utilities-manager --skill writing-for-agents-juanjaragavi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: agents miss referenced material, rush steps, or ignore instructions. This Skill provides a systematic reference for writing agent-facing documents so the agent follows the same process every run, covering skills, AGENTS.md, CLAUDE.md, and any doc reached by a pointer. ## 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 and progressive disclosure: A ladder model (in-file steps, in-file reference, disclosed reference) for deciding what stays inline and what moves behind a pointer. - Completion criteria and splitting: Guidance on writing checkable, exhaustive step completion criteria and deciding when to split documents by sequence or invocation. - Use Case: When authoring a new skill, use this reference to write a frontmatter description with distinct trigger branches, prune no-op sentences, and decide between model-invoked and user-invoked invocation via the companion SKILL-MECHANICS.md. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents principles and suggest pruning, pointer, and structure 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?▼

Write the description as a context pointer: front-load the leading trigger word 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.

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, so only a human typing its name can reach it, costing zero context load.

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.

Why does my agent ignore instructions in AGENTS.md?▼

Common causes are weakly worded pointers, negation-based instructions that activate the forbidden behavior, and no-op sentences the model already obeys by default. Sharpen pointer wording, state the positive target behavior, and delete sentences that fail the default-behavior test.

What is progressive disclosure in agent documentation?▼

Progressive disclosure moves reference material out of the main file and behind a context pointer so it loads only when the pointer fires. Inline what every branch needs and disclose what only some branches reach, keeping the top-level document legible.