skill create

Other Community

Skill notes

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}:

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

Step 3: Generate SKILL.md

Create .claude/skills/project/{name}/SKILL.md with: Body content includes: Purpose and when to use Step-by-step instructions for workflow skills Pattern reference for capability skills

Step 4: Generate Eval Files (optional)

Create evals/{name}/ directory with: eval.yaml format:

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"

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
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
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@popup-studio-ai · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
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}`:

02
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

03
Step 3: Generate SKILL.md

Create `.claude/skills/project/{name}/SKILL.md` with: Body content includes: Purpose and when to use Step-by-step instructions for workflow skills Pattern reference for capability skills

04
Step 4: Generate Eval Files (optional)

Create `evals/{name}/` directory with: eval.yaml format:

05
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`"

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.