skill-library-curation

原文涵盖的主题

• Skill Library Curation
• Core rules
• Auditing one workflow skill for protocol integrity
• Upstream-maintenance retirement rule
• Installer provenance and warning triage
• Upstream freshness — verify by HEAD diff, not the lock timestamp
• Review procedure
• Execution procedure after explicit confirmation

Use this for library review, pruning/overlap/consolidation proposals, or usage-based skill discovery. Review and recommendation are distinct modes; execution requires its own explicitly confirmed scope. For recurring discovery, follow references/usage-based-recommendations.md, not a whole-library sweep. Moving a skill out of the runtime into a shared/public repo is a different job — porting and publishing (de-coupling axes, generated catalogs, canonical-source swap), not this skill. Be active: a meaningful library review should produce a reusable inventory, classification, or skill-library improvement; do not turn “no deletion yet” into “no work done.” Be conservative: zero usage is evidence, not proof of low value. If the owner's scenario is unclear, classify needs confirmation and do not guess. Keep skills class-level: prefer one reusable workflow skill with a small topical reference set over many narrow incident skills or one umbrella with a reference file per session. Report overlap explicitly. Do not silently merge or delete a skill because another one looks similar. For usage-based discovery, ground recommendations in the owner's actual preceding-week activity, not agent-gene

这里只展示节选，请以完整原文和当前要求为准。