writing-for-agents

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

2|Updated May 12, 2026
One-click install
npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill writing-for-agents-tajo9128
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-for-agents
Source: https://github.com/tajo9128/BioDockify-Pharma-AI/tree/main/.agents/skills/writing-for-agents
Command: npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill writing-for-agents-tajo9128

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: weak descriptions never trigger, bloated files bury key steps, and vague completion criteria cause agents to stop early. This Skill provides a systematic reference 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: Rules for writing skill descriptions and AGENTS.md lines that front-load trigger words and list distinct branches so agents reach material reliably. - Information hierarchy and progressive disclosure: A framework for deciding what stays inline, what moves behind a pointer, and when to split documents by sequence or invocation. - Completion criteria and pruning: Guidance on writing checkable, exhaustive step boundaries, plus disciplines for removing duplication, no-op instructions, and stale content. - Use Case: When authoring a new skill, use this reference to write a description that triggers on the right prompts, structure the body with clear steps, and decide between model-invoked and user-invoked invocation via the companion SKILL-MECHANICS.md file. ## Quick Start Ask the agent to review your draft skill or AGENTS.md file using the writing-for-agents guidelines 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 trigger word, list one trigger per distinct branch the skill handles, and cut any identity the body already carries. The description is always loaded in context, so every word must earn its place by improving when the agent reaches the skill.

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, at the cost of permanent context load. A user-invoked skill sets disable-model-invocation: true, removing agent access entirely so only a human typing its name can trigger 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 deserves its own model-invoked skill. Each split spends context or cognitive load, so the cut must earn it.

What is progressive disclosure in agent documentation?

Progressive disclosure moves reference material out of the main file and behind a context pointer so it loads only when needed. Inline what every branch needs and disclose what only some branches reach, keeping the top-level document legible.

Why should I avoid negative instructions in prompts for agents?

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, reserving prohibitions for hard guardrails paired with a positive instruction.