writing-for-agents

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

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Evolutionary-Leadership/harness --skill writing-for-agents-evolutionary-leadership
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/Evolutionary-Leadership/harness/tree/main/.claude/skills/writing-for-agents
Command: npx skills add https://github.com/Evolutionary-Leadership/harness --skill writing-for-agents-evolutionary-leadership

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often produce inconsistent behavior because their wording, structure, and length are not engineered for how agents consume context. This Skill provides a reference framework for writing any agent-facing document (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 reliably trigger the right material, with front-loaded leading words and one trigger per branch. - Information hierarchy: A ladder model (in-file steps, in-file reference, disclosed reference) plus progressive disclosure and co-location guidance to keep documents legible and prevent sprawl. - Completion criteria and pruning: Techniques for writing checkable, demanding step completion criteria, and for removing duplication, stale caches, no-op sentences, and negation-based instructions. - Use Case: When creating a new skill or editing CLAUDE.md, consult this reference to decide what to inline, what to disclose behind a pointer, and how to word the description so the agent fires it reliably. ## Quick Start Ask the agent to review your new skill or CLAUDE.md draft using the writing-for-agents guidance and suggest what to inline, disclose, or prune.

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 skill description that an AI agent will trigger reliably?

Write the description as a context pointer: front-load the leading word, list one trigger per distinct branch the document handles, and cut anything the body already states. The pointer's wording, not its target, determines when the agent reaches the material.

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, 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 two 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 or another skill must reach it. Each split spends context or cognitive load, so the cut must earn it.

Why should I avoid negation in agent instructions?

Prohibitions drag the forbidden behavior into context and make it more available, since the negation is a weak modifier the activated concept overruns. State the positive target behavior instead, reserving prohibitions for hard guardrails paired with the positive instruction.

What content should stay in CLAUDE.md versus a separate referenced doc?

Keep in the main file what every branch needs; push behind a context pointer what only some branches reach. Cache only what the environment cannot reveal, such as unwritten conventions and rationale, and leave one-command lookups to config files and the directory layout.