writing-great-skills

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

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill writing-great-skills-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/writing-great-skills
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill writing-great-skills-mst-software-vn

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, splitting, 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, trading context load against cognitive load. - Information Hierarchy: A three-rung ladder (steps, in-file reference, disclosed reference) with progressive disclosure rules for keeping SKILL.md legible. - Failure Diagnosis: Named failure modes — premature completion, duplication, sediment, sprawl, and no-ops — with concrete fixes for each. - Use Case: When editing a skill whose agent keeps skipping steps, consult the failure modes section to sharpen completion criteria or split the sequence to hide post-completion steps. ## Quick Start Ask the agent to review your SKILL.md using the writing-great-skills principles and identify no-ops, duplication, and sprawl.

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.md description?▼

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.

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.

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 context load every turn. A user-invoked skill sets disable-model-invocation, making it reachable only by the human typing its name, with zero context load.

Why does my agent skip steps when running a skill?▼

This is premature completion, caused by vague completion criteria or visible post-completion steps pulling attention forward. First sharpen the completion criterion to be checkable; only if it stays fuzzy, split the sequence to hide later steps.

What are the limitations of progressive disclosure in skills?▼

Disclosed reference behind a context pointer only loads when the pointer fires, and weak pointer wording makes retrieval unreliable. Inline material every branch needs, and sharpen pointer wording before pulling must-have content back inline.