CreateSkill

Scaffold, validate, and canonicalize Aurora skill directories with TitleCase naming and flat structure.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Kaleb-Rupe/aurora --skill createskill-kaleb-rupe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CreateSkill
Source: https://github.com/Kaleb-Rupe/aurora/tree/main/claude/skills/Utilities/CreateSkill
Command: npx skills add https://github.com/Kaleb-Rupe/aurora --skill createskill-kaleb-rupe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating new Claude skills by hand leads to inconsistent naming, malformed YAML frontmatter, and folder structures that break skill discovery and routing. This Skill enforces the canonical Aurora skill format so every skill is discoverable and correctly structured. ## Core Features & Use Cases - Skill Scaffolding: Creates new skill directories with SKILL.md, Workflows/, and Tools/ following TitleCase naming and a maximum two-level folder depth. - Validation & Canonicalization: Audits existing skills against SKILLSYSTEM.md rules and restructures non-compliant skills, renaming files and converting legacy YAML trigger arrays. - Use Case: You ask to create a recipe-management skill; the workflow reads SKILLSYSTEM.md, generates a compliant SKILL.md with USE WHEN triggers, a workflow routing table, and example invocations, then verifies the result against a full checklist. ## Quick Start Ask the assistant to create a new skill for a task you want to automate, and it will scaffold the complete canonical skill structure.

Frequently Asked Questions about CreateSkill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Claude skill with proper structure?

Invoke the CreateSkill workflow, which reads SKILLSYSTEM.md, then creates a TitleCase skill directory containing SKILL.md with YAML frontmatter, a Workflows/ folder, and a Tools/ folder. It finishes with a compliance checklist covering naming, frontmatter, and routing.

How do I validate an existing skill's structure?

Use the ValidateSkill workflow, which checks TitleCase naming on directories and files, verifies the single-line USE WHEN description in YAML, confirms the Workflow Routing and Examples sections exist, and reports compliance or recommends canonicalization.

What naming convention do Aurora skills require?

All skill components use TitleCase (PascalCase): directories like CreateSkill, workflow files like Create.md, and tools like ManageServer.ts. Lowercase, hyphenated, snake_case, and all-caps names are rejected during validation.

Can skills have nested subdirectories for organization?

No. The canonical structure allows a maximum of two levels: skills/SkillName/Category/. Only Workflows/ and Tools/ subdirectories are permitted, and context documentation files must live directly in the skill root.

Why is my skill not triggering when expected?

Missing or malformed USE WHEN triggers in the YAML description are the usual cause. Run the ValidateSkill workflow to check that the description is single-line, intent-based, and free of legacy triggers or workflows arrays.