| name | skill-create |
| classification | workflow |
| classification-reason | Interactive skill creation workflow with user prompts, file generation, and eval scaffolding. Multi-step process requiring user decisions. |
| deprecation-risk | none |
| effort | low |
| description | Interactive skill creation workflow for project-local skills.
Triggers: skill-create, create skill
|
| argument-hint | /skill-create [name] | /skill-create from-btw {btw-id} |
| user-invocable | true |
| allowed-tools | ["Read","Write","Edit","Glob","Grep","Bash"] |
skill-create - Interactive Skill Creation Workflow
ํ๋ก์ ํธ ์ปจํ
์คํธ๋ฅผ ๋ถ์ํ์ฌ project-local ์คํฌ์ ์์ฑํ๋ ์ํฌํ๋ก์ฐ.
Workflow Steps
Step 1: Gather Information
If /skill-create (no args):
- Ask user for skill name (kebab-case)
- Ask user for skill purpose/description
- Ask user for classification: workflow or capability
If /skill-create {name}:
- Use provided name
- Analyze project context to infer purpose
- Ask user to confirm/modify
If /skill-create from-btw {btw-id}:
- Read btw suggestion from
.bkit/btw-suggestions.json
- Use suggestion text as seed for skill description
- Use suggestion context for project context
Step 2: Analyze Project Context
- Read
CLAUDE.md for project conventions
- Scan project structure:
- Identify tech stack (Java/Spring, Next.js, Python, etc.)
- Find relevant patterns in source code
- Check existing project-local skills for overlap
- Determine appropriate:
- Allowed tools for the skill
- Trigger keywords (Korean + English)
- Related files/patterns to reference
Step 3: Generate SKILL.md
Create .claude/skills/project/{name}/SKILL.md with:
---
name: {name}
classification: {workflow|capability}
classification-reason: "{reason based on analysis}"
deprecation-risk: none
effort: low
description: |
{Generated description}
Triggers: {trigger commands}
Keywords: {keywords in Korean and English}
argument-hint: "{usage hint}"
user-invocable: true
allowed-tools:
- Read