Router for bitdrift Capture skills — start here for setup, routing, troubleshooting, and diagnostics.
Check the invocation arguments before displaying any content:
| Argument | Action |
|---|---|
help, --help, -h | Show only the Help section, then stop |
diag, diagnostics | Run only the Diagnostics section, then stop |
| (none or unrecognized) | Show the Overview section |
Usage: /bd [subcommand]
| Subcommand | Description |
|---|---|
| (none) | Show skill overview, setup info, and routing table |
help | Show this help message |
diag | Run diagnostics and collect system info for bug reports |
Related skills:
| Skill | Description |
|---|---|
/bd-setup | CLI install, authentication, account setup |
/bd-instrumentation | SDK setup, logging, telemetry, network monitoring, crash reporting |
/bd-platform | Investigate app health, diagnose crashes, triage errors, what happened recently; workflows, charts, sessions, crash reports/issues, bd tail, portal/CLI ops |
/bd-migration | Migrate from another tool to bitdrift — Sentry supported (iOS, Android, React Native); more coming |
/bd-migration-sentry | Vendor-specific Sentry migration guide |
bd auth is safe to call anytime — it checks for existing valid credentials and skips login if already authenticated. If any bd command returns an authentication error, run bd auth or bd auth --force to re-authenticate. If the error suggests an API key issue, print the error, but you can also ask if they'd like to create another one (requires admin).
| Intent | Skill |
|---|---|
| Complete post-install setup (CLI, auth) | $bd-setup |
| Add logging, telemetry, SDK setup, network monitoring, crash reporting | $bd-instrumentation |
| Investigate app health, diagnose crashes, triage errors, what happened recently | $bd-platform |
| Workflows, charts, sessions, crash reports/issues, bd tail, portal/CLI ops | $bd-platform |
| Migrate from another observability tool to bitdrift | $bd-migration |
| Migrate specifically from Sentry to bitdrift | $bd-migration-sentry |
The developer needs:
bd CLI: brew tap bitdriftlabs/bd && brew install bdbd auth (browser login) or an API key (bd key create api). Sign up at https://bitdrift.ai/signup if new.For full guided setup (including skill install), follow https://bitdrift.ai/agent-setup
Already installed skills? Run /bd-setup to complete CLI install and auth.
If commands fail or behave unexpectedly:
brew outdated bd
npx skills check
brew upgrade bdnpx skills updatebd <command> --help
Collect and print this for the developer to paste when reporting issues:
echo "--- bd diagnostics ---"
echo "Agent: <your agent name>"
echo "OS: $(sw_vers -productName 2>/dev/null || uname -s) $(sw_vers -productVersion 2>/dev/null || uname -r) $(uname -m)"
brew info bd 2>&1 || echo "bd: not installed"
bd workflow list --limit 1 -o json >/dev/null && echo "bd auth: ok" || echo "bd auth: not authenticated"
echo "Node: $(node --version 2>&1 || echo 'not installed')"
echo "--- installed skills ---"
cat skills-lock.json 2>/dev/null || echo "no lock file found"
npx skills check 2>&1 || echo "skills check failed"
echo "--- end ---"
Format the output and tell the developer: "Paste this when reporting issues to bitdrift."