writing-for-agents

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

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill writing-for-agents-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.agents/skills/writing-for-agents
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill writing-for-agents-ab0umar

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 cause agents to stop early. This Skill provides a systematic reference for writing any agent-consumed document so the agent behaves predictably on every run. ## Core Features & Use Cases - Context pointer design: Rules for writing skill descriptions and AGENTS.md lines that reliably trigger, including front-loading leading words and one trigger per branch. - Information hierarchy: A framework for placing content as in-file steps, in-file reference, or disclosed reference behind pointers, with progressive disclosure and co-location guidance. - Completion criteria and pruning: Techniques for writing checkable, exhaustive step boundaries, plus disciplines for removing duplication, stale caches, and no-op instructions. - Use Case: When creating a new skill or editing CLAUDE.md, apply these rules to decide what to inline, what to disclose into separate files, and how to word the description so the agent fires it at the right time. ## Quick Start Use the writing-for-agents skill to review and improve the description and structure of my new skill's SKILL.md file.

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 does the triggering work, list one trigger per distinct branch the document handles, and cut identity the body already carries. Every word of an always-loaded description costs context on every turn, so prune it harder than the body.

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 for discoverability. 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 one skill document into two?▼

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

Why does my agent stop a task before it is finished?▼

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 hide later steps across a real context boundary if the rush persists.

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

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