writing-for-agents

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

28|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/NauelG/astro-blocks --skill writing-for-agents-nauelg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/NauelG/astro-blocks/tree/main/.agents/skills/writing-for-agents
Command: npx skills add https://github.com/NauelG/astro-blocks --skill writing-for-agents-nauelg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: weak descriptions never trigger, bloated files dilute attention, and vague steps invite premature completion. This Skill provides a reference framework for writing any document an agent consumes so it behaves predictably on every run. ## Core Features & Use Cases - Context pointer design: Rules for writing skill descriptions and AGENTS.md lines that reliably trigger the right material at the right branch. - Information hierarchy: A ladder model (in-file steps, in-file reference, disclosed reference) plus progressive disclosure and co-location guidance to fight document sprawl. - Completion criteria and splitting: Techniques for sharpening step boundaries, deciding when to split documents by sequence or invocation, and using leading words instead of negation. - Use Case: When authoring a new skill or editing an AGENTS.md file, apply the pruning, duplication, and no-op tests to keep every line earning its context load. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents guidance and suggest improvements to its description 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 good skill description for an AI agent?▼

Front-load the leading word that triggers the skill, list one trigger per distinct branch the document handles, and cut any identity the body already carries. The description is always loaded, so every word must earn its context cost.

How should I structure an AGENTS.md or CLAUDE.md file?▼

Treat it as a set of context pointers: each line names out-of-context material and the conditions for reaching it. Keep always-loaded lines minimal, push detail into referenced docs, and prune lines that restate what the environment already shows.

When should I split a skill into multiple skills?▼

Split by sequence when visible later steps tempt the agent to rush the current one, or 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 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 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. State the positive target behavior instead so attention lands on what to do.