skill-creator

Create standardized Skill Units packaged as distributable .skill files.

1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/yonderlab/kota.agent.skills --skill skill-creator-yonderlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/yonderlab/kota.agent.skills/tree/main/.agents/skills/skill-creator
Command: npx skills add https://github.com/yonderlab/kota.agent.skills --skill skill-creator-yonderlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The Skill Creator provides a standardized, end-to-end process to design, organize, and package Skill Units, ensuring consistent structure and reusable resources across skills.

Core Features & Use Cases

  • Creates a SKILL.md frontmatter template and structured body that guides users to define skill scope, usage, and guidance.
  • Sets up optional resource directories (scripts/, references/, assets/) with example placeholders to illustrate organization and usage.
  • Supports initialization, validation, and packaging workflows to produce distributable .skill files for sharing and deployment.

Quick Start

Initialize a new skill scaffold with the provided template, then customize SKILL.md and the bundled resources for your use case.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I package a skill unit into a distributable .skill file?

You package a skill unit by defining a standardized SKILL.md frontmatter, organizing optional scripts, references, and assets folders, and running the packaging workflow to generate a distributable .skill file.

What is a SKILL.md frontmatter template and how does it work?

A SKILL.md frontmatter template is a standardized metadata header requiring name and description fields, used to define the scope, usage, and guidance for a self-contained skill unit.

Do I need to include scripts, references, and assets folders for every skill?

No, the scripts, references, and assets folders are optional resource directories. You add them only when your skill requires bundled resources, while the validation process prevents extraneous files.

What's the best way to validate a skill before sharing it?

The best way to validate a skill is to run the built-in validation workflow, which enforces required frontmatter fields like name and description and checks for extraneous files before packaging.