writing-great-skills

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

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ninthday/skills-base --skill writing-great-skills-ninthday
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/ninthday/skills-base/tree/main/archived-skills/writing-great-skills/20260913T073113Z
Command: npx skills add https://github.com/ninthday/skills-base --skill writing-great-skills-ninthday

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing agent skills that behave consistently is hard: descriptions misfire, instructions bloat, and agents rush steps or ignore guidance. This Skill supplies a shared vocabulary and set of principles for designing, structuring, and pruning skills so they behave predictably on every run. ## Core Features & Use Cases - Invocation Design: Explains the trade-off between model-invoked skills (agent-discoverable, with context load) and user-invoked skills (zero context load, human-triggered), including router skills for managing many user-invoked ones. - Information Hierarchy: Defines how to arrange steps and reference material across SKILL.md and disclosed files using progressive disclosure and context pointers. - Failure Mode Diagnosis: Catalogs failure modes such as premature completion, duplication, sediment, sprawl, no-ops, and negation, each paired with its cure. - Use Case: When editing an existing skill that the agent triggers unreliably, consult this reference to sharpen the description's trigger wording, collapse duplicated branches, and push rarely needed reference material behind a pointer. ## 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 agent invocation?

Front-load the skill's leading word and list one trigger per distinct branch, since every word adds context load. Collapse synonym triggers that rename the same branch, and cut identity statements already covered in the skill body.

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, paying permanent context load. A user-invoked skill sets disable-model-invocation so only the human typing its name can reach it, costing zero context load.

When should I split a skill into multiple skills?

Split by invocation when you have a distinct leading word that should trigger a model-invoked skill on its own. Split by sequence when visible upcoming steps tempt the agent into premature completion of the current step.

Why does my agent skip steps or finish tasks too early?

This is premature completion, caused by vague completion criteria and visible post-completion steps pulling attention forward. Sharpen the completion criterion first; only hide later steps via a context boundary if the criterion stays fuzzy and rushing persists.

Should I use negative instructions like 'do not do X' in a skill?

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 paired with what to do instead.