writing-for-agents

Write and structure documents that AI agents consume, including skills and AGENTS.md files.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill writing-for-agents-kunj-sharma03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/Kunj-Sharma03/agent-contextify/tree/main/skills-main/skills/productivity/writing-for-agents
Command: npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill writing-for-agents-kunj-sharma03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: agents skip instructions, rush steps, or ignore reference material. This Skill provides a systematic reference for writing agent-facing documents — skills, AGENTS.md, CLAUDE.md — so the agent follows the same process reliably on every run. ## Core Features & Use Cases - Context pointer design: Write descriptions and pointer lines whose wording controls when the agent reaches out-of-context material, with one trigger per branch. - Information hierarchy: Organize content into in-file steps, in-file reference, and disclosed reference behind pointers, using progressive disclosure and co-location to prevent sprawl. - Completion criteria and splitting: Define clear, demanding completion criteria for each step, and split documents by sequence or invocation to prevent premature completion. - Use Case: When authoring a new skill or editing an AGENTS.md file, apply the pruning rules (single source of truth, no-op detection, leading words) to cut token load while sharpening agent behavior. ## Quick Start Ask the agent to review your SKILL.md or AGENTS.md draft using the writing-for-agents guidance and suggest improvements to its pointers, structure, and completion criteria.

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?

A skill description is a context pointer: front-load the leading 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 an AGENTS.md or CLAUDE.md file?

Organize content along the information hierarchy: in-file steps first, in-file reference second, and disclosed reference pushed behind pointers into separate files. Keep each concept's definition, rules, and caveats co-located under one heading so the document reads like documentation written for the agent.

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, removing agent discovery entirely so only a human typing its name can invoke 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 on its own or another skill must reach it. Each split spends context or cognitive load, so the cut must earn it.

Why does my agent skip steps in my skill instructions?

Premature completion happens when a step's completion criterion is vague and later steps remain visible, pulling attention toward being done. Sharpen the criterion's bound first; if it stays fuzzy and the rush persists, hide later steps behind a real context boundary such as a hand-off or subagent dispatch.