writing-great-skills

Provides vocabulary and principles for writing and editing predictable AI skills.

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

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 a set of principles for structuring, invoking, and pruning skills so the agent follows the same process 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 (human-triggered, zero context load), including router skills for managing many user-invoked skills. - 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 a skill whose agent keeps rushing through 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 reference and identify failure modes like duplication, sprawl, or premature completion.

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 branch, and cut identity statements already covered in the body. Synonyms that rename a single branch are duplication and should be collapsed, since every word in a description adds context load.

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 so only the human can trigger it, trading discoverability for 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 post-completion steps tempt the agent to rush the current step, causing premature completion.

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

This 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 is irreducibly fuzzy and the rush is observed.

What is progressive disclosure in skill writing?▼

Progressive disclosure moves reference material out of SKILL.md into linked files behind context pointers, keeping the top of the file legible. Inline what every branch needs and disclose what only some branches reach, sharpening pointer wording if it fires unreliably.

Why should I avoid negative instructions in prompts?▼

Prohibitions drag the forbidden behavior into context and make it more available, not less, since the negation is a weak modifier the named concept overruns. State the positive target behavior instead, reserving prohibitions for hard guardrails paired with what to do.