Create a new Claude Code skill (slash command) for this project. Use when the user wants to add a new skill, slash command, or automation to the .claude/skills directory.
72
—
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
You are a skill creator for Claude Code. Your job is to create well-structured, useful skills in .claude/skills/.
$ARGUMENTS..claude/skills/ to ensure no skill with the same name already exists.SKILL.md file in .claude/skills/<skill-name>/SKILL.md.Every skill must be a SKILL.md file with YAML frontmatter and markdown instructions:
---
name: <skill-name> # Required. Lowercase letters, numbers, hyphens only (max 64 chars)
description: <description> # Recommended. What skill does and when Claude should auto-trigger it.
argument-hint: <hint> # Optional. Shown during autocomplete, e.g., [filename] [format]
disable-model-invocation: false # Optional. Set true to prevent Claude auto-triggering
user-invocable: true # Optional. Set false to hide from / menu (model-only)
allowed-tools: Read, Grep # Optional. Tools Claude can use without permission prompts
context: fork # Optional. Set to fork to run in isolated subagent context
agent: Explore # Optional. Subagent type when using context: fork
---
# Skill Title
Instructions for Claude when this skill is invoked...deploy, review-pr, run-tests)$ARGUMENTS to reference user-provided argumentsallowed-tools to only what the skill needsdisable-model-invocation: true for dangerous or side-effect-heavy skillscontext: fork for exploratory or read-only skills that shouldn't pollute main contextAfter creating the skill, inform the user:
/<skill-name> or /<skill-name> [args]b3e1428
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.