writing-for-agents

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

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/kashman001/ai-workspace-template --skill writing-for-agents-kashman001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/kashman001/ai-workspace-template/tree/main/skills/writing-for-agents
Command: npx skills add https://github.com/kashman001/ai-workspace-template --skill writing-for-agents-kashman001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: agents miss referenced material, rush steps, or get buried under bloated files. This Skill provides a systematic reference for writing any document an agent consumes so the agent follows the same process reliably on every run. ## Core Features & Use Cases - Context pointer design: Rules for writing descriptions and pointer lines that front-load trigger words, cover one branch per trigger, and control when agents reach out-of-context material. - Information hierarchy and progressive disclosure: A ladder model (in-file steps, in-file reference, disclosed reference) for deciding what stays inline versus what moves behind a pointer, plus co-location and sprawl guidance. - Completion criteria and splitting: Techniques for writing checkable, exhaustive step completion criteria, and deciding when to split documents by sequence or invocation. - Use Case: When creating a new skill or editing an AGENTS.md file, apply the leading-words, pruning, and negation-avoidance rules to produce a lean document the agent follows deterministically. ## Quick Start Use the writing-for-agents skill to review and improve the skill file I am drafting.

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 agents trigger reliably?▼

Write the description as a context pointer: front-load the leading trigger word and list one trigger per distinct branch the document handles. Cut synonyms that rename a single branch and remove identity the body already carries, since every word of an always-loaded description costs context on every turn.

How do I structure an AGENTS.md or CLAUDE.md file for agents?▼

Structure it around an information hierarchy: keep primary steps in-file, push reference material behind context pointers, and co-locate each concept's definition, rules, and caveats under one heading. Prune duplication, stale lines, and no-op instructions the model already obeys by default.

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 the description from the agent's reach so only a human typing its name can invoke it.

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

Why should I avoid negative instructions in agent prompts?▼

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