integrate-with-yalc

Analyze Claude Code and YALC skill registries to plan a conflict-free integration.

277|88|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system --skill integrate-with-yalc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: integrate-with-yalc
Source: https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system/tree/main/.claude/skills/integrate-with-yalc
Command: npx skills add https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system --skill integrate-with-yalc

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about integrate-with-yalc

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

FAQPage Schema
How do I merge my Claude Code skills with YALC without causing trigger routing conflicts?

To merge Claude Code skills with YALC without trigger routing conflicts, perform a read-only analysis of both skill registries to detect hard name collisions and soft trigger overlaps, generating a safe migration plan before applying changes.

What happens when Claude Code and YALC skills have identical names or overlapping triggers?

When Claude Code and YALC skills have identical names or overlapping triggers, the integration analysis flags exact name matches as hard collision errors and trigger overlaps as soft collision warnings, recommending specific actions to resolve them.

Can I preview YALC integration changes before modifying my live Claude Code configuration?

Yes, you can preview YALC integration changes before modifying live files. The migration plan stages all context changes into a designated preview directory, keeping your active YALC files untouched until you explicitly confirm the application.

What is the best way to migrate CLAUDE.md rules and .claude/ skills into a YALC environment?

The best way to migrate CLAUDE.md rules and .claude/ skills into a YALC environment is to use an automated conflict-aware mapping tool that compares registries and stages context safely into a preview directory pending confirmation.

Why does integrating YALC break existing Claude Code workspace layouts and context?

Integrating YALC breaks existing Claude Code workspace layouts and context because it introduces skill name collisions, trigger-routing ambiguity, and duplicated rules that conflict with your current .claude/ setup if not properly reconciled beforehand.