oncokb-writing-for-agents

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

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/oncokb/oncokb-skills --skill oncokb-writing-for-agents-oncokb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oncokb-writing-for-agents
Source: https://github.com/oncokb/oncokb-skills/tree/main/skills/oncokb-writing-for-agents
Command: npx skills add https://github.com/oncokb/oncokb-skills --skill oncokb-writing-for-agents-oncokb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents written for AI agents often fail unpredictably: bloated files bury key steps, weak descriptions never trigger, and duplicated rules drift 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: Rules for writing skill descriptions and AGENTS.md lines that trigger reliably, with front-loaded leading words and one trigger per branch. - Information hierarchy: A ladder model (in-file steps, in-file reference, disclosed reference) plus progressive disclosure and co-location to keep documents legible. - Completion criteria and splitting: Guidance on writing checkable, exhaustive step completion criteria and deciding when to split documents by sequence or invocation. - Use Case: When creating a new agent skill or editing a CLAUDE.md file, apply the pruning rules (single source of truth, no-op detection, negation avoidance) to produce a tighter, more predictable document. ## Quick Start Ask the agent to review your draft SKILL.md or AGENTS.md using the writing-for-agents guidelines and suggest improvements.

Frequently Asked Questions about oncokb-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 word that triggers it, list one trigger per distinct branch the skill handles, and cut any identity the body already carries. Every word stays loaded in context, so prune aggressively.

How to structure an AGENTS.md or CLAUDE.md file?▼

Order content by the information hierarchy: in-file steps first, in-file reference consulted on demand, and disclosed reference pushed behind pointers to separate files. Keep each concept's definition, rules, and caveats co-located under one heading.

When should I split a skill into multiple skills?▼

Split by sequence when visible later steps tempt the agent to rush the current one, or by invocation when a distinct trigger word should fire a skill on its own. Each split spends context or cognitive load, so the cut must earn it.

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 so only a human typing its name can reach it, costing zero context load.

Why should I avoid negative instructions in agent prompts?▼

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.