writing-great-skills

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

3|1|Updated May 29, 2026
One-click install
npx skills add https://github.com/mambo-wang/CodingHub --skill writing-great-skills-mambo-wang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/mambo-wang/CodingHub/tree/main/.codebuddy/skills/writing-great-skills
Command: npx skills add https://github.com/mambo-wang/CodingHub --skill writing-great-skills-mambo-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing skills for AI agents often produces bloated, duplicated, or unreliable instructions that cause inconsistent agent behavior. This Skill supplies a shared vocabulary and decision framework for structuring, invoking, and pruning skills so agents behave predictably on every run. ## Core Features & Use Cases - Invocation Design: Guidance on choosing between model-invoked and user-invoked skills, including the trade-offs between context load and cognitive load, and when to use router skills. - Information Hierarchy: A ladder model for arranging steps, in-file reference, and disclosed reference files (like GLOSSARY.md) behind context pointers via progressive disclosure. - Failure Mode Diagnosis: Named failure modes — premature completion, duplication, sediment, sprawl, no-op, and negation — each paired with its cure. - Use Case: When editing an existing skill that has grown too long, use this reference to identify sprawl and sediment, then push reference material behind context pointers and prune no-op lines. ## Quick Start Ask the agent to review your SKILL.md using the writing-great-skills principles and suggest improvements to its description, structure, and pruning.

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-invocation only when the agent or another skill must reach it autonomously, accepting the context load of an always-loaded description. If it only ever fires by hand, set disable-model-invocation 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 use.

Why does my agent rush through skill steps?▼

Rushing is premature completion, caused by vague completion criteria and visible upcoming steps pulling attention forward. Sharpen the completion criterion first; only hide later steps by splitting the sequence if the criterion stays fuzzy and the rush persists.

When should I split one skill into multiple skills?▼

Split by invocation when you have a distinct leading word that should trigger a model-invoked skill independently. Split by sequence when visible post-completion steps tempt the agent to rush the current step.