skill-creator

To standardize frontmatter metadata across a skill catalog, enforce a canonical structure for descriptions and trigger boundaries. This skill applies progressive-disclosure guidance and validates compliance using shared catalog tooling.

Defining trigger boundaries requires drafting the frontmatter description, "Use this skill when" conditions, and "Do not use this skill when" exclusions first. This tightens scope before adding support files and validating with catalog tooling.

To upgrade an existing skill package for discoverability, refine its metadata, evals, and trigger boundaries. This skill enforces catalog compliance and alignment with shared tooling to ensure the package is consistently structured.

Yes, shared validation tooling is required to maintain a skill directory. This skill mandates validation to ensure frontmatter compliance, boundary definitions, and overall catalog discoverability after creating or refining packages.

You should not use a skill standardization process if your package only needs ad-hoc metadata without canonical frontmatter or trigger boundaries. This approach enforces strict directory structure, evals, and shared tooling validation.

To build a catalog skill package, add only the support files that genuinely improve execution after defining frontmatter boundaries. This ensures the directory structure remains lean and passes shared tooling validation.