writing-skills

Installation
SKILL.md

Writing Skills

A skill should help an agent make a better decision or produce a better result on a recurring task. Make it easy to select, useful when loaded alone, and no more demanding than the problem it addresses.

Loading this skill does not require a new skill, rewrite, test framework, subagent, or approval ceremony. For a review-only request, report findings and proposals without editing. Scale authoring and checks to the change.

1. Establish the Need and Scope

Read the current skill, relevant supporting files and project instructions, and nearby skill metadata before choosing a solution. Open neighboring bodies when ownership or boundaries need clarification, not as a full library sweep. When available, inspect actual missed loads, wrong outputs, or repeated user corrections. Do not invent a failure because a baseline happens to succeed.

Decide:

  • What improves? Name the recurring task, intended result, observed gap or explicit requirement, and important exceptions.
  • Where does it belong? Improve an existing skill when it already owns the trigger. Keep project-only rules in project instructions, session progress out of skills, and deterministic checks in existing automation when suitable. A separate skill needs a distinct selectable task, not just more detail within another workflow.
  • What is authorized? Separate an audit, a proposed design, and implementation. Ask only about unresolved choices that would materially change scope or behavior; do not reopen settled decisions.

For uncertain structure or portability choices, open authoring patterns and format notes. It distinguishes the open format from product-specific behavior; it is not a second mandatory checklist.

2. Design the Trigger Before the Body

Installs
48
First Seen
Oct 30, 2026