skill-create

Create Claude Code skills with structured SKILL.md templates and references.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/srnnkls/tropos --skill skill-create-srnnkls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-create
Source: https://github.com/srnnkls/tropos/tree/main/skills/skill-create
Command: npx skills add https://github.com/srnnkls/tropos --skill skill-create-srnnkls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a consistent, repeatable workflow for building Claude Code skills by outlining frontmatter requirements, structure, and governance patterns so teams can ship high-quality skills faster.

Core Features & Use Cases

  • Standardized skill structure (SKILL.md, templates, references) to accelerate creation.
  • Progressive disclosure guidance (metadata → SKILL.md → resources) to keep contexts lean.
  • Templates and references to maintain consistency across projects and teams.

Quick Start

Run the Skill Creation workflow to bootstrap a new skill directory and seed it with a SKILL.md.

Frequently Asked Questions about skill-create

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

FAQPage Schema
How do I create Claude Code skills with the correct frontmatter and metadata?

You create Claude Code skills by applying this workflow to bootstrap a new skill directory, which enforces frontmatter requirements and seeds the project with a standardized SKILL.md file.

What is progressive disclosure in skill creation and how does it structure documentation?

Progressive disclosure in skill creation structures documentation hierarchically from metadata to SKILL.md to resources, keeping contexts lean by only exposing necessary information at each layer.

Can I convert existing commands into reusable skills?

Yes, you can convert existing commands into reusable skills by applying this workflow, which extracts reusable capabilities and maps them into standardized templates with proper references.

What's the best way to maintain consistency across skill projects and teams?

The best way to maintain consistency is using standardized skill structures with templates and references, which enforces governance patterns and best practices across all projects.

Do I need any dependencies to bootstrap a new skill directory?

No dependencies are required to bootstrap a new skill directory, as the workflow operates independently to seed your project with structured templates and documentation.