plugins/analytics/skills/segment-analysis/SKILL.md
Analyze user segments, cohorts, and customer groups using PostHog data. Creates retention tables, compares segment behavior, and generates group breakdowns. Use when the user asks about customer segmentation, cohort retention, user group comparison, churn analysis, or funnel analysis by segment.
npx skillsauth add coalesce-labs/catalyst segment-analysisInstall 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.
Deep-dive into specific user segments, cohorts, or customer groups using PostHog data.
/segment-analysis <segment-description>
Examples:
/segment-analysis "users from paid plans vs free plans"
/segment-analysis "power users who use feature X daily"
/segment-analysis "users who churned in last 30 days"
/segment-analysis "cohort: signed up in Q4 2024"
/segment-analysis "Compare engagement patterns between free and paid users: session frequency, feature usage, retention"
/segment-analysis "Identify our power users: who are they, what features do they use, what's their profile?"
/segment-analysis "Analyze users who churned: what were their last actions, which features didn't they use?"
/segment-analysis "Compare conversion rates and engagement across our top 5 countries"
/segment-analysis "Show retention curves for each monthly signup cohort in 2024"
Analysis typically includes:
You can segment by:
/segment-analysis "Power users (5+ sessions/week) from enterprise plans who use feature X"
/segment-analysis "Compare signup to activation funnel for organic vs paid traffic"
/segment-analysis "30-day retention by initial feature used"
Plugin uses ~40k tokens. Disable when analysis is complete:
/plugin disable catalyst-analytics
See also: /catalyst-analytics:analyze-user-behavior, /catalyst-analytics:product-metrics
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