skill-creator

Generate structured SKILL.md metadata and documentation for Claude skills.

3|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/CANTAGESTUDIO/CosmicAtlasPacker --skill skill-creator-cantagestudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/CANTAGESTUDIO/CosmicAtlasPacker/tree/main/.claude/skills/skill-creator
Command: npx skills add https://github.com/CANTAGESTUDIO/CosmicAtlasPacker --skill skill-creator-cantagestudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Outlines how to create or update Claude Skills with structured guidance and packaging steps.

Core Features & Use Cases

  • Skill Structure: SKILL.md, scripts/references/assets.
  • Creation Process: Plan, implement, package, and iterate.

Quick Start

Outline a new skill concept and follow the steps to implement the SKILL.md.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I create a new Claude Skill with proper structure and documentation?

Creating a Claude Skill requires structuring it with a SKILL.md file, scripts folder, and references/assets directories. Follow the planning, implementation, packaging, and iteration workflow to enforce YAML frontmatter, metadata guidelines, and modular content organization for deployment across workflows.

What is the standard format and packaging process for Claude Skills?

Claude Skills use SKILL.md as the core file with supporting scripts, references, and assets. The packaging process enforces structured metadata, YAML frontmatter compliance, and modular content design to ensure reusability and consistent deployment across skill workflows.

Can I update or iterate on an existing Claude Skill after initial creation?

Yes, the skill creation workflow supports updating existing skills through structured refinement cycles. You can modify metadata, documentation, and scripts while maintaining YAML frontmatter requirements and modular structure guidelines for consistent skill versioning.

What guidelines should I follow when structuring skill documentation and metadata?

Skill documentation must follow YAML frontmatter requirements, enforce concise and reusable content patterns, and organize supporting resources into scripts, references, and assets folders. This ensures skills meet structure guidelines and remain deployable across modular workflows.

How do I bundle resources and package a skill for deployment?

Bundle resources by organizing scripts, references, and assets alongside the SKILL.md file according to structure guidelines. Apply metadata validation and YAML frontmatter formatting before packaging to ensure the skill deploys consistently across workflows and environments.