Skip to content
bitdrift Critical User Journey Monitoring

bitdrift Critical User Journey MonitoringSkill

by bitdrift
Released
4 views
PolyForm-Shield-1.0.0
Repository Docs
markdown Development

Summary

Stands up end-to-end monitoring for a business-critical flow — path discovery, conversion funnel, completion SLO, step-duration alerts and a dashboard.

Features

  • Six gated phases from discovery to dashboard
  • Sankey path discovery surfaces the routes users actually take
  • Conversion funnel with step timing
  • RED monitoring on the journey's network calls
  • Completion-rate SLO and step-duration alerting
  • Never invents field, event or matcher names

Install This Skill

Add this skill to your favorite AI agent in a few steps.

Any AI agent

This skill is plain instructions — it works with any assistant that accepts custom instructions or system prompts.

  1. Copy the skill content with the button below.
  2. Paste it into your agent's instruction file or system prompt (for example AGENTS.md, .cursorrules, or a custom instructions field).
  3. Ask the agent to apply the skill whenever the task matches.

Skill Content

Markdown Content

Copy this content and use it with your preferred AI agent

# Critical User Journey (CUJ) Monitoring

> For CLI usage, workflow creation, and alert syntax, see $bd-cli.
> For SDK integration and instrumentation, see $bd-instrumentation.

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).

Usage Instructions

Learn how to use this skill with different AI agents.

Generic Instructions
npx skills add bitdriftlabs/bd-skills

Then: "Set up CUJ monitoring for our checkout flow in bitdrift." Expect it to interview you about event names before it deploys anything.

Description

Checkout, onboarding, login and search are the flows where a regression costs money, and they are also the flows that are hardest to instrument coherently: a funnel here, an alert there, a dashboard nobody updated. This official bitdrift skill deploys the whole stack for one journey as a single, ordered piece of work.

It runs in six gated phases. Discovery establishes the event mappings, the key steps and the scope. A Sankey diagram then makes the real paths through the flow visible — including the ones nobody designed. A conversion funnel with timing follows, then RED (rate, errors, duration) monitoring on the network calls the journey depends on, then SLO and performance alerting, and finally a two-tab dashboard that pulls it together.

The governance is the point. The skill refuses to guess field names, event names or matcher values — every identifier has to come from you — and it will not deploy anything until you have approved the Phase 0 discovery summary, with a gate between each subsequent phase. That is deliberately slower than a one-shot generator, and it is what stops you ending up with a dashboard full of confidently-named metrics that match nothing in your telemetry.

Use it when you need conversion tracking, drop-off analysis, step duration measurement or SLO governance on a flow that matters. It depends on bitdrift's bd-cli skill for workflow and alert syntax and on bd-instrumentation for the SDK side. Note that bd-skills is licensed under PolyForm Shield 1.0.0 — source-available, not open source.

Related Skills

Skill: NVIDIA Warp Gradient Debugging

by NVIDIA

New

Diagnoses wrong gradients in differentiable NVIDIA Warp programs by measuring first — comparing autodiff against finite differences on a shrunk reproduction before proposing any fix.

Development
3 views

Skill: Google Workspace CLI (gws)

by Google Workspace

New

Google's official skill for the gws CLI — drive Gmail, Drive, Calendar, Sheets, Docs, Chat and Admin APIs from an agent, with Model Armor screening.

Development
4 views 1 copies

Skill: Netlify Database

by Netlify

New

Netlify's official skill for zero-config managed Postgres — querying from Functions, Drizzle setup, migrations and per-preview database branches.

Development
3 views

Skill: WordPress Block Development

by WordPress

New

Official WordPress skill for Gutenberg block work: block.json, attributes and serialization, dynamic rendering, and the deprecation path that keeps existing content valid.

Development
3 views 1 copies
Browse all skills →