pocock-writing-great-skills

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

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/l0lxl0lw/dotfiles --skill pocock-writing-great-skills-l0lxl0lw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pocock-writing-great-skills
Source: https://github.com/l0lxl0lw/dotfiles/tree/main/ai/shared/skills/mattpocock/pocock-writing-great-skills
Command: npx skills add https://github.com/l0lxl0lw/dotfiles --skill pocock-writing-great-skills-l0lxl0lw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing effective skills for AI agents is hard: descriptions fail to trigger, instructions bloat, and agents rush steps or ignore rules. This Skill supplies a shared vocabulary and a set of design principles that make a skill behave predictably on every run. ## Core Features & Use Cases - Invocation Design: Explains the trade-off between model-invoked skills (agent-discoverable, paying context load) and user-invoked skills (human-triggered, paying cognitive load), including router skills. - Information Hierarchy: Defines how to arrange steps and reference material across SKILL.md and disclosed files via progressive disclosure and context pointers. - Failure-Mode Diagnosis: Catalogs predictable failure modes — premature completion, duplication, sediment, sprawl, no-ops, and negation — with the specific lever that cures 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 suggest improvements to its description and structure.

Frequently Asked Questions about pocock-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 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.

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.

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. 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. First sharpen the completion criterion to be checkable; only if it stays fuzzy and the rush persists, split the sequence to hide later steps.

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 that cannot be phrased positively.