skill-creator

Generate SKILL.md frontmatter and structured instruction bodies for Claude Skills.

111|5|Updated Oct 29, 2021
One-click install
npx skills add https://github.com/nateberkopec/dotfiles --skill skill-creator-nateberkopec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/nateberkopec/dotfiles/tree/main/files/home/.claude/skills/skill-creator
Command: npx skills add https://github.com/nateberkopec/dotfiles --skill skill-creator-nateberkopec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the complex process of creating new AI Skills or enhancing existing ones, providing structured guidance and best practices. It helps you design effective, modular, and context-efficient Skills, reducing development time and ensuring high quality, so you can extend AI capabilities with ease.

Core Features & Use Cases

  • Structured Workflow: Guides you through a step-by-step process from understanding user needs to planning, initializing, and iterating on Skill content.
  • Resource Optimization: Advises on when and how to use scripts/, references/, and assets/ to manage context efficiently and avoid token waste.
  • Use Case: You want to create a new Skill for "Financial Report Generation." This Skill will guide you on how to structure your SKILL.md, what financial schemas to put in references/, and how to include report templates in assets/, ensuring your new Skill is robust and efficient.

Quick Start

Help me create a new skill called 'customer-onboarding-guide' that provides step-by-step instructions for new users.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I structure a new AI Skill with proper frontmatter and documentation?

Create a Skill by generating a SKILL.md file with YAML frontmatter containing a hyphen-case name and description, followed by a structured Markdown body. The frontmatter defines metadata while the body contains step-by-step procedural instructions, with optional scripts/, references/, and assets/ directories for managing context efficiently.

What's the best way to organize references and assets when building a Skill?

Use references/ to store schemas, templates, and reference data, and assets/ for supporting files. This separation avoids token waste by keeping large content modular and loadable on-demand rather than embedding everything in the instruction body.

Can I create Skills for specific workflows like financial reporting or customer onboarding?

Yes. Design domain-specific Skills by defining clear procedural steps, placing domain schemas and templates in references/, and including relevant output formats or examples in assets/. This approach works across workflows, tool integrations, and domain knowledge applications.

How do I reduce development time when creating multiple Skills?

Follow the structured workflow to plan user needs first, then initialize the SKILL.md template with proper frontmatter. Reuse reference formats and asset structures across similar Skills to maintain consistency and avoid rebuilding components.

What are the technical requirements for a valid Skill?

A valid Skill requires YAML frontmatter with hyphen-case naming and a non-bracketed description field, plus a procedural Markdown body. Optional components include scripts/, references/ for schemas, and assets/ for templates or supporting files.

When should I use scripts in a Skill versus inline instructions?

Use scripts/ for reusable automation, tool integrations, or complex procedural logic that would clutter the main instruction body. Keep inline instructions for sequential guidance and decision points that users need to follow directly.