writing-for-agents

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

3|1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/DuckKota/my-opencode-setup --skill writing-for-agents-duckkota
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/DuckKota/my-opencode-setup/tree/main/src/skills/writing-for-agents
Command: npx skills add https://github.com/DuckKota/my-opencode-setup --skill writing-for-agents-duckkota

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: weak descriptions never trigger, bloated files bury key steps, and vague completion criteria let agents stop early. This Skill provides a reference of writing levers that make agent-facing documents behave consistently across runs. ## Core Features & Use Cases - Context pointer design: Write descriptions and pointer lines with front-loaded trigger words and one trigger per branch so agents reach material reliably. - Information hierarchy management: Apply progressive disclosure, co-location, and splitting rules to keep documents legible and prevent sprawl. - Completion criteria and pruning: Define clear, demanding done-conditions per step and prune duplication, stale caches, and no-op instructions. - Use Case: When authoring a new skill or editing an AGENTS.md file, consult this reference to decide invocation mode, structure steps versus reference material, and sharpen leading words. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents guidance 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, list one trigger per distinct branch the document handles, and cut anything the body already states. The description is always loaded, so every word must earn its context cost.

When should I split a skill into multiple files?▼

Split by sequence when visible later steps tempt the agent to rush the current one, or 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 the difference between model-invoked and user-invoked skills?▼

A model-invoked skill keeps a description so the agent 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.

Why does my agent stop a task before finishing it?▼

Premature completion usually comes from a vague completion criterion combined with visible post-completion steps pulling attention forward. Sharpen the done-condition first; only hide later steps behind a real context boundary if the rush persists.

Should I avoid negative instructions in agent prompts?▼

Yes. Negation drags the forbidden behavior into context and makes it more available. State the positive target behavior instead, reserving prohibitions for hard guardrails paired with the positive instruction.