plugins/analytics/skills/product-metrics/SKILL.md
View key product metrics, KPIs, and conversion rates from PostHog
npx skillsauth add coalesce-labs/catalyst product-metricsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Query PostHog for key product metrics, KPIs, and performance indicators.
/product-metrics [metric-type] [time-range]
Examples:
/product-metrics "overall KPIs last 30 days"
/product-metrics "conversion rates this quarter"
/product-metrics "feature usage breakdown this week"
/product-metrics "Show me our key metrics for last month: MAU, conversion rates, and top features"
/product-metrics "Breakdown of our signup to paid funnel with drop-off rates at each step"
/product-metrics "Compare usage of our top 5 features over the last quarter"
/product-metrics "How do our December signups compare to November in terms of activation and retention?"
Results typically include:
today, yesterdaylast 7 days, last 30 days, last 90 daysthis week, last weekthis month, last month, this quarter2024-01-01 to 2024-03-31Add segmentation to any query:
/product-metrics "MAU by country"
/product-metrics "conversion rates by traffic source"
/product-metrics "feature usage by plan type"
This plugin consumes ~40k tokens. Disable after viewing metrics:
/plugin disable catalyst-analytics
See also: /catalyst-analytics:analyze-user-behavior, /catalyst-analytics:segment-analysis
development
Migrate a single-harness repo to the dual-harness layout so both Claude Code and Codex load the same instructions and skills — AGENTS.md as the portable canonical doc, a thin CLAUDE.md `@AGENTS.md` bridge, and a `.agents/skills` dir with a `.claude/skills` symlink onto it. Use when asked to migrate to dual-harness, make this repo work in both Claude and Codex, or for agent metadata cleanup.
tools
Goal-driven senior-engineer pipeline-unstick sweep (CTL-1176 rung 3). Given the stuck/failed/needs-human set (or ONE ticket handed by the recovery router), its GOAL is to get the pipeline MOVING again — not to fix one ticket's review findings (that is phase-remediate). It runs AFTER the eyes (diagnostician evidence) and the hands (deterministic unstuck-sweep seams) have already tried, and it CONSUMES their output from a recovery-pass.json brief rather than re-diagnosing or redoing their narrow work. It acts like a senior engineer with full tool access — it resolves merge conflicts, rebases, force-pushes, merges green PRs, and re-dispatches stalled phases AUTONOMOUSLY — and escalates to the operator ONLY for a genuine value judgment / something that degrades other functionality / a real cost-benefit trade-off / a serious architecture change / an ADR conflict. On escalation it AUTHORS the operator inbox row + the push notification (executive-voiced). Dispatched as a `claude --bg` job by phase-agent-dispatch via slash command, AND invocable bare by the operator as a sweep — hence `user-invocable: true`. Ships behind CATALYST_RECOVERY_PASS (off by default — no live behavior change until shadow/enforce).
tools
Diagnose and fix Catalyst setup issues. Validates tools, database, config, OTel, direnv, and thoughts. Automatically fixes what it can — creates directories, initializes the database, sets WAL mode, runs migrations. Use for new installs, upgrades, or when something isn't working.
tools
--- name: phase-triage description: Phase agent that triages a Linear ticket — expands acronyms, classifies (feature/bug/docs/refactor/chore), identifies genuine blockers (a semantic second-pass over the backlog — NOT a prose scrape; CTL-838), estimates scope, writes triage.json, and posts a triage analysis comment to Linear. Triage completion is signaled by that comment plus the local triage.json — there is no `triaged` label. Emits phase.triage.complete.<TICKET> on success and phase.triage.fai