metrics-pull
Pull snapshots from all configured metric sources, compute deltas against prior snapshots, flag unexplained signals, and draft evidence entries for canvas files. One entry point for all external product/market metrics.
npx skills add majiayu000/claude-skill-registry --skill metrics-pull-haabe-mycelium-3 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 `s
- When to Use
- Precondition: .claude/jit-tooling/active-metrics.yml exists
- Workflow
- Step 1: Load configuration
- Step 2: Dispatch adapters in parallel
- Step 3: Save raw snapshots
- Step 4: Load prior snapshots
- Step 5: Compute deltas
- Step 6: Flag unexplained signals
- Step 7: Generate combined report
- Step 8: Draft evidence entries
- Step 9: Update .claude/jit-tooling/active-metrics.yml
- Step 10: Anomaly → devils-advocate auto-chain (added v0.29.0)
- Parallel dispatch
What does the metrics-pull skill do?
Pull snapshots from all configured metric sources, compute deltas against prior snapshots, flag unexplained signals, and draft evidence entries for canvas files. One entry point for all external product/market metrics.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill metrics-pull-haabe-mycelium-3 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.