skill-creator

To create a KiloCode skill, you scaffold a SKILL.md file under .kilo/skills/<skill-name>/ with YAML frontmatter enforcing the name and description fields. This standardizes skill creation and ensures reliable loading and discovery.

Migrating third-party skills to KiloCode involves porting the skill structure while preserving governance and organization. This skill assists in refactoring and migration workflows to ensure consistent naming, frontmatter validation, and resource directory setup.

Yes, KiloCode supports both project-scoped and mode-scoped skill organization. You can structure your skills by placing SKILL.md files in the appropriate .kilo/skills/ directories to enable targeted loading and discovery within specific contexts.

You organize scripts and references by adding optional scripts/, references/, and assets/ directories within your skill folder. This structure enables reusable automation and guidance, ensuring resources are properly organized for reliable loading.

KiloCode skill loading fails due to frontmatter validation when the YAML frontmatter is missing required name or description fields. The skill scaffolding process enforces these fields to ensure consistent naming and reliable discovery across the system.