YuukiAS Skill Library Analysis
Use this to keep a large skill collection coherent. The goal is to reduce duplicates and preserve provenance, not to maximize skill count.
Workflow
- Inventory candidate skills with path, name, description, provenance, license, and upstream commit.
- Group by user task, not by repository.
- Compare each group against existing local skills:
- exact duplicate;
- same trigger with stronger references;
- complementary capability;
- plugin-only or software-only source;
- unclear license or provenance.
- Choose one action:
- merge into existing skill;
- create one new local skill;
- record only;
- reject as software/non-skill;
- defer because of conflict.
- Record decisions in a tracked source log before deleting scratch clones.
Quality Rules
- Do not bulk-import a repository when a distilled local skill is enough.
- Do not keep multiple active skills with the same trigger boundary.
- Do not hide conflicts; record them for user decision.
- Prefer profile and marketplace aggregation over many near-duplicate installable skills.