skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
bitdriftlabs/bd-skills315 installs

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.

How do I install this agent skill?

npx skills add https://github.com/bitdriftlabs/bd-skills --skill bd-cuj
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill facilitates the interactive setup of monitoring journeys in the bitdrift platform using the 'bd' CLI. It generates observability configurations and dashboards based on user input and analysis of session logs. The primary security considerations involve the processing of untrusted external log data and user-supplied identifiers, which are subsequently used in shell command execution and configuration generation.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

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

#PhaseOutputReference
0DiscoveryApproved event map, key step, scope, app IDs, network pathsreferences/discovery.md
1SankeyPath discovery workflowreferences/sankey.md
2FunnelFunnel workflow (funnel + key step timing + slow session capture) + separate completion rate workflow (for SLOs)references/funnel.md
3NetworkNetwork RED workflowreferences/network.md
4AlertsCompletion rate MWMBR SLO + key step p95 alertreferences/alerts.md
5DashboardTwo-tab dashboard: Journey + Networkreferences/dashboard.md

Start with references/discovery.md.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/bitdriftlabs/bd-skills/bd-cuj">View bd-cuj on skillZs</a>