skill-create

Other Community

Repo stars 549
Author repo bkit-claude-code

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: | 프로젝트 컨텍스트를 분석하여 project-local 스킬을 생성하는 워크플로우. If /skill-create (no args): If /skill-create {name}: If /skill-create from-btw {…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Workflow Steps”, “Step 1: Gather Information”, “Step 2: Analyze Project Context”, “Step 3: Generate SKILL.md”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skill-create directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Workflow Steps / Step 1: Gather Information / Step 2: Analyze Project Context” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

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
  - Write
  - Edit
  - Glob
  - Grep
  - Bash
---

Body content includes:

Purpose and when to use
Step-by-step instructions for workflow skills
Pattern reference for capability skills
Code examples from actual project files
Integration points with other skills

Step 4: Generate Eval Files (optional)

Create evals/{name}/ directory with:

evals/{name}/
  eval.yaml        - Test configuration
  prompt.txt       - Test prompt
  expected.txt     - Expected behavior description

eval.yaml format:

name: "{name} skill eval"
skill: ".claude/skills/project/{name}/SKILL.md"
tests:
  - name: "basic trigger"
    prompt: "{trigger command}"
    expected:
      - "{expected behavior 1}"
      - "{expected behavior 2}"
  - name: "edge case"
    prompt: "{edge case prompt}"
    expected:
      - "{expected behavior}"

Step 5: Confirm and Report

Show generated file paths
Show skill summary (name, classification, triggers)
Suggest: "Test with /{name} or review at .claude/skills/project/{name}/SKILL.md"

Project-Local Skill Location

All generated skills go to: .claude/skills/project/{name}/SKILL.md

This location:

Is git-trackable for team sharing
Takes precedence over bkit core skills (2-layer architecture)
Is auto-loaded by Claude Code's skill discovery

Naming Conventions

Pattern	Example	Use When
`{project}-{domain}`	`hunikflow-model`	Domain-specific capability
`{action}-{target}`	`validate-entity`	Action-oriented workflow
`{tool}-{purpose}`	`proxy-guide`	Tool/pattern guide

From-BTW Integration

When creating from a /btw suggestion:

Read the suggestion's context.file to understand what code was being worked on
Read the suggestion's context.feature to understand the PDCA feature context
Use suggestion text as the primary description seed
After creation, update the btw suggestion's promotedTo field with the new skill name

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Other
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @popup-studio-ai · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Python
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-create.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# skill-create - Interactive Skill Creation Workflow

프로젝트 컨텍스트를 분석하여 project-local 스킬을 생성하는 워크플로우.

## Workflow Steps

### Step 1: Gather Information

If `/skill-create` (no args):
1. Ask user for skill name (kebab-case)
2. Ask user for skill purpose/description
3. Ask user for classification: workflow or capability

If `/skill-create {name}`:
1. Use provided name
2. Analyze project context to infer purpose
3. Ask user to confirm/modify

If `/skill-create from-btw {btw-id}`:
1. Read btw suggestion from `.bkit/btw-suggestions.json`
2. Use suggestion text as seed for skill description
3. Use suggestion context for project context

### Step 2: Analyze Project Context

1. Read `CLAUDE.md` for project conventions
2. 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
3. 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:

```yaml
---
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
  - Write
  - Edit
  - Glob
  - Grep
  - Bash
---
```

Body content includes:
- Purpose and when to use
- Step-by-step instructions for workflow skills
- Pattern reference for capability skills
- Code examples from actual project files
- Integration points with other skills

### Step 4: Generate Eval Files (optional)

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Workflow Steps → Step 1: Gather Information → Step 2: Analyze Project Context → Step 3: Generate SKILL.md → Step 4: Generate Eval Files (optional) → Step 5: Confirm and Report
terms    -> eval.yaml format · 프로젝트 컨텍스트를 분석하여 project-local 스킬을 생성하는 워크플로우. · If /skill-create (no args): 1. · If /skill-create {name}: 1. · If /skill-create from-btw {btw-id}: 1. · 1. Read CLAUDE.md for project conventions 2. · 1. Show generated file paths 2. · When creating from a /btw suggestion: 1.
files/cmd -> /skill-create · /skill-create {name} · /skill-create from-btw {btw-id} · .bkit/btw-suggestions.json · CLAUDE.md · .claude/skills/project/{name}/SKILL.md · evals/{name}/ · /{name}
body sha256 -> 60c6621af27c