writing-for-agents

Guides writing and editing of skills, AGENTS.md, and CLAUDE.md documents for agents.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill writing-for-agents-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/writing-for-agents
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill writing-for-agents-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: bloated context, weak triggers that never fire, duplicated guidance, and instructions the model already follows by default. This Skill provides a systematic framework for writing any document an agent consumes so it behaves predictably on every run. ## Core Features & Use Cases - Context pointer design: Craft descriptions and references that reliably trigger the right material at the right branch, with front-loaded leading words and one trigger per branch. - Information hierarchy management: Apply progressive disclosure, co-location, and pruning to decide what stays inline versus what moves behind a pointer into disclosed reference files. - Completion criteria and splitting: Define clear, demanding completion criteria for steps and decide when to split documents by sequence or invocation. - Use Case: When authoring a new skill or editing an AGENTS.md file, use this Skill to sharpen the description trigger, push branch-specific detail into referenced files like SKILL-MECHANICS.md, and prune no-op sentences that add load without changing behavior. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents guidance to sharpen triggers, prune redundancy, and fix the information hierarchy.

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 agent discovery?▼

Keep the description short and specific about the requested operation, putting the trigger first. Avoid broad capability lists that attract unrelated tasks and get truncated in large catalogs; a database migration skill should mention creating or reviewing migrations, not every query.

How to structure an AGENTS.md file for AI coding agents?▼

Keep only rules needed across repository tasks in AGENTS.md, and route service boundaries to architecture docs, schema work to data docs, and deployment to release docs. Do not require a full repository map before an unrelated small edit.

When should I split a skill into multiple files?▼

Split by sequence when later steps tempt the agent to rush the current one, and split by invocation when distinct workflows deserve separate referenced branches. Keep a short self-contained skill inline and push substantial distinct workflows into referenced files loaded only when the pointer fires.

What is progressive disclosure in agent skill writing?▼

Progressive disclosure moves material down the information hierarchy, out of the main file and behind a context pointer, so the top stays legible. Inline what every branch needs and push behind a pointer what only some branches reach.

Why do agents ignore instructions in long documents?▼

Long documents cause sprawl: attention thins across excess lines even when every line is relevant. The fix is disclosing reference material behind pointers and splitting by branch or sequence so each path carries only what it needs.

Should I use negative instructions like 'do not do X' in prompts?▼

Negation drags the forbidden behavior into context and makes it more available, so prompt the positive target behavior instead. Reserve prohibitions for hard guardrails you cannot phrase positively, and pair them with the positive target.