skill-creator

Standardize Claude skill creation and documentation with SKILL.md frontmatter and bundled resources.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/h4v1d/extension-collection-geminicli --skill skill-creator-h4v1d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/h4v1d/extension-collection-geminicli/tree/main/skill-creator
Command: npx skills add https://github.com/h4v1d/extension-collection-geminicli --skill skill-creator-h4v1d

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Standardizes the creation and documentation of Claude skills.

Core Features & Use Cases

  • Specifies a standardized blueprint for SKILL.md frontmatter (name + description) and a clean Markdown body.
  • Enforces a consistent resource layout (scripts/, references/, assets/) with starter templates to illustrate best practices.
  • Provides a repeatable workflow for initializing, editing, validating, and packaging skills, with clear progressive disclosure guidance.
  • Use cases include creating a new skill for a domain, updating an existing skill with new references, or packaging assets for reuse.

Quick Start

  1. Initialize a new skill scaffold using the Skill Initializer: scripts/init_skill.py <skill-name> --path <output-directory>.
  2. Open the generated SKILL.md and complete the frontmatter; fill in the description and procedural steps.
  3. Add reusable resources under scripts/, references/, and assets/, then validate and package with the provided tooling.

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 with standardized frontmatter?

To create and package Claude skills, use a standardized blueprint for SKILL.md frontmatter and Markdown body, then bundle reusable resources under scripts/, references/, and assets/ directories to ensure reliable packaging.

What's the best way to structure documentation and assets for a new skill?

The best way to structure skill documentation is maintaining a consistent resource layout with scripts/, references/, and assets/ directories, using starter templates to illustrate best practices for modular resource patterns.

How does the skill initialization workflow validate naming conventions?

The skill initialization workflow validates naming conventions by enforcing specific rules during the scaffolding process, running validation tooling against generated frontmatter and bundled resources to support reliable packaging.

Can I update an existing skill with new references without breaking packaging rules?

Yes, you can update an existing skill with new references by adding reusable resources to the designated directories and running the provided validation and packaging tooling to ensure compliance with structural rules.

Do I need starter templates to follow skill creation guidelines?

Starter templates are provided to illustrate best practices, but the core requirement is following the specified process, structure, and metadata frontmatter guidelines for standardizing creation and documentation.

Why does progressive disclosure matter when building skill workflows?

Progressive disclosure matters in skill workflows because it provides clear guidance on structuring procedural steps and bundled resources, ensuring users interact with complexity only when needed during skill execution.