Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Security: fix shell injection in ITEM_ID/PROJECT_ID args, fix Python code injection in LIMIT/HOURS params. All inputs now validated and passed via env vars.
What This Skill Does
Connects OpenClaw to Rollbar error tracking. List recent error items, inspect occurrences, resolve or mute issues, and view deployment history via the Rollbar API. Supports both project-level and account-level tokens.
Lets you inspect and act on Rollbar errors without switching to the web dashboard, keeping triage inside your existing agent workflow.
When to use it
- Reviewing new critical errors after a production deployment
- Muting a known flaky error that is flooding the error queue
- Correlating a traffic spike with a specific deployment from the deploy history
- Getting all occurrences of a single error item to gauge its frequency
- Running a daily triage of the top active errors sorted by occurrence count
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: What are the top active errors from the last 24 hours?
- 1Runs `rollbar.sh top --limit 10 --hours 24` to fetch the most frequent active items
- 2Parses the JSON response and extracts item IDs, titles, and occurrence counts
- 3Calls `rollbar.sh item <id>` on the highest-occurrence result to retrieve full details
- 4Returns a ranked summary with error messages, counts, and item IDs for follow-up
A ranked list of the 10 most frequent active Rollbar errors in the past 24 hours, with titles, occurrence counts, and item IDs
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.