metrics-pull

# Metrics Pull Skill Unified pull across all metric sources configured in `.claude/jit-tooling/active-metrics.yml`. Dispatches to per-source adapters (starting with `github`), normalizes to a shared schema, computes deltas, and drafts canvas evidence entries. This skill is the L0/L1/L2/L5 evidence-gathering loop. Replaces manual "I checked the dashboard" reports with timestamped, sourced, diffable data. ## When to Use - Before `/mycelium:diamond-assess` at L0/L1/L2/L5, if the newest snapshot is >7 days old. - After any public activity (launch, post, conference mention) — typically 24-48h later to capture the bump. - Weekly baseline, regardless of activity. - Ad hoc when the user wants a fresh read. ## Precondition: .claude/jit-tooling/active-metrics.yml exists If `.claude/jit-tooling/active-metrics.yml` does NOT exist: 1. Tell the user: "No metric sources are configured. Running `/mycelium:metrics-detect` first." 2. Invoke `/mycelium:metrics-detect` (or follow `${CLAUDE_PLUGIN_ROOT}/jit-tooling/metrics-detector.md`). 3. After detection completes, return to this skill. ## Workflow ### Step 1: Load configuration Read `.claude/jit-tooling/active-metrics.yml`. Filter to sources with `status: active`. For each, verify the adapter file exists at `${CLAUDE_PLUGIN_ROOT}/jit-tooling/metrics-adapters/<source>.md`. If missing, follow `${CLAUDE_PLUGIN_ROOT}/jit-tooling/metrics-adapters/GENERATING.md` to generate it. If `confirmed_by_user: false`, ask the user to confirm the so...