skill-status
- Repo stars 549
- Author repo bkit-claude-code
skill-status - Skill Inventory Report
로드된 스킬 목록을 core(bkit 기본)와 project-local로 구분하여 표시.
Command: /skill-status
Step 1: Scan Core Skills
- Read bkit core skills directory:
~/.claude/plugins/cache/bkit-marketplace/bkit/*/skills/ - For each skill directory, read SKILL.md frontmatter:
- name, classification, description (first line)
- Count total core skills
Step 2: Scan Project-Local Skills
- Read project skills directory:
.claude/skills/project/*/SKILL.md - For each skill, read frontmatter
- Count total project skills
Step 3: Detect Conflicts
- Compare skill names between core and project
- If same name exists in both: mark as "override" (project wins)
- If project skill triggers overlap with core: mark as "shadow"
Step 4: Display Report
Skill Status Report
====================
Layer: bkit Core (v1.6.2)
Skills: 28 loaded
-----------------------------------------------
Name | Type | Classification
--------------------|------------|---------------
pdca | workflow | PDCA lifecycle
enterprise | workflow | Enterprise init
bkit-rules | capability | Auto-apply rules
code-review | workflow | Code analysis
... (truncated)
Layer: Project-Local (hunikflow)
Skills: 8 loaded
-----------------------------------------------
Name | Type | Classification
--------------------|------------|---------------
btw | workflow | BTW suggestions
skill-create | workflow | Skill generator
skill-status | workflow | This report
hunikflow-model | capability | @Flow patterns
hunikflow-proxy | capability | DataProxy patterns
hunikflow-domain | capability | ERP domain logic
hunikflow-i18n | capability | i18n CSV guide
hunikflow-dynamic-api| capability | Dynamic API guide
Conflicts: 0 overrides, 0 shadows
Summary: 36 total skills (28 core + 8 project)
Options
/skill-status --detail: Show full descriptions and trigger keywords for each skill.
/skill-status --conflicts: Show only skills with naming conflicts or trigger overlaps.
Skill Layer Priority
Priority (high to low):
1. .claude/skills/project/ (project-local, git-tracked)
2. ~/.claude/plugins/.../skills/ (bkit core, plugin-managed)
3. ~/.claude/skills/ (user global, if any)
When a project skill has the same name as a core skill, the project skill takes precedence. This is the "2-layer override" pattern.
- 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
- Unspecified
- 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,默认拥有全部工具权限。
The current SKILL.md does not define a fixed output example. Read bkit core skills directory: ~/.claude/plugins/cache/bkit-marketplace/bkit//skills/ For each skill directory, read SKILL.md frontmatter:
Read project skills directory: .claude/skills/project//SKILL.md For each skill, read frontmatter
Compare skill names between core and project If same name exists in both: mark as "override" (project wins) If project skill triggers overlap with core: mark as "shadow"
Step 4: Display Report
# skill-status - Skill Inventory Report
로드된 스킬 목록을 core(bkit 기본)와 project-local로 구분하여 표시.
## Command: `/skill-status`
### Step 1: Scan Core Skills
1. Read bkit core skills directory:
`~/.claude/plugins/cache/bkit-marketplace/bkit/*/skills/`
2. For each skill directory, read SKILL.md frontmatter:
- name, classification, description (first line)
3. Count total core skills
### Step 2: Scan Project-Local Skills
1. Read project skills directory:
`.claude/skills/project/*/SKILL.md`
2. For each skill, read frontmatter
3. Count total project skills
### Step 3: Detect Conflicts
1. Compare skill names between core and project
2. If same name exists in both: mark as "override" (project wins)
3. If project skill triggers overlap with core: mark as "shadow"
### Step 4: Display Report
```
Skill Status Report
====================
Layer: bkit Core (v1.6.2)
Skills: 28 loaded
-----------------------------------------------
Name | Type | Classification
--------------------|------------|---------------
pdca | workflow | PDCA lifecycle
enterprise | workflow | Enterprise init
bkit-rules | capability | Auto-apply rules
code-review | workflow | Code analysis
... (truncated)
Layer: Project-Local (hunikflow)
Skills: 8 loaded
-----------------------------------------------
Name | Type | Classification
--------------------|------------|---------------
btw | workflow | BTW suggestions
skill-create | workflow | Skill generator
skill-status | workflow | This report
hunikflow-model | capability | @Flow patterns
hunikflow-proxy | capability | DataProxy patterns
hunikflow-domain | capability | ERP domain logic
… Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.
sections -> Command: /skill-status → Step 1: Scan Core Skills → Step 2: Scan Project-Local Skills → Step 3: Detect Conflicts → Step 4: Display Report → Options
terms -> /skill-status --detail · /skill-status --conflicts · 로드된 스킬 목록을 core(bkit 기본)와 project-local로 구분하여 표시. · 1. Read bkit core skills directory: ~/.claude/plugins/cache/bkit-marketplace/bkit//skills/ 2. · 1. Read project skills directory: .claude/skills/project//SKILL.md 2. · 1. Compare skill names between core and project 2. · /skill-status --detail: Show full descriptions and trigger keywords for each skill. · /skill-status --conflicts: Show only skills with naming conflicts or trigger overlaps.
files/cmd -> /skill-status · ~/.claude/plugins/cache/bkit-marketplace/bkit//skills/ · .claude/skills/project//SKILL.md · /skill-status --detail · /skill-status --conflicts
body sha256 -> d8eee5f8e712
Decide Fit First
Design Intent
How To Use It
Boundaries And Review