coalesce-labs/segment-analysis
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.
$ install --global
skillsauthnpx skillsauth add coalesce-labs/catalyst segment-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 21, 2026, 2:50 AM188.8s1 file scanned
SKILL.md
- name:
- segment-analysis
- description:
- 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.
- disable-model-invocation:
- false
- allowed-tools:
- Task, TodoWrite
- version:
- 1.0.0
Segment Analysis
Deep-dive into specific user segments, cohorts, or customer groups using PostHog data.
Usage
/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"
What This Analyzes
User Segments
- By plan type (free, pro, enterprise)
- By geography (country, region)
- By acquisition source (organic, paid, referral)
- By behavior (power users, casual users, at-risk)
Cohort Analysis
- By signup date (monthly, weekly cohorts)
- By first feature used
- By activation milestone reached
- By engagement level
Comparison Analysis
- Segment A vs Segment B
- Before/after feature launch
- Treatment vs control (A/B tests)
- Time period comparisons
Example Analyses
Plan Comparison
/segment-analysis "Compare engagement patterns between free and paid users: session frequency, feature usage, retention"
Power User Identification
/segment-analysis "Identify our power users: who are they, what features do they use, what's their profile?"
Churn Analysis
/segment-analysis "Analyze users who churned: what were their last actions, which features didn't they use?"
Geographic Performance
/segment-analysis "Compare conversion rates and engagement across our top 5 countries"
Cohort Retention
/segment-analysis "Show retention curves for each monthly signup cohort in 2024"
Output Format
Analysis typically includes:
- Segment characteristics (size, demographics, behavior)
- Key metrics for each segment
- Comparative insights between segments
- Behavior patterns unique to segment
- Recommendations for targeting or improvement
Segmentation Criteria
You can segment by:
- Demographics: Country, language, device type
- Behavior: Feature usage, session frequency, engagement score
- Business: Plan type, payment history, LTV
- Temporal: Signup date, last active, tenure
- Custom: Any event or property in PostHog
Advanced Analysis
Multi-dimensional Segmentation
/segment-analysis "Power users (5+ sessions/week) from enterprise plans who use feature X"
Funnel by Segment
/segment-analysis "Compare signup to activation funnel for organic vs paid traffic"
Retention by Segment
/segment-analysis "30-day retention by initial feature used"
Tips for Better Analysis
- Be specific - Define your segment clearly
- Ask for comparisons - "vs" between segments reveals insights
- Look for patterns - What makes segments different?
- Consider time - Trends over time matter
- Combine criteria - Multi-dimensional segments can be revealing
Context Cost
Plugin uses ~40k tokens. Disable when analysis is complete:
/plugin disable catalyst-analytics
See also: /catalyst-analytics:analyze-user-behavior, /catalyst-analytics:product-metrics
Related Skills
coalesce-labs/phase-remediate
testing
VerifiedTrustedCommunity
Phase-agent that fixes a failing verify verdict so the pipeline self-heals instead of stalling to needs-human (CTL-653). Reads `${ORCH_DIR}/workers/<ticket>/verify.json`, fixes the `findings[]` (every severity:"high" plus the regression_risk drivers) directly via Edit/Write, commits the remediation, and emits `phase.remediate.complete.<ticket>`. The scheduler's router then re-dispatches `verify` to re-check (the verify⇄remediate cycle, cap 3). Dispatched as a `claude --bg` job by `phase-agent-dispatch`, which invokes it via slash command — hence `user-invocable: true`.
14SKILL.mdUpdated May 28, 2026
coalesce-labs/plugins/dev/skills/phase-triage
tools
VerifiedTrustedCommunity
--- 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
14SKILL.mdUpdated May 18, 2026
coalesce-labs/phase-research
tools
VerifiedTrustedCommunity
Phase agent for the research step of the 9-phase orchestrator pipeline (CTL-450). Wraps /catalyst-dev:research-codebase and produces thoughts/shared/research/<date>-<ticket>.md, then emits phase.research.complete.<ticket>. Reads triage.json from the worker dir as its prior-phase artifact. Spawned via plugins/dev/scripts/phase-agent-dispatch, which invokes it via slash command — hence `user-invocable: true`.
14SKILL.mdUpdated May 18, 2026
coalesce-labs/phase-pr
development
VerifiedTrustedCommunity
Phase-agent wrapper that opens the pull request after implementation completes (CTL-449 Initiative 1 Phase 3). Delegates to `/catalyst-dev:create-pr` (which already auto-runs `describe-pr` and transitions Linear to `inReview`), then writes the PR number + URL into the phase signal file so the downstream `phase-monitor-merge` agent can read it without re-querying GitHub. Dispatched as a `claude --bg` job by `phase-agent-dispatch`, which invokes it via slash command — hence `user-invocable: true`.
14SKILL.mdUpdated May 18, 2026