What problem does it solve? Authors of computational-biology skills repeatedly re-derive the same SKILL.md structure, frontmatter rules, and section conventions, leading to inconsistent skills that fail validation or route poorly during skill selection. ## Core Features & Use Cases - Canonical frontmatter template: Documents the allowed keys (name, description, license, allowed-tools), the kebab-case naming rule, and the 350-character description cap enforced by the toolkit linter. - Structured body scaffold: Provides ready-made sections for Overview, Decision Tree, Quick Start, Progressive Depth (basic/intermediate/advanced), Verification Checklist, Common Pitfalls, and See also cross-references. - Companion directory conventions: Includes README guidance for references/, scripts/, checks/, and assets/ so authors know what belongs in each on-demand resource directory. - Use Case: A bioinformatician adding a new scanpy or scVI skill to the scio catalog copies this template, renames the placeholder to a kebab-case identifier, fills in the sections, and validates with quick_validate.py before committing. ## Quick Start Copy the templates/skill directory to a new kebab-case skill folder, replace SKILL_IDENTIFIER with the real name, fill in the description and body sections, then run the quick_validate.py script to confirm it passes.