IRON LAW: Keep each skill's responsibility explicit; any skill dependency must have a declared one-way contract and a defined missing-dependency outcome.

Skill Conventions

Apply these conventions to the complete skill package.

Workflow

• Establish the requested capability, target package, authorized changes and unresolved choices.
• Preserve existing supported metadata and invocation/authorization behavior; choose the smallest useful package structure.
• Write a discriminating description, essential constraints and conditional reference pointers.
• Verify package validity, referenced resources, realistic task behavior and any changed executable helpers.

Frontmatter

For new repository skills, default to two keys: name and description, with quoted string values (no block scalars >-, |, |+). The examples below describe this repository default, not the complete supported skill format.

When updating an existing skill, preserve supported metadata and agents/openai.yaml UI, policy and dependency configuration, including explicit-only invocation. Do not delete or regenerate them merely to match the new-package default. Format or invocation migrations require an explicit task need and resolved scope; uncertainty about the intended behavior requires asking before changing it. If another active authoring policy conflicts with preserving the existing format or behavior, surface that conflict and ask before a destructive cleanup rather than silently discarding configuration.