writing-great-skills

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

1|Updated Apr 25, 2025
One-click install
npx skills add https://github.com/Gabr1elaugus700/WorkaPool --skill writing-great-skills-gabr1elaugus700
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/Gabr1elaugus700/WorkaPool/tree/main/.agents/skills/writing-great-skills
Command: npx skills add https://github.com/Gabr1elaugus700/WorkaPool --skill writing-great-skills-gabr1elaugus700

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing skills for AI agents often produces bloated, unreliable instructions that fire inconsistently or steer the agent unpredictably. This Skill supplies a shared vocabulary and decision framework for structuring, invoking, and pruning skills so the agent behaves the same way 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 a router skill. - Information Hierarchy: A ladder model for arranging steps, in-file reference, and disclosed reference behind context pointers, with progressive disclosure and co-location rules. - Failure Mode Diagnosis: Named failure modes — premature completion, duplication, sediment, sprawl, no-op, and negation — each paired with its cure, plus a full glossary in GLOSSARY.md. - Use Case: When editing an existing skill that the agent triggers inconsistently, consult this reference to sharpen the description's trigger wording, collapse duplicated branches, and push excess reference material behind pointers. ## Quick Start Ask the agent to review your skill file 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 synonyms that rename a single branch, and cut identity statements already covered in the body.

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 permanent context load of an always-loaded description. If it only ever fires by hand, set disable-model-invocation and pay no context load.

What is progressive disclosure in skill writing?

Progressive disclosure moves reference material out of SKILL.md into linked files reached by context pointers, keeping the top of the file legible. Inline what every branch needs and disclose what only some branches reach.

Why does my agent skip steps or finish tasks early?

This is premature completion, caused by vague completion criteria and visible upcoming steps pulling attention forward. Sharpen the completion criterion first; only split the sequence to hide later steps if the criterion is irreducibly fuzzy and rushing is observed.

Should I use negative instructions like 'don't do X' in prompts?

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

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 on its own, or by sequence when visible upcoming steps cause the agent to rush the current one. Each split spends context load or cognitive load, so the cut must earn it.