What problem does it solve? Teams maintaining a collection of agent skills struggle to keep every SKILL.md consistent with house conventions: thin router bodies, layered references, lint-clean product-agnostic content, and behavior-preserving refactors. This Skill turns a brief into a convention-compliant skill, or conservatively splits an oversized SKILL.md, and refuses to hand back output that fails the lint and completeness gate. ## Core Features & Use Cases - Author mode: Runs a short interview (goal, trigger phrases, tracker interaction, chain membership), drafts a router-style SKILL.md from templates, scaffolds references/, and optionally a repo-local stub. - Split mode: Refactors an existing SKILL.md into references/ files word-for-word without changing behavior, refusing skills under ~150 lines or with no dominant template to extract. - Hard quality gate: Enforces scripts/lint.sh, split-mode completeness checks (no lost code blocks or lines, unchanged description, safety boundary loaded on every run), and a readability test before reporting. - Use Case: A maintainer says "create a skill for generating release notes" and receives a fully scaffolded skills/ot-release-notes/ directory with frontmatter, router body, references, and passing lint results. ## Quick Start Ask the agent to create a new skill from your brief, for example: use ot-create-skill to create a skill for triaging incoming bug reports.
