writing-for-agents

Write skills, AGENTS.md, and CLAUDE.md documents that agents follow predictably.

9|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Yassimba/loom --skill writing-for-agents-yassimba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/Yassimba/loom/tree/main/skills/writing-for-agents
Command: npx skills add https://github.com/Yassimba/loom --skill writing-for-agents-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often produce inconsistent behavior: agents skip steps, miss reference material, or rush to premature completion. This Skill provides a reference framework for writing any agent-consumed document so the agent follows the same process every run. ## Core Features & Use Cases - Context pointer design: Rules for writing descriptions and pointer lines that reliably trigger the agent to reach out-of-context material at the right branch. - Information hierarchy and progressive disclosure: A ladder model (in-file steps, in-file reference, disclosed reference) for deciding where each piece of content lives, plus co-location and sprawl guidance. - Completion criteria and splitting: Techniques for writing checkable, exhaustive step completion criteria, and criteria for when to split documents by sequence or invocation. - Use Case: When authoring a new skill or editing an AGENTS.md file, apply the leading-word, pruning, and negation-avoidance rules to produce a shorter document the agent follows more reliably. ## Quick Start Use the writing-for-agents skill to review and rewrite my AGENTS.md so the agent follows it consistently.

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 an AI agent will trigger reliably?

Write the description as a context pointer: front-load the leading trigger word and list one trigger per distinct branch the skill 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 file so agents follow it?

Order content by the information hierarchy: in-file steps first, in-file reference second, and disclosed reference pushed behind context pointers. Keep each concept's definition, rules, and caveats co-located under one heading, and end every step with a clear, checkable completion criterion.

When should I split one skill into multiple skills?

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.

What is the difference between model-invoked and user-invoked skills?

A model-invoked skill keeps its description visible 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.

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 that cannot be phrased positively.