skill-creator

Extract mandatory frontmatter from SKILL.md to define a Skill Unit.

Updated Mar 27, 2022
One-click install
npx skills add https://github.com/emliunix/home.conf --skill skill-creator-emliunix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/emliunix/home.conf/tree/main/skills/skill-creator
Command: npx skills add https://github.com/emliunix/home.conf --skill skill-creator-emliunix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skill creation and packaging can be inconsistent across teams. This Guide standardizes the discovery and packaging of Skill Units by enforcing a minimal frontmatter and clear structure.

Core Features & Use Cases

  • Standardized frontmatter validation with required name and description.
  • Optional resource organization (scripts/, references/, assets/) to keep SKILL.md lean while providing depth as needed.
  • Clear workflow for creating, updating, and packaging Skills to ensure reproducibility across teams.
  • Use cases include onboarding new skills, updating existing ones, and sharing best practices across organizations.

Quick Start

Define a new Skill Unit by adding SKILL.md with name and description frontmatter, then attach optional resources as needed.

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 creation and packaging across development teams?

Standardizing skill creation requires extracting mandatory frontmatter from SKILL.md to define a Skill Unit. This enforces consistent structure by validating required name and description fields across teams.

What is a Skill Unit and how does frontmatter validation work?

A Skill Unit is a packaged skill located under the skills/ directory. Frontmatter validation works by requiring name and description fields in SKILL.md to ensure proper structure and discovery.

How do I organize optional resources like scripts and references when building a skill?

Organize optional resources by placing them in scripts/, references/, and assets/ directories alongside SKILL.md. This keeps the core skill definition lean while providing additional depth as needed.

What metadata fields should I include in a SKILL.md frontmatter block?

Include structured YAML metadata fields such as name, tagline, description, request, complexity, category, keywords, dependencies, components, and safety fields in your SKILL.md frontmatter block.

Can I update existing skills without breaking the standardized packaging workflow?

Yes, you can update existing skills by modifying the SKILL.md frontmatter and optional resources while maintaining the required name and description fields to preserve packaging consistency.

What's the best way to onboard new skills into an existing development workflow?

Onboard new skills by creating a SKILL.md file with required frontmatter and attaching optional resources as needed. This ensures reproducibility and standardization across the organization.