writing-for-agents

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

Updated Jan 19, 2023
One-click install
npx skills add https://github.com/inkfin/dotfiles --skill writing-for-agents-inkfin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/inkfin/dotfiles/tree/main/dot_agents/skills/exact_writing-for-agents
Command: npx skills add https://github.com/inkfin/dotfiles --skill writing-for-agents-inkfin

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 principles that make agent-facing documents behave consistently across runs. ## Core Features & Use Cases - Context pointer design: Rules for writing skill descriptions and AGENTS.md pointers that reliably trigger the right material, with one trigger per branch and front-loaded leading words. - Information hierarchy: A ladder model (in-file steps, in-file reference, disclosed reference) plus progressive disclosure and co-location guidance to keep documents legible without hiding needed material. - Completion criteria and splitting: Techniques for sharpening step completion conditions, deciding when to split documents by sequence or invocation, and configuring model-invoked versus user-invoked skills. - Use Case: When authoring a new skill or editing an AGENTS.md file, consult this reference to prune no-op sentences, replace restatements with leading words, and structure frontmatter so the agent discovers the document at the right time. ## Quick Start Ask the agent to review your draft SKILL.md or AGENTS.md using the writing-for-agents principles and suggest concrete revisions.

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 word that triggers the skill, 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.

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. 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 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.

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; if the rush persists, hide later steps behind a real context boundary like a subagent dispatch.

Should agent instructions use negative rules like 'do not do X'?

Negation drags the forbidden behavior into context and makes it more available, so prompt the positive target behavior instead. Reserve prohibitions for hard guardrails that cannot be phrased positively, and pair them with the desired action.