skills.rest
Aurora-AI
Aurora-AICOMMUNITY
Explore all skills by this author →
WebsiteGitHub

skill-creator

Standardize Aurora skill identity, versioning, and catalog registration via YAML frontmatter.

Updated Apr 24, 2026
Search Tags:#automation#documentation#standardization#catalog#governance#skill-creation#semantic-triggers
One-click install
npx skills add https://github.com/Aurora-AI/Elysiancorpfront --skill skill-creator-aurora-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/Aurora-AI/Elysiancorpfront/tree/main/.aurora/skills/skill-creator
Command: npx skills add https://github.com/Aurora-AI/Elysiancorpfront --skill skill-creator-aurora-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures every Aurora skill has a consistent header, description, and discovery metadata, enabling reliable governance, auditability, and deterministic loading into tooling.

Core Features & Use Cases

  • Enforces YAML frontmatter with required fields (name, version, updated, domain, description)
  • Provides a standard workflow for creating, mapping, and registering skills into the global catalog
  • Supports semantic triggers and observability hooks to maintain governance across the skill ecosystem

Quick Start

Create a new skill by adding a SKILL.md with proper frontmatter and descriptive body, then update the global catalog.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I standardize skill metadata for consistent governance and catalog registration?▼

Semantic triggers automate the discovery and loading of standardized skills into tooling by mapping specific function intents, ensuring reliable governance and observability hooks across the skill ecosystem.

What is the standard workflow for creating and registering a new skill?▼

Skill versioning requires updating the version field within the YAML frontmatter header and ensuring the global catalog is updated with the new skill version to maintain auditability and deterministic loading into tooling.

Do I need YAML frontmatter to set up skill identity and discovery metadata?▼

Yes, you need YAML frontmatter to set up skill identity because it enforces required fields such as name, version, updated, domain, and description, which are mandatory for reliable governance and catalog registration.

What are the limitations of managing skill standardization without semantic triggers?▼

Without semantic triggers, skill standardization lacks automated function mapping and observability hooks, making it difficult to maintain governance, ensure deterministic discovery, and audit skills across the ecosystem.

Related Skills

Explore More Software Engineering Skills→
MileniumTickMileniumTick

elysiajs

Extract Skill Units from SKILL.md frontmatter and generate YAML metadata.

Community
Advanced
matt-rileymatt-riley
1

skill-creator

Create, upgrade, or standardise skill packages with canonical frontmatter and validation.

Community
Advanced
QventuQventu

mintlify

Creates and maintains Mintlify documentation sites using CLI, MDX frontmatter, and docs.json.

Official
Intermediate
mrkhachaturovmrkhachaturov

using-rkstack

Discover and route user intents to RKstack skills at session start.

Community
Basic