popup-studio-ai/skill-status
skills/skill-status/SKILL.md
Show loaded skill inventory — bkit core vs project-local, conflicts, coverage gaps. Triggers: skill-status, skill list, 스킬 상태, 스킬 목록.
$ install --global
skillsauthnpx skillsauth add popup-studio-ai/bkit-claude-code skill-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 9, 2026, 7:25 AM128.4s1 file scanned
SKILL.md
- name:
- skill-status
- context:
- fork
- classification:
- workflow
- classification-reason:
- Reports loaded skill inventory across core and project layers. Read-only status check workflow.
- deprecation-risk:
- none
- effort:
- low
- description:
- |
- Triggers:
- skill-status, skill list, 스킬 상태, 스킬 목록.
- argument-hint:
- /skill-status [--detail] [--conflicts]
- user-invocable:
- true
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.
Related Skills
popup-studio-ai/sprint
testing
VerifiedTrustedCommunity
Sprint Management — generic sprint capability for ANY bkit user. 16 sub-actions: init, start, status, watch, phase, iterate, qa, report, archive, list, feature, pause, resume, fork, help, master-plan. Triggers: sprint, sprint start, sprint init, sprint status, sprint list, 스프린트, 스프린트 시작, 스프린트 상태, スプリント, スプリント開始, スプリント状態, 冲刺, 冲刺开始, 冲刺状态, sprint, iniciar sprint, estado sprint, sprint, demarrer sprint, statut sprint, Sprint, Sprint starten, Sprint Status, sprint, avviare sprint, stato sprint, master plan, multi-sprint plan, sprint master plan, 마스터 플랜, 멀티 스프린트 계획, 스프린트 마스터 플랜, マスタープラン, マルチスプリント計画, スプリントマスタープラン, 主计划, 多冲刺计划, 冲刺主计划, plan maestro, plan multi-sprint, plan maestro sprint, plan maître, plan multi-sprint, plan maître sprint, Masterplan, Multi-Sprint-Plan, Sprint-Masterplan, piano principale, piano multi-sprint, piano principale sprint.
548SKILL.mdUpdated May 13, 2026
popup-studio-ai/cc-version-analysis
tools
VerifiedTrustedCommunity
CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report. Triggers: cc-version-analysis, CC upgrade, version analysis, CC 버전 분석, 버전 영향.
545SKILL.mdUpdated Apr 18, 2026
popup-studio-ai/rollback
testing
VerifiedTrustedCommunity
Manage PDCA checkpoints and rollback — create, list, restore for safe recovery. Rollback events are recorded via lib/audit/audit-logger ACTION_TYPES.rollback_executed. For sprint-level recovery, individual feature rollbacks may be triggered from within sprint phases (sprint itself is forward-only — terminal state is `archived`, not rolled back; v2.1.13). Triggers: rollback, checkpoint, restore, undo, 롤백, 체크포인트, 복원.
539SKILL.mdUpdated Apr 18, 2026
popup-studio-ai/qa-phase
testing
VerifiedTrustedCommunity
QA Phase execution — L1-L5 test planning, generation, execution, and reporting for a single feature. For sprint-level QA (7-Layer dataFlowIntegrity / S1 gate across multiple features) use /sprint qa <sprintId> which delegates to sprint-qa-flow agent (v2.1.13). Triggers: qa phase, QA test, qa run, QA 실행, QAフェーズ, QA阶段, fase QA, phase QA, QA-Phase, fase QA.
539SKILL.mdUpdated Apr 18, 2026