skills-curate

Audits a skill collection for stale entries and overlapping clusters, staging merge or archive proposals.

6|1|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/t-mercier/ai-agents-orchestrator --skill skills-curate-t-mercier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skills-curate
Source: https://github.com/t-mercier/ai-agents-orchestrator/tree/main/skills/skills-curate
Command: npx skills add https://github.com/t-mercier/ai-agents-orchestrator --skill skills-curate-t-mercier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Over time an AI agent's skill collection inflates with near-duplicate skills and dormant entries, making discovery harder and triggers ambiguous. This Skill performs a periodic curation pass over the whole collection, refreshing usage data from transcripts and identifying clusters that should be consolidated — without ever deleting anything or acting without review. ## Core Features & Use Cases - Usage-driven state machine: Refreshes usage counters from transcripts and reports each skill as active, stale (30 days), or archived (90 days), with a grace floor for never-used skills. - Cluster detection and consolidation: Groups skills by prefix or domain keyword and proposes merging near-siblings into one umbrella skill with labelled subsections, or demoting narrow skills to reference/template/script files. - Safe staged proposals: Writes every merge, new-skill, or archive proposal to a pending directory for human review via /skills-review; only agent-proposed skills are ever moved, and dependency checks (launchd jobs, other skills, app config) prevent dangling references. - Use Case: After months of agent sessions, you have five pr-* skills that overlap. Run the curation pass to get a staged proposal merging them into one umbrella skill, with archive proposals for the absorbed siblings — nothing changes until you approve it. ## Quick Start Ask the agent to curate the skills collection and stage consolidation proposals for review.

Frequently Asked Questions about skills-curate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce duplicate or overlapping AI agent skills?

Run a curation pass that groups skills by prefix or domain keyword and judges whether a human maintainer would write them as one skill with labelled subsections. Overlapping siblings are merged into an umbrella skill or demoted to reference files, with all changes staged as proposals for review.

How do I find unused or stale skills in my collection?

Refresh usage counters from session transcripts with the skill_usage.py scan and report commands. Skills are classified as active, stale after 30 days, or archived after 90 days, with a grace floor so recently created skills are not penalized for lacking usage.

Does the curation pass delete skills automatically?

No. The maximum action is archiving, which moves a skill directory to a recoverable archive folder, and even that is only staged as a proposal. Nothing changes in the live skills directory until a human approves it through the review step.

Can curation modify hand-written skills I created myself?

No. Only skills marked with origin agent-proposed in their frontmatter can be staged for moves or archives. Hand-written skills may be reported as part of an overlapping cluster, but no action is ever staged for them.

What happens if another tool or job depends on a skill being archived?

Before staging any archive, the pass checks launchd jobs, other skills, global instructions, and the app config for references to the skill name. Referenced skills are skipped or consolidated with the reference explicitly moved, never archived and left dangling.