writing-great-skills

Analyzes skill documents to improve clarity and reduce ambiguity.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill writing-great-skills-ian-pascoe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-great-skills
Source: https://github.com/ian-pascoe/dotfiles-chezmoi/tree/main/dot_agents/skills/writing-great-skills
Command: npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill writing-great-skills-ian-pascoe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you write and edit skills that are easier for an AI to follow, easier to maintain, and more predictable in practice.

Core Features & Use Cases

  • Explains how invocation, information hierarchy, and progressive disclosure shape a skill's structure.
  • Shows how to reduce duplication, no-ops, sediment, and sprawl before they weaken a skill.
  • Guides decisions for splitting skills, choosing leading words, and writing stronger completion criteria.
  • Useful when drafting a new skill, refining an existing one, or reviewing a skill for clarity and reliability.

Quick Start

Ask me to review your skill draft and rewrite it to be clearer, leaner, and more predictable.

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 agent-facing documentation that behaves predictably?

To write predictable agent-facing documentation, analyze your skill instructions to reduce ambiguity. Focus on structuring the information hierarchy, applying progressive disclosure, and writing clear completion criteria.

What is progressive disclosure in prompt engineering?

Progressive disclosure in prompt engineering is a structuring technique that organizes information hierarchy so an agent receives only necessary details, reducing duplication and sediment before they weaken skill performance.

How do I review an existing skill to reduce ambiguity?

Review an existing skill to reduce ambiguity by checking invocation rules, leading words, completion criteria, and pruning requirements. This process ensures instructions remain clear, relevant, and maintainable.

When should I split AI skills into separate instructions?

You should split AI skills into separate instructions when sprawl, duplication, or no-ops weaken the operational guidance. Splitting helps maintain leaner, more predictable agent-facing documentation.

What are leading words and how do they affect skill invocation?

Leading words are specific terms placed at the beginning of skill instructions to trigger invocation. Choosing stronger leading words ensures the agent correctly identifies and follows the intended operational guidance.

What causes no-ops and sediment in AI operational guidance?

No-ops and sediment in AI operational guidance occur when redundant instructions or accumulated unused details clutter the documentation. Pruning these requirements improves clarity, relevance, and overall maintenance.