/cm-skill-index

name: cm-skill-index
description: "Progressive Disclosure skill index — efficient skill loading in 3 layers. Layer 1 (index, ~100 tokens) always loaded. Layer 2 (summary, ~300 tokens) loaded on context need. Layer 3 (full SKILL.md) loaded on execution only."
token_budget: 800
compressed: true
deprecated: false

Skill Index — Progressive Disclosure Engine

TL;DR

• **Use when** searching for a CodyMaster or community skill
• **Layered**: L1 index (always loaded) → L2 summary → L3 full
• **Includes**: discovery, search, mastery (consolidated in v6)

> **Save 90%+ tokens.** Agents scan the index first, load full skills only when executing. > Inspired by Loki Mode's 3-Layer Progressive Disclosure memory architecture.

The Problem

Traditional approach: Load every SKILL.md to decide which skill to use.

• 30+ skills × ~3000 tokens each = **90,000+ tokens just for discovery**
• Agent only needs ~500 tokens to make the choice
• **89,500 tokens wasted on reading full skills**

The Solution: 3-Layer Loading

┌────────────────────────────────────────────────┐
│ LAYER 1: INDEX (~100 tokens per skill)          │
│ Always loaded. Quick scan. "What exists?"        │
│ Name + Domain + Triggers + 1-line summary       │
└─────────────────────┬──────────────────────────┘
                      │ (match found?)
                      v
┌────────────────────────────────────────────────┐
│ LAYER 2: SUMMARY (~300 tokens per skill)        │
│ Load when choosing. "Is this the right one?"     │
│ Description + When to use + Integration table   │
└─────────────────────┬──────────────────────────┘
                      │ (confirmed?)
                      v
┌────────────────────────────────────────────────┐
│ LAYER 3: FULL SKILL.md (1500-5000 tokens)       │
│ Load ONLY during execution. "How to use it."     │
│ Complete instructions, examples, red flags       │
└────────────────────────────────────────────────┘

Layer 1: Skill Index

**Always loaded by agents at session start.** Maximum 100 tokens per skill.

Engineering Swarm 🔧

| Skill | Triggers | Summary | |-------|----------|---------| | `cm-tdd` | test, TDD, red-green-refactor | Red-Green-Refactor cycle before any implementation | | `cm-debugging` | bug, error, fix, debug, broken | Root cause analysis before fixing. 5-phase investigation | | `cm-quality-gate` | deploy, ship, verify, quality, gate | 6-gate verification: static analysis → blind review → ship | | `cm-quality-gate` | test setup, CI, verification | Test + verification gate before claiming completion | | `cm-code-review` | review, PR, feedback, branch | Request reviews, handle feedback, complete branches | | `cm-codeintell` | understand codebase, call graph, impact, architecture, what calls X, what breaks | AST knowledge graph + architecture diagrams + smart context (30% fewer tokens) | | `cm-reactor` | rewrite, pivot, migrate, direction change, architecture wrong, restructure | TRIZ-powered strategic codebase re-direction — 5-phase incremental migration | | `cm-clean-code` | clean, dead code, refactor, code smell, DRY, SOLID, naming, messy | 7-point hygiene gate: dead code, imports, naming, SRP, DRY, nesting |

Operations Swarm ⚙️

| Skill | Triggers | Summary | |-------|----------|---------| | `cm-safe-deploy` | deploy, staging, production, release | Multi-gate deploy pipeline with rollback strategy | | `cm-identity-guard` | git push, deploy, Cloudflare, Supabase, account | Verify identity before any push/deploy to prevent wrong-account | | `cm-execution` | branch, isolate, worktree, parallel | Execution modes including isolated workspaces and parallel batches | | `cm-terminal` | command, terminal, run, execute | Safe terminal execution with progress logging |

Security Swarm 🔒

| Skill | Triggers | Summary | |-------|----------|---------| | `cm-safe-deploy` | secret, token, leak, security, scan, pre-commit, gitleaks, rotate | Defense-in-depth: repo scanning, token lifecycle, and release safety |

Product Swarm 🎨

| Skill | Triggers | Summary | |-------|----------|---------| | `cm-brainstorm-idea` | analyze, enhance, improve, initiative, evaluate, review product | Strategic analysis gate: 9 Windows + Double Diamond → 2-3 qualified options | | `cm-planning` | plan, design, brainstorm, feature | Brainstorm intent → write implementation plan → then code | | `cm-ux-master` | UI, UX, design, interface, usability | 48 UX Laws + 37 Design Tests + Figma/Stitch integration | | `cm-design-system` | preview, visual, mockup, render UI, wireframe | Live UI concept generation via design-token and Stitch/Open Design workflows | | `cm-dockit` | docs, documentation, knowledge base, SOP | Generate complete knowledge base from codebase | | `cm-project-bootstrap` | new project, init, bootstrap, setup | Full project setup: design system → staging → CI → deploy | | `cm-jtbd` | customer discovery, JTBD, jobs to be done, product-market fit, why users churn | JTBD canvas: Switch Interview → Outcome Metrics → Opportunity Scoring |

Growth Swarm 📈

| Skill | Triggers | Summary | |-------|----------|---------| | `cm-content-factory` | content, blog, article, marketing | AI content engine: research → generate → audit → deploy | | `cm-ads-tracker` | pixel, tracking, GTM, Meta, TikTok, Google Ads | Complete conversion tracking setup across platforms | | `cm-cro-methodology` | conversion, A/B test, landing page, funnel | CRO audit: funnel mapping → persuasion → objection handling |

Orchestration Swarm 🎯

| Skill | Triggers | Summary | |-------|----------|---------| | `cm-execution` | execute, implement, plan, RARV, batch | Execute plans: batch mode, subagent-driven, parallel, or RARV | | `cm-continuity` | memory, context, CONTINUITY, learnings | Working memory protocol: read at start, update at end | | `cm-skill-index` | which skill, skill list, discover, help | Meta-skill: when to invoke skills and how to discover the right one | | `cm-skill-health` | skill broken, skil