skill-status
Skill66 starsChanged 7 months agoApache-2.0View on GitHub
Show loaded skills inventory with status, classification, and coverage information. Lists all skills from the skills/ directory with their activation state.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- kannaka-labs/Kannaktopustheir own version, first seen Oct 13, 2026
- popup-studio-ai/bkit-claude-codetheir own version, first seen Oct 8, 2026
- Terum-Inc/terum-skillstheir own version, first seen Sep 20, 2026
- ww-w-ai/bkit-claude-codetheir own version, first seen Aug 14, 2026
- nyldn/claude-octopustheir own version, first seen Aug 13, 2026
- XBuilderLAB/cheat-on-skilltheir own version, first seen Jun 27, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- nyldn/claude-octopus★ 4.4ksame name
- popup-studio-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-claude-code★ 605same name
- XBuilderLAB/cheat-on-skill★ 191same name
- Terum-Inc/terum-skills★ 28same name
- kannaka-labs/Kannaktopus★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository42 other files it gives its agents.
- auditSkill
- batchSkill
- bkend-authSkill
- bkend-cookbookSkill
- bkend-dataSkill
- bkend-guidesSkill
- bkend-mcpSkill
- bkend-quickstartSkill
- bkend-securitySkill
- bkend-storageSkill
- bkit-rulesSkill
- bkit-templatesSkill
- btwSkill
- code-reviewSkill
- controlSkill
- deploySkill
- desktop-appSkill
- development-pipelineSkill
- dynamicSkill
- enterpriseSkill
- gemini-cli-learningSkill
- loopSkill
- mobile-appSkill
- output-style-setupSkill
- pdcaSkill
- phase-1-schemaSkill
- phase-2-conventionSkill
- phase-3-mockupSkill
- phase-4-apiSkill
- phase-5-design-systemSkill
- phase-6-ui-integrationSkill
- phase-7-seo-securitySkill
- phase-8-reviewSkill
- phase-9-deploymentSkill
- plan-plusSkill
- pm-discoverySkill
- qa-phaseSkill
- rollbackSkill
- simplifySkill
- skill-createSkill
- starterSkill
- zero-script-qaSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
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
- Distinctive: line 57
If skill file exists, parse YAML frontmatter for metadata
- Distinctive: line 137
Check for potential issues:
- Very specific: line 144
Use /skill-status before /skill-create to check for conflicts
- Very specific: line 145
Use --verbose to debug skill activation issues
“Common” is measured: kept by at least 6 in 10 of the 5 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.
Files
Skill Status
Show all loaded skills with classification, status, and coverage analysis
Commands
| Command | Description | Example |
/skill-status | Show skill inventory summary | /skill-status |
/skill-status --verbose | Show detailed per-skill info | /skill-status --verbose |
How to Execute
1. Scan Skills Directory
- List all directories under
skills/ - For each directory, check if
SKILL.mdorskill.mdexists - If skill file exists, parse YAML frontmatter for metadata
2. Categorize Skills
Group skills by source:
- bkit Core: Skills shipped with bkit extension
- Project-Local: Skills added by the project team
Group skills by classification:
- W (Workflow): Multi-step process skills
- C (Command): Single-action skills
- G (Guide): Educational/reference skills
3. Determine Status
For each skill:
- Active: Has SKILL.md with valid frontmatter
- Empty: Directory exists but no SKILL.md (stub)
- Error: SKILL.md exists but has invalid frontmatter
4. Coverage Analysis
Calculate coverage metrics:
- Total skill directories vs active skills
- PDCA phase coverage (plan, design, do, check, act)
- Agent integration coverage (which skills reference agents)
Output Format
Summary View (Default)
## bkit Skill Inventory
### Summary
- Total: 35 skills | Active: 33 | Empty: 0 | Error: 2
### By Classification
- Workflow (W): 12 skills
- Command (C): 18 skills
- Guide (G): 5 skills
### Skills
| # | Name | Class | Phase | Status |
|---|------|-------|-------|--------|
| 1 | pdca | W | all | Active |
| 2 | code-review | C | do | Active |
| 3 | deploy | W | do | Active |
| 4 | audit | C | check | Active |
| ... | | | | |
### PDCA Coverage
- Plan: 4 skills
- Design: 3 skills
- Do: 8 skills
- Check: 6 skills
- Act: 3 skillsVerbose View (--verbose)
Adds for each skill:
- Description (first line)
- Trigger keywords
- Allowed tools list
- Agent integrations
- Import dependencies
### pdca (Workflow)
- **Phase**: all
- **Triggers**: pdca, plan, design, analyze...
- **Tools**: read_file, write_file, glob, grep_search, tracker_*
- **Agents**: gap-detector, pdca-iterator, report-generator
- **Imports**: 4 templatesConflict Detection
Check for potential issues:
- Duplicate triggers: Two skills with the same trigger keyword
- Missing agents: Skill references an agent that does not exist
- Circular imports: Skill A imports B which imports A
Integration
- Use
/skill-statusbefore/skill-createto check for conflicts - Use
--verboseto debug skill activation issues - Results help identify coverage gaps in the PDCA workflow
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
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.

