skill status

Other Community

Skill notes

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"

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

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 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
No explicit requirements detected
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: 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

02
Step 2: Scan Project-Local Skills

Read project skills directory: `.claude/skills/project/*/SKILL.md` For each skill, read frontmatter Count total project skills

03
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"

04
Step 4: Display Report

Step 4: Display Report

Discussion

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