skill-creator

Scaffolding a new Skill generates a complete, well-structured layout including SKILL.md, resources/, and activation tests. Provide your Skill's name, core purpose, and trigger keywords—the scaffolder creates a migration-pattern–compliant foundation ready for immediate development and deployment.

Yes. Migration patterns translate slash commands to Skills by restructuring triggers, descriptions, and validation logic. The Skill creator applies Fakt patterns and progressive disclosure during conversion, ensuring the migrated Skill meets activation readiness standards without manual rework.

Activation-readiness requires trigger-rich descriptions, model-agnostic design, and passing activation tests included in the scaffold. The Skill creator bundles a test prompt that validates your Skill's structure and triggers before rollout, reducing deployment risk.

Scaffolding builds a new Skill from requirements; migration converts an existing slash command or tool into Skill form. Both follow the same migration patterns and produce activation-ready output, but migration preserves existing logic and triggers while restructuring for Skill standards.

Progressive disclosure is enforced automatically during scaffolding—it structures how your Skill's features reveal to users. You define triggers and core purpose; the scaffolder applies disclosure patterns so users encounter complexity incrementally, improving usability.

Consistent Skill structure—enforced through migration patterns—ensures discoverability, activation compatibility, and user onboarding. The scaffolder validates structure compliance automatically, preventing silent failures during rollout and reducing support burden.