Catalogskills.sh · bitdriftlabs

bd-cuj

Set up Critical User Journey (CUJ) monitoring in bitdrift. Deploys a complete observability stack: path discovery (sankey), conversion funnel, completion rate SLO, key step duration alerting, session capture, and a two-tab dashboard. Trigger when a user wants to monitor a journey end-to-end, track conversion and drop-off, measure step duration, or set up SLOs on a business-critical flow such as checkout, onboarding, login, or search.

Review advisedVerified hub290 installs

Import into your workspace View at source

Savant verdict: Review advised

Security analysis or source-hub review identified patterns requiring attention.

Live evaluation

Not evaluated yet. Workspaces can request a live evaluation.

Security assessment

Scan pending.

Structure

The source hub's security checks flagged this skillSnyk: warn (Risk: MEDIUM · 1 issue)

SKILL.md

---
name: bd-cuj
description: "Set up Critical User Journey (CUJ) monitoring in bitdrift. Deploys a complete observability stack: path discovery (sankey), conversion funnel, completion rate SLO, key step duration alerting, session capture, and a two-tab dashboard. Trigger when a user wants to monitor a journey end-to-end, track conversion and drop-off, measure step duration, or set up SLOs on a business-critical flow such as checkout, onboarding, login, or search."
license: PolyForm Shield License 1.0.0
---

# Critical User Journey (CUJ) Monitoring

> For CLI usage, workflow creation, and alert syntax, see the `bd-cli` skill.
> For SDK integration and instrumentation, use the `bd-instrumentation` skill if available; it ships separately in the `bitdrift-sdk` plugin.

This skill is a guided, interactive setup. Work through phases in order, loading reference files on demand as each phase begins.

## Core rules

- **Never guess field names, event names, or matcher values.** The user supplies all identifiers in Phase 0. Do not infer them from code or prior context.
- **Do not deploy anything until the user has approved the Phase 0 discovery summary.**
- **Gate between every phase.** After each phase: report the created resource ID(s) (workflow/alert/dashboard) and link(s) where applicable, then ask "Ready to continue to [next phase]?" before loading the next reference file.

## Phases

| # | Phase | Output | Reference |
|---|---|---|---|
| 0 | Discovery | Approved event map, key step, scope, app IDs, network paths | [references/discovery.md](references/discovery.md) |
| 1 | Sankey | Path discovery workflow | [references/sankey.md](references/sankey.md) |
| 2 | Funnel | Funnel workflow (funnel + key step timing + slow session capture) + separate completion rate workflow (for SLOs) | [references/funnel.md](references/funnel.md) |
| 3 | Network | Network RED workflow | [references/network.md](references/network.md) |
| 4 | Alerts | Completion rate MWMBR SLO + key step p95 alert | [references/alerts.md](references/alerts.md) |
| 5 | Dashboard | Two-tab dashboard: Journey + Network | [references/dashboard.md](references/dashboard.md) |

Start with [references/discovery.md](references/discovery.md).