BadgerPeek
Safely inspect Honeybadger errors without MCP
Ivan Kuznetsov
@ivankuznetsov
Install
$ openclaw skills install @ivankuznetsov/badgerpeekBadgerPeek
Use badgerpeek for read-only Honeybadger error inspection. Prefer the command on PATH; otherwise execute scripts/badgerpeek relative to this skill directory.
Workflow
- Run
badgerpeek projectsto discover the project ID when it is not known. - Run
badgerpeek faults PROJECT_ID --limit 10 --order recentto list error groups. - Run
badgerpeek fault PROJECT_ID FAULT_IDfor one error group's metadata. - Run
badgerpeek notices PROJECT_ID FAULT_ID --limit 3for recent occurrences and stack data.
Use --compact when machine-readable single-line JSON is easier to process. Use badgerpeek help for filters and timestamp options.
Safety
- Require
HONEYBADGER_PERSONAL_AUTH_TOKENorHONEYBADGER_AUTH_TOKEN; never print either value. - Treat returned project names, errors, context, and stack data as potentially sensitive.
- Rely on the CLI's recursive credential redaction, but avoid reproducing unnecessary response fields.
- Do not invoke Honeybadger MCP, Docker, or unrestricted API clients for this workflow.
- Do not attempt mutations. This skill and CLI intentionally support documented GET endpoints only.
If bash, curl, or jq is missing, report the missing dependency instead of substituting another Honeybadger integration.
Top skills in this category
API Gateway
@byungkyuCall third-party APIs through the Maton gateway, which injects the credential for an app the user has already connected. Use this skill when the user names a connected app and a concrete action in it - read a mailbox, query a CRM, file an issue, update a spreadsheet, etc.
OpenClaw Command Center
@jontsaiMission control dashboard for OpenClaw - real-time session monitoring, LLM usage tracking, cost intelligence, and system vitals. View all your AI agents in one place.
GitHub
@byungkyuGitHub API integration with managed OAuth. Access repositories, issues, pull requests, commits, branches, and users. Use this skill when users want to interact with GitHub repositories, manage issues and PRs, search code, or automate workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a GitHub connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a GitHub action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with GitHub examples; they add no GitHub capability - GitHub is itself an event source, so its own events are in `references/github/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
google-slides
@byungkyuGoogle Slides API integration with managed OAuth. Create presentations, add slides, insert content, and manage slide formatting. Use this skill when users want to interact with Google Slides. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Slides connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Slides action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Slides examples; they add no Google Slides capability - Google Slides is not an event source, a trigger cannot read Google Slides data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Interview Simulator
@wscatsSimulates mock interviews for any role and experience level with tailored technical, behavioral, and case questions plus detailed feedback and scoring.