What problem does it solve?
Integrating YALC into an existing Claude Code setup can cause skill name collisions, trigger-routing ambiguity, and duplicated or conflicting context. This Skill helps you reconcile the two environments by analyzing what’s already in your repo and producing a reviewable integration plan before any changes occur.
Core Features & Use Cases
- Read-only repo analysis: Scans your existing
.claude/ skills and CLAUDE.md (and optionally .claude/rules/) to understand your current behavior.
- YALC-side registry review: Compares your skills against YALC’s skill registry to identify exact name matches and likely trigger overlaps.
- Conflict-aware mapping: Flags hard collisions (identical skill
name) as errors and soft collisions (trigger overlap) as warnings, then recommends how to proceed.
- Context migration via preview: Plans a safe move of relevant context into
~/.gtm-os/_preview/ without touching live YALC files until you confirm.
Quick Start
Use this integration skill by telling it your existing Claude Code repo absolute path and a one-line description of what that repo does.