writing-for-agents

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

1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/jwh3times/holland-vip --skill writing-for-agents-jwh3times
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/jwh3times/holland-vip/tree/main/.agents/skills/writing-for-agents
Command: npx skills add https://github.com/jwh3times/holland-vip --skill writing-for-agents-jwh3times

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often produce inconsistent behavior: agents skip steps, finish early, or ignore reference material. This Skill provides a reference framework for writing agent-consumed documents so the agent follows the same process every run. ## Core Features & Use Cases - Context pointer design: Write descriptions and pointer lines whose wording reliably triggers the agent to reach out-of-context material at the right branch. - Information hierarchy and progressive disclosure: Place steps and reference on the right tier — in-file steps, in-file reference, or disclosed reference behind a pointer — to prevent sprawl and buried instructions. - Completion criteria and splitting: Define clear, demanding completion criteria for each step, and split documents by sequence or invocation to prevent premature completion. - Use Case: When authoring a new skill or editing an AGENTS.md file, apply the pruning rules (single source of truth, no-op detection, leading words) to keep the document short, relevant, and behavior-changing. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents guidance and suggest pruning and pointer 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 skill description that an AI agent will trigger reliably?▼

Write the description as a context pointer: front-load the leading word, state what the material is, 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. Splitting spends context or cognitive load, so the cut must earn it.

Why does my agent finish tasks before the work is actually done?▼

Premature completion happens when a step's completion criterion is vague and later steps remain visible, pulling attention toward being done. Sharpen the criterion's bound first; only if it stays fuzzy, hide later steps behind a real context boundary like a hand-off.

What are the limitations of using negation in agent instructions?▼

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