skill-creator

Scaffold, validate, and package Claude skills as distributable .skill files.

Updated Aug 27, 2013
One-click install
npx skills add https://github.com/pkking/dotfiles --skill skill-creator-pkking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/pkking/dotfiles/tree/main/dotfiles/dot_config/opencode/skills/skill-creator
Command: npx skills add https://github.com/pkking/dotfiles --skill skill-creator-pkking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, quick_validate, and includes scripts (resource) components.

What problem does it solve?

This skill guide helps users design and package modular, reusable Claude skills. It provides a concise blueprint for creating, organizing, and distributing skill units that extend capabilities with workflows, tool integrations, and references.

Core Features & Use Cases

  • Structured Skill Anatomy: Defines a Skill Unit with a mandatory SKILL.md frontmatter and optional resources (scripts, references, assets) to support complex tasks.
  • Resource Packaging: Encourages bundling reusable scripts, reference docs, and templates for predictable automation.
  • Migration and Distribution: Includes templates and packaging scripts to generate distributable .skill files for sharing and reuse.

Quick Start

Use this skill to learn how to initialize a new skill with the provided templates, populate the bundled resources, and package the skill for sharing.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I create and package Claude skills as self-contained units?

To create and package Claude skills, you scaffold a new skill using initialization templates, populate resources like scripts and references, and bundle the output into a distributable .skill file for sharing.

What is the required YAML frontmatter contract for a valid skill file?

The required YAML frontmatter contract for a valid skill file mandates specifically name and description fields, while also supporting optional license and progressive disclosure metadata for extended configuration.

Can I use this to update existing Claude skills instead of starting from scratch?

Yes, you can update existing Claude skills by applying the provided validation and resource organization tooling, which ensures your current frontmatter and bundled assets meet the required structural contract.

What's the best way to organize reusable scripts and references for skill automation?

The best way to organize reusable scripts and references is to bundle them within the skill's optional resources directory, ensuring predictable automation and seamless packaging into the final distributable unit.

Does packaging a skill require external validation dependencies?

Packaging a skill relies on internal validation dependencies like yaml and quick_validate scripts, which automatically enforce the required frontmatter contract before generating the final distributable file.

Why does my Claude skill fail validation during initialization?

Your Claude skill fails validation during initialization when the SKILL.md file is missing mandatory frontmatter fields, specifically the required name and description keys defined in the YAML contract.