skill-creator

Validate SKILL.md files and generate YAML metadata for Skill Units.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Void0312Aurora/RAAS --skill skill-creator-void0312aurora
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/Void0312Aurora/RAAS/tree/main/skills/skill-creator
Command: npx skills add https://github.com/Void0312Aurora/RAAS --skill skill-creator-void0312aurora

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design or update DeepCode Next skills so they are concise, stage-aware, and compatible with the project's file-backed SKILL.md mechanism.

Core Features & Use Cases

  • Frontmatter-driven skill definitions (roles, stages, context, allowed_tools, paths)
  • Guidance on creating, migrating, adapting, refactoring skills
  • Validation checks ensuring name matches folder and appropriate triggers
  • Supports recommended creation flow and rules

Quick Start

Create a lean frontmatter block for a new skill and store it in SKILL.md.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I create a SKILL.md file with valid YAML frontmatter for DeepCode Next?

To create a SKILL.md file, define a YAML frontmatter block at the root directory containing the required name and description fields, along with optional directories for skill metadata generation.

What is frontmatter-driven skill design in workflow automation?

Frontmatter-driven skill design uses a YAML block in a SKILL.md file to define roles, stages, context, allowed tools, and paths for concise, stage-aware workflow automation.

What metadata fields are required when generating a new skill unit?

Generating a skill unit requires accurate metadata fields including tagline, description, request, complexity, category, keywords, dependencies, components, and toxicity derived from SKILL.md content.

How do I validate that a skill name matches its folder structure?

Validation checks ensure the skill name matches its folder structure by verifying the SKILL.md exists at the root with appropriate triggers and valid YAML frontmatter.

Does this skill validation approach work without external dependencies?

Yes, the skill validation approach works without external dependencies, relying solely on the file-backed SKILL.md mechanism to identify and validate skill units.

What are the limitations when migrating existing prompts to stage-aware skills?

Limitations when migrating prompts include ensuring concise stage-aware definitions and strict adherence to the prescribed YAML schema and formatting rules for compatibility.