writing-for-agents

Write and structure skills, AGENTS.md, and CLAUDE.md documents for agent consumption.

4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/staticaland/skills --skill writing-for-agents-staticaland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/staticaland/skills/tree/main/plugins/skill-authoring/skills/writing-for-agents
Command: npx skills add https://github.com/staticaland/skills --skill writing-for-agents-staticaland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for agents often fail unpredictably: bloated files bury key steps, weak descriptions never trigger, and duplicated guidance drifts out of sync. This Skill provides a reference framework 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: Write descriptions and references whose wording controls when the agent reaches the material, with one trigger per branch. - Information hierarchy: Place content on the right tier — in-file steps, in-file reference, or disclosed reference behind a pointer — using progressive disclosure and co-location. - Completion criteria and splitting: End every step with a clear, demanding completion criterion, and split documents by sequence or invocation to prevent premature completion. - Skill mechanics: A companion file covers frontmatter, model-invoked versus user-invoked skills, and router skills. - Use Case: When authoring a new skill or editing an AGENTS.md, apply the pruning rules to remove no-op sentences, replace restatements with leading words, and keep a single source of truth for each behavior. ## Quick Start Ask the agent to review your SKILL.md or AGENTS.md using the writing-for-agents reference and tighten its description, structure, and pruning.

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, state what the material is, and list one trigger per distinct branch the document handles. Cut synonyms and identity the body already carries, since every word of an always-loaded description costs context on every turn.

How do I structure a SKILL.md or AGENTS.md file?▼

Order content by the information hierarchy: in-file steps first, in-file reference consulted on demand, then disclosed reference pushed to separate files behind context pointers. Inline what every branch needs and disclose what only some branches reach.

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 reach it, with zero context load.

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

Why does my agent ignore instructions in long documents?▼

Long documents cause sprawl: attention thins across excess lines even when every line is relevant. Disclose reference material behind pointers, prune no-op sentences the model already obeys by default, and keep each meaning in a single source of truth.