skill-creator

Scaffold SKILL.md files and package skills into .skill archives.

40|9|Updated Mar 23, 2025
One-click install
npx skills add https://github.com/kyopark2014/mcp --skill skill-creator-kyopark2014
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/kyopark2014/mcp/tree/main/application/skills/skill-creator
Command: npx skills add https://github.com/kyopark2014/mcp --skill skill-creator-kyopark2014

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Standardizes how agent skills are defined, organized, and packaged to reduce ad-hoc processes and ensure consistent structure across teams.

Core Features & Use Cases

  • Scaffold SKILL.md with required frontmatter (name and description) and a guided body structure for skills.
  • Optional resource directories (scripts, references, assets) to organize tooling, documentation, and output assets.
  • End-to-end packaging and validation workflow to generate a distributable .skill file while enforcing naming conventions and security checks.

Quick Start

Run scripts/init_skill.py <skill-name> --path skills to generate the SKILL.md scaffold and then customize it.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I scaffold and package agent skills with a standardized frontmatter structure?

To scaffold and package agent skills, run the initialization script to generate a SKILL.md file with required frontmatter, organize optional resource directories like scripts and assets, and validate naming conventions before packaging into a distributable .skill archive.

What is the required frontmatter and file structure for a valid SKILL.md module?

The required frontmatter for a valid SKILL.md module includes the name and description fields. The file structure should contain a guided body and can optionally include scripts, references, and assets directories to organize tooling and documentation.

How does the end-to-end packaging workflow generate a distributable .skill file?

The end-to-end packaging workflow generates a distributable .skill file by applying frontmatter validation, enforcing naming conventions, executing security checks, and bundling the SKILL.md with its associated resource directories into a single archive.

Do I need any external dependencies to create and validate skill archives?

You do not need any external dependencies to create and validate skill archives. The packaging workflow relies solely on its bundled scripts to handle frontmatter validation, resource organization, and security checks without external packages.

What is the best way to organize scripts and assets when updating an existing skill?

The best way to organize scripts and assets when updating an existing skill is to use the optional resource directories within the skill structure, separating tooling, documentation references, and output assets to maintain consistent distribution and validation.

What security checks are enforced during the skill packaging process?

During the skill packaging process, security checks are enforced alongside naming convention validation and frontmatter verification to ensure the modular skill structure is safe for consistent distribution across teams without ad-hoc processes.