writing-great-skills

Provides vocabulary and principles for writing predictable, well-structured AI agent skills.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/j172/bid --skill writing-great-skills-j172
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/j172/bid/tree/main/agent/skills/writing-great-skills
Command: npx skills add https://github.com/j172/bid --skill writing-great-skills-j172

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing skills for AI agents often produces bloated, unreliable instructions that fire inconsistently or steer the agent unpredictably. This Skill supplies a shared vocabulary and decision framework for structuring, invoking, and pruning skills so the agent behaves predictably on every run. ## Core Features & Use Cases - Invocation Design: Guidance on choosing between model-invoked and user-invoked skills, trading context load against cognitive load, and using router skills when user-invoked skills multiply. - Information Hierarchy: A ladder model for arranging steps, in-file reference, and disclosed reference behind context pointers, with progressive disclosure and co-location principles. - Failure Mode Diagnosis: Named failure modes — premature completion, duplication, sediment, sprawl, no-op, and negation — each paired with its cure, plus a full glossary in GLOSSARY.md. - Use Case: When editing an existing skill that the agent triggers inconsistently, use this Skill to sharpen the description's trigger wording, collapse duplicated branches, and push excess reference material behind context pointers. ## Quick Start Ask the agent to review your SKILL.md using the writing-great-skills principles and suggest improvements to its description and structure.

Frequently Asked Questions about writing-great-skills

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 skill's leading word, list one trigger per distinct branch, and cut identity statements already covered in the body. Every word in a model-invoked description adds permanent context load, so prune it harder than the body text.

When should a skill be model-invoked vs user-invoked?

Choose model-invoked only when the agent or another skill must reach it autonomously, since its description costs context load every turn. If it only ever fires by hand, strip the description to make it user-invoked and pay zero context load.

What is progressive disclosure in skill writing?

Progressive disclosure moves reference material out of SKILL.md into linked files reached via context pointers, keeping the top of the file legible. Inline what every branch needs and disclose what only some branches reach.

Why does my agent skip steps or finish tasks early?

This is premature completion, caused by vague completion criteria and visible upcoming steps pulling attention forward. Sharpen the completion criterion first; only split the sequence to hide later steps if the criterion is irreducibly fuzzy and the rush is observed.

Should I use negative instructions like 'don't do X' in prompts?

Avoid negation because naming the forbidden behavior makes it more available to the model, not less. State the positive target behavior instead, reserving prohibitions for hard guardrails you cannot phrase positively.