writing-for-agents

Write and structure documents that agents consume, including skills and AGENTS.md files.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill writing-for-agents-sevwren
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/SevWren/Daily-Motivation-Brain-Helper/tree/main/.agents/skills/writing-for-agents
Command: npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill writing-for-agents-sevwren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: agents skip instructions, rush steps, or miss reference material. This Skill provides a systematic reference for writing agent-facing documents — skills, AGENTS.md, CLAUDE.md — so the agent follows the same process reliably on every run. ## Core Features & Use Cases - Context pointer design: Rules for writing descriptions and pointers that trigger reliably, with front-loaded leading words and one trigger per branch. - Information hierarchy guidance: A ladder model (in-file steps, in-file reference, disclosed reference) for deciding what to inline versus push behind a pointer via progressive disclosure. - 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 authoring a new skill or editing an AGENTS.md file, consult this reference to prune no-op instructions, eliminate duplication, choose leading words, and decide between model-invoked and user-invoked skill mechanics. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents reference to sharpen its pointers 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 skill description that triggers 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 that rename a single branch and identity the body already carries, since every word of an always-loaded pointer 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 invoke it, costing zero context load but requiring the human to remember it exists.

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 leading word should trigger a skill on its own or another skill must reach it. Splitting spends context or cognitive load, so the cut must earn it.

What is progressive disclosure in agent documentation?▼

Progressive disclosure moves reference material out of the main file and behind a context pointer, loaded only when the pointer fires. Inline what every branch needs and disclose what only some branches reach, keeping the top of the document legible and protecting the information hierarchy.

Why should I avoid negative instructions in prompts for agents?▼

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.