brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
create-skillCreate new skills for Claude Code. Use when users ask to create a skill, add a skill, make a new command, build a skill, add a slash command, create a plugin skill, or define a new automation. Trigger phrases include "create a skill", "new skill", "add a skill", "make a command", "build a skill", "I want a skill that", "add slash command", "create automatio…
Independent GitHub snapshot · Automated classification · Original documentation governs
Create new skills for Claude Code. Use $ARGUMENTS to determine what the user wants.
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.
my-skill)Skills can be created at two levels:
<project-root>/skills/<skill-name>/SKILL.md~/.claude/skills/<skill-name>/SKILL.md~/.claude/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:
name in kebab-casedescription with plenty of trigger phrases so Claude knows when to activate itCreate the skill:
skills/<skill-name>/SKILL.md relative to project root~/.claude/skills/<skill-name>/SKILL.mdConfirm creation and show the user:
/<plugin-name>:<skill-name> or just by asking naturally (Claude auto-triggers based on description)