Skill

create-skill

Creates new skills for Claude Code. Guides users through defining skill behavior, scope (project or global), and generating SKILL.md files with proper frontmatter and trigger phrases.

developer-tools

automation

npx claudepluginhub moazbuilds/claudeclaw --plugin claudeclaw

Popularity

Stars

1,143

Forks

207

Shared by

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/claudeclaw:create-skill

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Create new skills for Claude Code. Use `$ARGUMENTS` to determine what the user wants.

SKILL.md

63 lines · ~615 tokens

Similar Skills

create-skill-claude

108

Guides creating Claude Code skills: clarify purpose, set file structure, configure frontmatter like disable-model-invocation, user-invocable, hooks. Triggers on 'create skill' requests.

creating-prompts

claude-code-skill-development

Guides development of Claude Code SKILL.md files with best practices, structure, YAML frontmatter rules, categories, patterns, references, and testing.

7 files2 tools

toolkit

create-agent-skills

Guides creation of Claude Code skills and slash commands: SKILL.md structure, frontmatter fields, invocation controls, commands vs skills, and best practices.

20 files

compound-engineering

Stats

LanguageTypeScript

Stars1,143

Forks207

MaintenanceExcellent

Last CommitJun 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Create Skill

Create new skills for Claude Code. Use $ARGUMENTS to determine what the user wants.

Skill File Format

A skill is a SKILL.md file inside a skills/<skill-name>/ directory. It uses YAML frontmatter:

--- name: my-skill description: Short description of when to trigger this skill. Include trigger phrases so Claude knows when to activate it. --- # Skill Title Instructions for what Claude should do when this skill is triggered.

Key rules for SKILL.md:

name: lowercase, kebab-case (e.g. my-skill)

description: must include trigger phrases and keywords so Claude knows when to use it

The body contains the full instructions Claude will follow when the skill is invoked

Scope

Skills can be created at two levels:

Project Level (default)

Location: <project-root>/skills/<skill-name>/SKILL.md

Only available within this project

No special permissions needed

Use this when the skill is project-specific

Global Level

Location: ~/.claude/skills/<skill-name>/SKILL.md

Available across all projects

Requires write access to ~/.claude/

Use this when the skill should work everywhere

Steps

Ask the user conversationally what the skill should do, what scope (project or global), and what name they want. Suggest ideas based on context.

Based on their answers, generate the SKILL.md content:

Write a clear, descriptive name in kebab-case
Write a description with plenty of trigger phrases so Claude knows when to activate it
Write detailed body instructions for what Claude should do

Create the skill:

Project level: Write to skills/<skill-name>/SKILL.md relative to project root
Global level: Write to ~/.claude/skills/<skill-name>/SKILL.md

Confirm creation and show the user:

The skill name and path
How to invoke it: /<plugin-name>:<skill-name> or just by asking naturally (Claude auto-triggers based on description)
Remind them the skill is available immediately — no restart needed

Create Skill

Create new skills for Claude Code. Use $ARGUMENTS to determine what the user wants.

Skill File Format

A skill is a SKILL.md file inside a skills/<skill-name>/ directory. It uses YAML frontmatter:

---
name: my-skill
description: Short description of when to trigger this skill. Include trigger phrases so Claude knows when to activate it.
---

# Skill Title

Instructions for what Claude should do when this skill is triggered.

Key rules for SKILL.md:

name: lowercase, kebab-case (e.g. my-skill)
description: must include trigger phrases and keywords so Claude knows when to use it
The body contains the full instructions Claude will follow when the skill is invoked

Scope

Skills can be created at two levels:

Project Level (default)

Location: <project-root>/skills/<skill-name>/SKILL.md
Only available within this project
No special permissions needed
Use this when the skill is project-specific

Global Level

Location: ~/.claude/skills/<skill-name>/SKILL.md
Available across all projects
Requires write access to ~/.claude/
Use this when the skill should work everywhere

Steps

Ask the user conversationally what the skill should do, what scope (project or global), and what name they want. Suggest ideas based on context.
Based on their answers, generate the SKILL.md content:
- Write a clear, descriptive name in kebab-case
- Write a description with plenty of trigger phrases so Claude knows when to activate it
- Write detailed body instructions for what Claude should do
Create the skill:
- Project level: Write to skills/<skill-name>/SKILL.md relative to project root
- Global level: Write to ~/.claude/skills/<skill-name>/SKILL.md
Confirm creation and show the user:
- The skill name and path
- How to invoke it: /<plugin-name>:<skill-name> or just by asking naturally (Claude auto-triggers based on description)
- Remind them the skill is available immediately — no restart needed

create-skill

Popularity

Invocation

Context Preview

SKILL.md

Similar Skills

Help us improve

Help us improve

Find plugins for your project

create-skill

Popularity

Invocation

Context Preview

SKILL.md

Create Skill

Skill File Format

Key rules for SKILL.md:

Scope

Project Level (default)

Global Level

Steps

Similar Skills

Help us improve

Create Skill

Skill File Format

Key rules for SKILL.md:

Scope

Project Level (default)

Global Level

Steps