writing-for-agents

Guides writing and structuring documents that agents consume, including skills and AGENTS.md files.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nseng-ai/ns --skill writing-for-agents-nseng-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/nseng-ai/ns/tree/main/.agents/skills/writing-for-agents
Command: npx skills add https://github.com/nseng-ai/ns --skill writing-for-agents-nseng-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for 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 agent-consumed document — skills, AGENTS.md, CLAUDE.md, or pointer-reached docs — so the agent follows the same process reliably every run. ## Core Features & Use Cases - Context pointer design: Rules for writing descriptions and pointer lines that front-load trigger words, carry one trigger per branch, and control when material gets loaded. - 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 writing checkable, demanding step boundaries and deciding when to split documents by sequence or invocation. - Skill mechanics reference: Companion file SKILL-MECHANICS.md covers frontmatter, model-invoked vs user-invoked skills, and router skills. - Use Case: When authoring a new agent skill, use this reference to write a description that triggers on the right branches, keep the body lean by disclosing reference material behind pointers, and choose the correct invocation mode. ## Quick Start Ask the agent to apply the writing-for-agents reference to review and improve the SKILL.md file you are currently drafting.

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?

Write the description as a context pointer: front-load the leading trigger word, 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 to structure a SKILL.md file for agents?

Organize content on an information hierarchy: in-file steps first, in-file reference second, and disclosed reference pushed to separate files behind pointers. End every step with a clear, demanding completion criterion, and co-locate each concept's definition, rules, and caveats under one heading.

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

A model-invoked skill keeps an agent-facing description so the agent and other skills can trigger it autonomously, paying permanent context load. A user-invoked skill sets disable-model-invocation: true, so only a human typing its name can fire it, costing zero context load but requiring the human to remember it.

When should I split a skill into multiple documents?

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

Why does my agent ignore instructions in AGENTS.md?

Common causes are weakly worded pointers, no-op instructions the model already follows by default, and negations that activate the forbidden behavior. Sharpen pointer wording, delete sentences that do not change default behavior, and state positive target behaviors instead of prohibitions.