writing-great-skills

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

3|Updated Nov 8, 2014
One-click install
npx skills add https://github.com/mintuz/.dotfiles --skill writing-great-skills-mintuz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/mintuz/.dotfiles/tree/main/agents/.agents/skills/writing-great-skills
Command: npx skills add https://github.com/mintuz/.dotfiles --skill writing-great-skills-mintuz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing effective AI skills is hard: descriptions fail to trigger, instructions bloat, and agents behave inconsistently across runs. This Skill provides a shared vocabulary and set of principles for designing, structuring, and pruning skills so the agent follows the same process every run. ## Core Features & Use Cases - Invocation Design: Guidance on choosing between model-invoked and user-invoked skills, and how to write trigger-rich descriptions. - Information Hierarchy: A ladder model for arranging steps and reference material, including progressive disclosure into linked files like GLOSSARY.md. - Failure Mode Diagnosis: Named failure modes (premature completion, duplication, sediment, sprawl, no-op, negation) with concrete cures for each. - Use Case: When reviewing a skill that fires unreliably or runs too long, use this reference to diagnose whether the issue is a weak description, sprawl, or a vague completion criterion, then apply the matching fix. ## 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 and list one trigger per branch, since every word adds context load. Collapse synonym triggers that rename a single 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 its description so the agent and other skills can fire it, paying permanent context load. A user-invoked skill sets disable-model-invocation: true, making it reachable only by the human typing its name, with 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 AI skill rush through steps before finishing?

This is premature completion, caused by a vague completion criterion combined with visible upcoming steps. First sharpen the criterion to be checkable and exhaustive; only hide later steps by splitting if the criterion is irreducibly fuzzy and the rush persists.

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

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