writing-for-agents

Guides writing skills, AGENTS.md, and CLAUDE.md documents for agent consumption.

Updated May 9, 2024
One-click install
npx skills add https://github.com/AceCodePt/dotfiles --skill writing-for-agents-acecodept
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/AceCodePt/dotfiles/tree/main/.config/opencode/skills/writing-for-agents
Command: npx skills add https://github.com/AceCodePt/dotfiles --skill writing-for-agents-acecodept

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: weak descriptions never trigger, bloated files dilute attention, and vague steps invite premature completion. This Skill provides a reference framework for writing any document an agent consumes so the agent follows the same process reliably on every run. ## Core Features & Use Cases - Context pointer design: Rules for writing skill descriptions and AGENTS.md lines that front-load trigger words and list distinct branches so material is reached reliably. - Information hierarchy: A ladder model (in-file steps, in-file reference, disclosed reference) plus progressive disclosure and co-location guidance to fight document sprawl. - Completion criteria and splitting: Techniques for writing checkable, exhaustive step boundaries and deciding when to split documents by sequence or invocation. - Skill mechanics: A companion file covers frontmatter, model-invoked versus user-invoked skills, and router skills. - Use Case: When authoring a new skill or editing CLAUDE.md, apply the pruning, leading-word, and negation-avoidance rules to cut token load while sharpening agent behavior. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents guidelines and suggest 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 skill 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, removing agent discovery so only a human typing its name can trigger it.

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 deserves its own model-invoked skill. 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 so it loads only when needed. 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.