skills-manager_skill

This skill audits, consolidates, and safely manages Claude Code skills by verifying project state and usage patterns before changes.
  • Python

648

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill ananddtyagi/cc-marketplace --skill skills-manager

  • SKILL.md29.0 KB

Overview

This skill is a universal consolidation and audit tool for Claude Code skills that inspects your actual project state, usage, and code before recommending or performing changes. It detects redundancies, ranks necessity, and safely manages merges, archives, and deletions with backups, confirmations, and rollback support.

How this skill works

It first scans the repository to detect project type, primary technologies, and directory layout, then inventories all skills and extracts metadata, triggers, and capabilities. Next it analyzes usage by inspecting git history and inter-skill references, computes necessity scores, and runs capability and trigger-overlap checks to surface redundancy. All destructive actions are gated by explicit user confirmation, automatic backups, and rollback procedures.

When to use it

  • When you need to audit which Claude Code skills are actually used versus unused
  • When you want to consolidate overlapping or duplicate skills safely
  • When you plan to archive obsolete skills while retaining the ability to restore them
  • When you want to reorganize skills to match current project structure and priorities
  • During regular maintenance to keep the skillset lean and relevant

Best practices

  • Always run a full /skills-audit pass before proposing consolidation or archive actions
  • Keep conservative thresholds for merges (e.g., ≥85% similarity) and require manual approval
  • Use git history and recent usage (last 90–180 days) as primary signals for necessity scoring
  • Back up skill files and record a rollback point before any archive, merge, or delete
  • Refine activation triggers to eliminate exact-match conflicts instead of deleting skills

Example use cases

  • Identify and merge two near-duplicate Vue debugging skills to centralize fixes and reduce trigger conflicts
  • Archive an obsolete skill that references deprecated frameworks after confirming zero usage in 180+ days
  • Generate a consolidation plan that ranks skills by necessity and recommends low-risk merges
  • Detect trigger collisions across multiple skills and propose trigger specificity updates
  • Create safe rollback points and backups before applying bulk skill reorganizations

FAQ

No. Destructive actions require explicit user confirmation and a backup is created before any deletion or archive; rollback is supported.

How does it decide which skills to merge?

It uses necessity scoring, capability overlap (keyword and Jaccard similarity), trigger conflict analysis, and conservative rules such as high similarity with low usage overlap to recommend merges.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational