How do I install the Bugsnag CLI skill?

Run npx skillmds@latest add yoanbernabeu/bugsnag-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bugsnag CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bugsnag CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bugsnag CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bugsnag CLI?

yoanbernabeu (@yoanbernabeu) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bugsnag CLI by yoanbernabeu — Agent Skill

Name: Bugsnag CLI
Author: yoanbernabeu

Bugsnag CLI

Use the bugsnag-cli command-line tool to interact with the Bugsnag Data Access API. Use this skill whenever the user mentions Bugsnag errors, wants to investigate production bugs tracked in Bugsnag, check project health or stability metrics, list organizations/projects/releases, configure their Bugsnag CLI access, or needs help with any bugsnag-cli command syntax. Also triggers when the user asks about error trends, crash-free rates, or wants to comment on Bugsnag errors from the terminal.

yoanbernabeu a9c3baa 5 files · 16.9 KB Updated Sep 17, 2026

File contents

bugsnag-cli

A fast, agent-friendly CLI for the Bugsnag Data Access API. Outputs JSON by default (ideal for agents and scripts), supports --format table for human reading.

When to read which reference

Pick the reference file that matches the user's intent:

User intent	Reference file
Install, configure, authenticate, first steps	`references/quickstart.md`
Investigate a specific error (details, events, trends, comments)	`references/investigate-error.md`
Assess overall project health (error counts, trends, stability, releases)	`references/project-health.md`
Look up exact command syntax, flags, or options	`references/command-reference.md`

If unsure, start with references/command-reference.md — it covers every command.

Quick overview

Authentication

Three methods (checked in this priority order):

Flag: --api-token TOKEN or -t TOKEN
Env var: BUGSNAG_API_TOKEN
Config file: ~/.bugsnag-cli.yaml (created via bugsnag configure --api-token TOKEN)

Available commands

Command	Description
`bugsnag configure`	Save auth token and defaults to config file
`bugsnag organizations list`	List organizations
`bugsnag projects list/get`	List or get project details
`bugsnag errors list/get`	List errors with filters, or get error details
`bugsnag events list/get`	List event occurrences, or get event details
`bugsnag trends project/error`	View error trends over time
`bugsnag collaborators list`	List organization collaborators
`bugsnag comments list/create`	List or add comments on errors
`bugsnag releases list`	List project releases
`bugsnag stability trend`	View crash-free session rate
`bugsnag version`	Print CLI version

Global flags

Flag	Short	Default	Description
`--api-token`	`-t`	—	Bugsnag API token
`--format`	`-f`	`json`	Output format: json or table
`--per-page`	—	`30`	Results per page (1-100)
`--all-pages`	`-a`	`false`	Fetch all pages
`--base-url`	—	`https://api.bugsnag.com`	API base URL
`--config`	—	`~/.bugsnag-cli.yaml`	Config file path

Output format

JSON lists return: {"data": [...], "total_count": N, "has_more": bool}

Single items return the object directly. Errors go to stderr as {"error": "..."}.

Exit codes

Code	Meaning
0	Success
1	General error
2	Configuration error (missing token/flag)
3	API error (401, 403, 404, 500)
4	Network error (timeout, DNS, connection refused)

Common workflows

First setup:

bugsnag configure --api-token TOKEN
bugsnag organizations list
bugsnag projects list --org-id ORG_ID

Investigate an error: read references/investigate-error.md

Project health check: read references/project-health.md

Need exact flag syntax: read references/command-reference.md

---name: bugsnag-clidescription: Use the bugsnag-cli command-line tool to interact with the Bugsnag Data Access API. Use this skill whenever the user mentions Bugsnag errors, wants to investigate production bugs tracked in Bugsnag, check project health or stability metrics, list organizations/projects/releases, configure their Bugsnag CLI access, or needs help with any bugsnag-cli command syntax. Also triggers when the user asks about error trends, crash-free rates, or wants to comment on Bugsnag errors from the terminal.---# bugsnag-cliA fast, agent-friendly CLI for the Bugsnag Data Access API. Outputs JSON by default (ideal for agents and scripts), supports `--format table` for human reading.## When to read which referencePick the reference file that matches the user's intent:| User intent | Reference file ||-------------|---------------|| Install, configure, authenticate, first steps | `references/quickstart.md` || Investigate a specific error (details, events, trends, comments) | `references/investigate-error.md` || Assess overall project health (error counts, trends, stability, releases) | `references/project-health.md` || Look up exact command syntax, flags, or options | `references/command-reference.md` |If unsure, start with `references/command-reference.md` — it covers every command.## Quick overview### AuthenticationThree methods (checked in this priority order):1. Flag: `--api-token TOKEN` or `-t TOKEN`2. Env var: `BUGSNAG_API_TOKEN`3. Config file: `~/.bugsnag-cli.yaml` (created via `bugsnag configure --api-token TOKEN`)### Available commands| Command | Description ||---------|-------------|| `bugsnag configure` | Save auth token and defaults to config file || `bugsnag organizations list` | List organizations || `bugsnag projects list/get` | List or get project details || `bugsnag errors list/get` | List errors with filters, or get error details || `bugsnag events list/get` | List event occurrences, or get event details || `bugsnag trends project/error` | View error trends over time || `bugsnag collaborators list` | List organization collaborators || `bugsnag comments list/create` | List or add comments on errors || `bugsnag releases list` | List project releases || `bugsnag stability trend` | View crash-free session rate || `bugsnag version` | Print CLI version |### Global flags| Flag | Short | Default | Description ||------|-------|---------|-------------|| `--api-token` | `-t` | — | Bugsnag API token || `--format` | `-f` | `json` | Output format: json or table || `--per-page` | — | `30` | Results per page (1-100) || `--all-pages` | `-a` | `false` | Fetch all pages || `--base-url` | — | `https://api.bugsnag.com` | API base URL || `--config` | — | `~/.bugsnag-cli.yaml` | Config file path |### Output formatJSON lists return: `{"data": [...], "total_count": N, "has_more": bool}`Single items return the object directly. Errors go to stderr as `{"error": "..."}`.### Exit codes| Code | Meaning ||------|---------|| 0 | Success || 1 | General error || 2 | Configuration error (missing token/flag) || 3 | API error (401, 403, 404, 500) || 4 | Network error (timeout, DNS, connection refused) |### Common workflows**First setup:**```bashbugsnag configure --api-token TOKENbugsnag organizations listbugsnag projects list --org-id ORG_ID```**Investigate an error:** read `references/investigate-error.md`**Project health check:** read `references/project-health.md`**Need exact flag syntax:** read `references/command-reference.md`

Frequently asked questions