Possible complementary direction: skill lifecycle governance with SkillClaw

Hi, I'd like to suggest a complementary direction for `web-quality-skills`.

Project:
https://github.com/AMAP-ML/SkillClaw

Your project focuses on quality-focused developer skills.

SkillClaw focuses on long-term skill lifecycle management after repeated usage: deduplication, merging, quality improvement, and sharing across agents or devices.

One reason I think the overlap is interesting is that once a skill library evolves over time, governance becomes more important as well. A lifecycle layer like SkillClaw and a validation / scanning / quality layer like your project seem naturally complementary.

If useful, I can send a concise technical summary or a more concrete workflow angle.

Paper:
https://arxiv.org/abs/2604.08377