creating-new-skills

Create new Claude Code Agent Skills with structured SKILL.md files.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/PytaichukBohdan/DanaCockFightBot --skill creating-new-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-new-skills
Source: https://github.com/PytaichukBohdan/DanaCockFightBot/tree/main/.claude/skills/meta-skill
Command: npx skills add https://github.com/PytaichukBohdan/DanaCockFightBot --skill creating-new-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps users create well-structured Skill units by validating frontmatter, providing a guided workflow, and ensuring progressive disclosure and reusability.

Core Features & Use Cases

  • Structured Skill creation: Step-by-step workflow to create a Skill directory and SKILL.md
  • Best practices enforcement: Adheres to naming conventions and frontmatter rules
  • Guided extension: Guides adding references/scripts/assets with progressive disclosure

Quick Start

When asked to "create a new Skill" the Skill will:

  • Instruct on creating directory .claude/skills/<skill-name>
  • Require a SKILL.md with proper frontmatter
  • Show how to add supporting files like scripts/references/assets
  • Provide examples and testing steps

Frequently Asked Questions about creating-new-skills

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

FAQPage Schema
How do I create a new Agent Skill for Claude Code?

Create a new Agent Skill by setting up a directory at `.claude/skills/<skill-name>`, adding a SKILL.md file with required YAML frontmatter (name, description, allowed-tools), writing Instructions and Examples sections, and organizing supporting files like scripts, references, and assets following progressive disclosure with three loading levels.

What frontmatter constraints and metadata rules apply when building a Skill?

Frontmatter must include name, description, and allowed-tools fields in YAML format. The Skill enforces naming conventions, validates metadata constraints, and requires proper structure to ensure reusability across personal, project, and plugin skill types.

How does progressive disclosure work when structuring a Skill?

Progressive disclosure organizes Skill content into three loading levels, revealing Instructions and Examples incrementally, with optional resources available separately. This approach balances comprehensiveness with usability, preventing cognitive overload while keeping advanced guidance accessible.

Can I use this workflow for personal, project, and plugin Skills?

Yes, the end-to-end creation workflow applies across all three Skill types. The structured approach to directory organization, frontmatter requirements, and supporting file management ensures consistency whether you're building for personal use, team projects, or plugin distribution.

What supporting files and assets can I include in a Skill?

Beyond the SKILL.md file, you can organize references, scripts, and assets in supporting directories. The Skill guides how to structure and reference these files while maintaining progressive disclosure, ensuring they're discoverable without cluttering the initial Skill presentation.

Why does Skill creation enforce best practices and naming conventions?

Enforcing best practices and naming conventions ensures Skills are well-structured, reusable, and maintainable across teams. Consistent metadata, proper frontmatter, and guided workflows reduce friction when sharing Skills and prevent structural issues that degrade usability or documentation clarity.