writing-for-agents

Reviews and rewrites agent-facing documents using context pointers, disclosure, and completion criteria.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents—skills, AGENTS.md, CLAUDE.md, sub-agent prompts—often cause unpredictable agent behavior because of weak trigger wording, bloated bodies, vague completion criteria, and stale content. This Skill provides a systematic reference for writing and reviewing such documents so the agent follows the same process every run. ## Core Features & Use Cases - Context pointer design: Write descriptions and pointer lines with front-loaded leading words and one trigger per branch, balancing context load against cognitive load. - Information hierarchy and progressive disclosure: Decide what stays inline, what moves behind a pointer, and when to split a document by sequence or invocation. - Completion criteria and review modes: Define clear, demanding done-conditions per step, and audit documents against seven failure modes (premature completion, duplication, sediment, sprawl, no-op, negation, ambiguity). - Static audit tooling: Run the bundled audit.py to check skills against measurable rules, detect CLI documentation drift, and find dangling cross-references. - Use Case: When writing a new skill or reviewing an existing CLAUDE.md, invoke this Skill to sharpen the description's trigger wording, push reference material behind pointers, and verify each step ends in a checkable criterion. ## Quick Start Ask the agent to review your SKILL.md or CLAUDE.md using the writing-for-agents guidelines and report each of the seven failure modes as present, absent, or not applicable.

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, and cut anything the body already states. Open with the verb that claims the work, and keep it between roughly 105 and 800 characters.

When should I split a skill into multiple documents?▼

Split by sequence when visible later steps tempt the agent to rush the current step, and split by invocation when a distinct trigger word should fire a skill on its own. Each split spends context load or cognitive load, so the cut must earn its cost.

What is the difference between model-invoked and user-invoked skills?▼

A model-invoked skill keeps its description in context so the agent can fire it autonomously, paying permanent context load. A user-invoked skill sets disable-model-invocation: true, removing it from the agent's reach so only the human typing its name can trigger it.

How do I audit a SKILL.md file for common problems?▼

Run the bundled audit.py script with the skill path or --all to check measurable rules: body length, description size, shouted commands, and missing scripts or references. The refs mode also reports cross-references pointing at removed or user-invoked-only skills.

Why should I avoid negative instructions in agent prompts?▼

A prohibition drags the forbidden behavior into context and makes it more available, so the ban half-reads as an instruction. State the positive target behavior instead, reserving negation for hard guardrails that cannot be phrased positively.

What are the limitations of static skill auditing?▼

Static auditing only covers rules decidable from the file alone, such as length and wording patterns. Whether a description actually triggers the skill or a line changes behavior requires a live run with a validation harness, since no-op detection is model-relative.