Generate layered inventory reports of loaded skills from SKILL.md frontmatter.
npx skills add https://github.com/hendrax5/ironman --skill skill-status-hendrax5
Please help me install this Agent Skill. Skill: skill-status Source: https://github.com/hendrax5/ironman/tree/main/skills/skill-status Command: npx skills add https://github.com/hendrax5/ironman --skill skill-status-hendrax5
Provide a clear, read-only inventory of loaded skills across core (bkit/plugin-managed) and project-local layers to help discover duplicates, overrides, and coverage gaps without manual file inspection.
Run the skill-status command to generate a layered report of core and project-local skills and include --detail or --conflicts to expand or filter the output.
High-intent search queries and answers about installing and using this skill.
Skill conflict detection works by scanning core and project-local directories, reading SKILL.md frontmatter, and comparing names and triggers to identify shadowing or overrides. You can run the status command with --conflicts to filter output for collisions only.
A layered inventory report scans core and project-local skill directories, summarizes SKILL.md frontmatter, and maps coverage to help discover duplicates and gaps. Running the skill-status command generates this read-only overview without manual file inspection.
Yes, detailed skill metadata viewing is supported by running the status command with the --detail option. This expands the layered inventory report to include comprehensive SKILL.md frontmatter information for both core and project-local skills.
Trigger shadowing happens when project-local skills share identical names or triggers with core bkit skills. Running a conflict detection report identifies these collisions by comparing frontmatter across layers, helping you document coverage and prevent unintentional overrides.
No dependencies are required to run skill inventory and conflict detection. It applies to environments using bkit plugin-managed core skills and project-local .claude skills, reading SKILL.md frontmatter directly from those directories to generate status reports.
Running a skill coverage audit is ideal when onboarding a new feature to ensure project-local skills do not unintentionally override core skills. It documents current skill coverage and maps triggers to prevent conflicts before deployment.
shawn-sandyAudit repository structure and scaffold Claude Code marketplace configuration files.
dangngocbinhImport local media files into a structured imports/ directory with collision-safe filenames.
indiesoftbyAutomate maintenance tasks for Defold agent skills and proto references.
shakefuParse SKILL.md frontmatter to list skills, descriptions, and tools.
