Creating Skills

Create, revise, migrate, or audit a skill from its intent, required outcome, and only the hard constraints that define acceptable completion or remain under user authority. The result is either a prioritized read-only audit or a self-contained skill package with structural validation, appropriately scoped behavioral evidence, and separate trigger and installation checks.

Skills produced here follow the Agent Skills format: a directory with a SKILL.md (frontmatter plus body) and optional references/, assets/, and scripts/. Canonical frontmatter uses only name, description, license, compatibility, and metadata. Read references/portability.md when authoring frontmatter, choosing an install location, or making a harness-specific claim.

An independent reviewer must not have participated in the authoring discussion or produced the artifact under review. One independent grader inspects each matched case; a different fresh-context reviewer performs the final package review. If the current environment cannot start those independent contexts, prepare a self-contained handoff for a separate session and keep the affected grade or review unverified until that session completes it. Do not substitute the author's own review.

Workflow

Creating a new skill starts at step 1. Auditing, updating, or migrating an existing skill starts at step 0. A read-only audit ends at step 0; approved changes continue through the remaining workflow.

0. Audit an existing skill

Have a separate fresh-context agent that has not participated in the current authoring work read the whole package and the host repository's instructions. Give it the skill, the review checklist, and the stated intent without the author's conclusions. Have it apply references/review-checklist.md top to bottom, then present a prioritized fix list where each item names the problem, impact, and change risk.

Read-only completion: deliver the evidence-backed review, prioritized recommendations, and final verdict without changing files. The execution ends there. Revision begins only in a separate user-authorized request.

Change completion: the user has approved the material fix scope, including any authority or taste decisions that stay with them. Continue at step 1.