skill-creator

Build self-contained skill units from procedural guidance and bundled resources.

130|28|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/kitchen-engineer42/Anything2Ontology --skill skill-creator-kitchen-engineer42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/kitchen-engineer42/Anything2Ontology/tree/main/reference/skill-creator
Command: npx skills add https://github.com/kitchen-engineer42/Anything2Ontology --skill skill-creator-kitchen-engineer42

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It removes the guesswork from creating high-quality Skills by giving you a clear structure for metadata, instructions, validation, and supporting files.

Core Features & Use Cases

  • Skill design guidance: Decide what belongs in SKILL.md versus scripts, references, and assets.
  • Workflow packaging: Initialize, validate, and package skills into distributable .skill files.
  • Use cases: Create a new skill for a repetitive task, update an existing skill, or organize reusable resources for deterministic automation and richer context.

Quick Start

Use this skill to create or update a skill by writing a precise SKILL.md frontmatter, adding only the resources you need, and packaging the finished directory after validation.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I package procedural guidance and scripts into a reusable skill?

To package procedural guidance, you write a SKILL.md file with valid frontmatter, add only the necessary scripts, references, and assets, then validate and package the finished directory into a distributable .skill file.

What is the best way to structure metadata for workflow automation skills?

Structuring metadata for workflow automation skills requires a precise SKILL.md frontmatter definition, which separates core instructions from bundled scripts and references to ensure deterministic execution and proper validation.

Do I need pyyaml installed to validate and build skill packages?

Yes, pyyaml is a required dependency to build and validate skill packages, as it is necessary for parsing the SKILL.md frontmatter and processing the metadata required for packaging.

Can I update existing skills with new domain knowledge and tool integrations?

You can update existing skills by modifying the SKILL.md instructions and adding new bundled resources like scripts or references, then running validation before repackaging the updated directory.

How do I decide what belongs in SKILL.md versus bundled scripts and references?

Core procedural guidance and metadata belong in SKILL.md, while executable logic, supporting documentation, and static files should be separated into bundled scripts, references, and assets to support deterministic execution.

Why does my skill validation fail before packaging into a .skill file?

Skill validation typically fails due to missing or incorrectly formatted SKILL.md frontmatter, or due to missing required dependencies like pyyaml, which prevents the packaging process from executing deterministically.