writing-for-agents

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often trigger unreliably, bloat the context window, or get ignored. This Skill provides a reference framework for writing any document an agent consumes—skills, AGENTS.md, CLAUDE.md, or pointer-reached docs—so the agent follows the same process every run. ## Core Features & Use Cases - Context pointer design: Rules for writing descriptions and pointer lines that front-load trigger words and list distinct branches, so agents reach material reliably. - Information hierarchy guidance: A ladder model (in-file steps, in-file reference, disclosed reference) plus progressive disclosure and co-location principles to fight document sprawl. - 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 skill, use this reference to write a description that triggers on the right branches, prune no-op sentences, and decide between model-invoked and user-invoked invocation via the companion SKILL-MECHANICS.md file. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents principles and suggest improvements to its description and structure.

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 and list one trigger per distinct branch the skill handles. Cut synonyms that rename a single branch and remove 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.

What is progressive disclosure in agent documentation?▼

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

Why should I avoid negative instructions in prompts for agents?▼

Negation drags the forbidden behavior into context and makes it more available, since the strongly-activated concept overruns the weak negation. State the positive target behavior instead, reserving prohibitions for hard guardrails paired with a positive instruction.