claude-skill-manager

Create and update Claude skills with standard SKILL.md structure.

Updated Nov 11, 2025
One-click install
npx skills add https://github.com/shredbx/demo-3d-model --skill claude-skill-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-skill-manager
Source: https://github.com/shredbx/demo-3d-model/tree/main/.claude/skills/claude-skill-manager
Command: npx skills add https://github.com/shredbx/demo-3d-model --skill claude-skill-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill guides users through the entire process of creating, structuring, and maintaining effective Claude Skills, ensuring they are modular, discoverable, and efficiently extend Claude's specialized knowledge and workflows.

Core Features & Use Cases

  • Skill Anatomy & Structure: Understand the required SKILL.md frontmatter and optional scripts/, references/, assets/ directories.
  • Progressive Disclosure: Design skills to efficiently manage context loading, from metadata to full resources.
  • Use Case: You need to create a new skill for managing financial reports. Use this Skill to initialize the skill directory, structure its SKILL.md, and decide which financial schemas belong in references/ versus assets/.

Quick Start

Use the claude-skill-manager skill to initialize a new skill named 'my-new-skill' in the 'skills/public' directory.

Frequently Asked Questions about claude-skill-manager

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?

Create a skill by initializing a directory in .claude/skills with a SKILL.md file containing YAML frontmatter (name and description), an Overview section, and optional scripts/, references/, and assets/ subdirectories organized by function and naming conventions.

What goes in a SKILL.md file and how should I organize skill resources?

SKILL.md requires YAML frontmatter with name and description, followed by Overview and workflows or tasks sections. Store domain schemas and data in references/, visual or binary content in assets/, and automation logic in scripts/.

Can I modify an existing skill's metadata and structure after creation?

Yes, you can update existing skills by modifying the SKILL.md frontmatter, adjusting resource organization across scripts/, references/, and assets/ directories, and refactoring the skill's anatomy to follow standard conventions.

How do I make a skill modular and efficient for context loading?

Design progressive disclosure by separating metadata and high-level description in frontmatter from full resources in subdirectories. Load only necessary components on demand—metadata first, then workflows, then detailed references or assets.

What naming conventions and packaging guidelines should I follow for skills?

Use clear, lowercase skill names with hyphens, consistent file naming in subdirectories, and organize resources hierarchically. Package skills as self-contained modules in .claude/skills with all dependencies listed and components properly documented.