Metrics Detect
Apps & Automationmetrics-detectMetrics Detect is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Detect which external metric sources apply to this product (GitHub, Plausible, Stripe, etc.) and configure adapters. Retrofit entry point for projects that started before v0.14; also runnable to refresh source list when the product grows.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/integration/metrics-detect/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/metrics-detect, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Metrics Detect Skill
Retrofit entry point for .claude/jit-tooling/metrics-detector.md. For new projects this runs automatically inside /interview Phase 6. Use this skill when:
- The project existed before v0.14 and has no
active-metrics.yml. - New infrastructure has been added (new analytics provider, new app store, new payment processor) and source list needs refresh.
- An existing adapter is >180 days old and needs regeneration.
- The user explicitly wants to review / reconfigure metric sources.
Workflow
Follow .claude/jit-tooling/metrics-detector.md end-to-end:
- Signal scan — check git remote, package manifests, env vars, SDK installs.
- Ask the user — deployment URL, payment provider, app stores, support channels (things the repo does not reveal).
- Confirm each candidate source — yes / no / later.
- Ensure adapters exist — for each confirmed source, check
metrics-adapters/<source>.md. If missing, followmetrics-adapters/GENERATING.mdto generate one, present to user, save on confirmation. - Write
active-metrics.yml— detected + user-declared sources, withconfirmed_by_user: falseuntil the user approves the full set. - Confirm with user — show the full source list; set
confirmed_by_user: trueafter approval.
Credentials
Mycelium is NOT a secrets manager. For each source, state what the user needs in their environment (env var names, vendor CLI auth) and verify they have it before marking the source active. If they don't, mark status: deferred and move on — do not block detection on setup.
Output
.claude/jit-tooling/active-metrics.yml(or update to existing)- Generated adapters in
.claude/jit-tooling/metrics-adapters/<source>.md(one per novel source) - Clear next step to the user: "Ready. Run
/metrics-pullto fetch your first snapshot."
What This Skill Does NOT Do
- Does NOT pull data. Detection only. Keep the phases separate so the user can review before any network calls.
- Does NOT store credentials.
- Does NOT assume; always asks for sources that cannot be detected from the repo (deployed URLs, payment processors, app stores).
Theory Citations
- Gilad: evidence gathering is infrastructure — the cost of pulling must be near-zero for users to do it reliably.
- Mycelium's JiT philosophy: detect and configure on demand, don't pre-ship per-source complexity.