coalesce-labs/analyze-user-behavior
plugins/analytics/skills/analyze-user-behavior/SKILL.md
Analyze user behavior patterns and cohorts using PostHog
$ install --global
skillsauthnpx skillsauth add coalesce-labs/catalyst analyze-user-behaviorInstall 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: Apr 30, 2026, 3:16 AM17.3s1 file scanned
SKILL.md
- name:
- analyze-user-behavior
- description:
- Analyze user behavior patterns and cohorts using PostHog
- disable-model-invocation:
- false
- allowed-tools:
- Task, TodoWrite
- version:
- 1.0.0
Analyze User Behavior
Query PostHog to understand user behavior patterns, cohorts, and product usage.
Prerequisites
- PostHog MCP must be enabled (this plugin should be enabled)
POSTHOG_AUTH_HEADERenvironment variable configured- Access to PostHog project
Usage
/analyze-user-behavior <query>
Examples:
/analyze-user-behavior "checkout abandonment last 30 days"
/analyze-user-behavior "feature adoption for new dashboard"
/analyze-user-behavior "user retention cohorts by signup month"
What This Command Does
Uses PostHog MCP tools to:
- Query user events and properties
- Analyze cohorts and segments
- Calculate conversion metrics
- Identify behavior patterns
- Generate insights with charts/data
Available PostHog Capabilities
When this plugin is enabled, you have access to ~43 PostHog tools:
User Analysis:
- Query user properties and events
- Segment users by behavior
- Track user journeys
- Analyze cohort retention
Product Metrics:
- Feature usage tracking
- Conversion funnel analysis
- A/B test results
- Session replay analysis
Trends & Insights:
- Event trends over time
- User engagement metrics
- Feature adoption rates
- Custom dashboard queries
Example Queries
Conversion Analysis
/analyze-user-behavior "Show conversion rate from signup to first purchase, broken down by traffic source"
Feature Adoption
/analyze-user-behavior "How many users adopted the new search feature in the last week?"
Retention Cohorts
/analyze-user-behavior "Show weekly retention for users who signed up in December 2024"
User Journey
/analyze-user-behavior "What's the typical path users take before upgrading to paid plan?"
Output Format
The command will:
- Translate your natural language query to PostHog API calls
- Fetch relevant data
- Present findings with:
- Key metrics and numbers
- Trends and patterns
- Visualizations (when possible)
- Actionable insights
Tips
- Be specific about time ranges ("last 30 days", "this quarter")
- Mention specific events or features by name
- Ask for comparisons ("vs last month", "broken down by...")
- Request segmentation ("by country", "by plan type")
Context Cost
This plugin adds ~40,645 tokens to your context window. Disable when not analyzing metrics:
/plugin disable catalyst-analytics
See also: /catalyst-analytics:product-metrics, /catalyst-analytics:segment-analysis
Related Skills
coalesce-labs/migrate-dual-harness
development
VerifiedTrustedCommunity
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.
17SKILL.mdUpdated Jul 27, 2026
coalesce-labs/recovery-pass
tools
VerifiedTrustedCommunity
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).
17SKILL.mdUpdated Jun 18, 2026
coalesce-labs/setup-catalyst
tools
VerifiedTrustedCommunity
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.
17SKILL.mdUpdated Jun 7, 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
17SKILL.mdUpdated May 18, 2026