Create New Skills

Create new Agent Skills with YAML frontmatter and multi-file structure.

Updated May 13, 2025
One-click install
npx skills add https://github.com/GolferGeek/orchestrator-ai --skill create-new-skills-golfergeek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Create New Skills
Source: https://github.com/GolferGeek/orchestrator-ai/tree/main/.claude/skills/meta-skill
Command: npx skills add https://github.com/GolferGeek/orchestrator-ai --skill create-new-skills-golfergeek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the complex process of extending Claude's capabilities by guiding users through the creation of new Agent Skills, ensuring best practices and multi-file patterns are followed.

Core Features & Use Cases

  • Skill Architecture Guidance: Provides comprehensive documentation on skill structure, progressive disclosure, and multi-file patterns.
  • Step-by-Step Creation: Walks through defining purpose, structuring SKILL.md, writing instructions, and adding supporting files.
  • Best Practices Enforcement: Ensures skills are focused, descriptions are clear, and testing is thorough for effective agent utilization.
  • Use Case: When you identify a repetitive task or a specific domain where Claude needs more expertise, use this skill to package that knowledge into a reusable, discoverable Agent Skill.

Quick Start

I want to create a new skill for reviewing JavaScript code. Guide me through the process.

Frequently Asked Questions about Create New Skills

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

FAQPage Schema
How do I create reusable Agent Skills for Claude?

Create Agent Skills by structuring a multi-file project with YAML frontmatter, a SKILL.md containing instructions, and optional REFERENCE.md and EXAMPLES.md files. This approach packages domain-specific capabilities into discoverable, reusable skills across projects and workflows.

What's the best way to document and structure custom agent capabilities?

Use progressive disclosure with a primary SKILL.md file for core instructions, supplemented by REFERENCE.md for external documentation and EXAMPLES.md for usage patterns. Supporting files in scripts/, templates/, and config/ directories provide controlled tool access and implementation details.

When should I package a workflow as a skill instead of a one-off prompt?

Package as a skill when you've identified a repetitive task or domain where Claude needs consistent expertise across multiple projects or team members. Skills enforce best practices, ensure clear documentation, and enable discovery and reuse at scale.

Can I share custom Agent Skills across teams and projects?

Yes. The multi-file skill structure with YAML frontmatter and standardized components is designed for shareability. Document your skill's purpose, provide clear examples, and follow the focus and testing best practices to make it discoverable and effective across contexts.

What file structure do Agent Skills require?

Skills require a YAML frontmatter (name and description), a SKILL.md with instructions, optional REFERENCE.md and EXAMPLES.md files for documentation, and supporting directories (scripts/, templates/, config/) for implementation and tool access control.

How do I ensure my custom skill follows agent development best practices?

Define a focused purpose, write clear descriptions in SKILL.md, provide concrete examples, test thoroughly, and organize supporting files for progressive disclosure. This enforces consistency, makes skills maintainable, and ensures effective agent utilization across workflows.