agentleFS
Sign inStart free
ww-w-aiww-w-ai/bkit-claude-code/skills/skill-status/SKILL.md

skill-status

Skill605 starsChanged 3 months agoApache-2.0View on GitHub

Show loaded skill inventory — bkit core vs project-local, conflicts, coverage gaps. Triggers: skill-status, skill list

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read bkit core skills directory: ~/.claude/plugins/cache/bkit-marketplace/bkit/*/skills/

    line 29
  2. Very specific:

    Read project skills directory: .claude/skills/project/*/SKILL.md

    line 37
  3. Distinctive:

    If same name exists in both: mark as "override" (project wins)

    line 45
  4. Distinctive:

    If project skill triggers overlap with core: mark as "shadow"

    line 46
  5. Distinctive:

    When a project skill has the same name as a core skill, the project skill takes precedence.

    line 99

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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
  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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free