Sentry CLI Skill for OpenClaw

OpenClaw Sentry CLI Skill Overview

The Sentry CLI skill connects OpenClaw to Sentry — the leading error monitoring and performance tracking platform — through the official sentry-cli tool. Once installed, your OpenClaw agent can manage releases, upload source maps, query issues, register deployments, and monitor cron jobs, all through natural language.

Error monitoring is critical for production applications, but managing releases and debugging issues often involves repetitive CLI commands. The OpenClaw Sentry CLI skill streamlines this workflow. Instead of memorizing sentry-cli releases subcommands or manually uploading source maps after every build, simply describe what you need and let the agent handle the rest.

Typical workflow:

1. Ask OpenClaw to create a new release and upload source maps after a build.
2. The agent runs sentry-cli releases new, uploads the maps, and finalizes the release.
3. You get a confirmation summary with the release version and upload status — no manual steps required.

Prerequisites for Sentry CLI Skill

Before installing the Sentry CLI skill, make sure you have:

• OpenClaw installed and running (v1.0+)
• Sentry CLI installed — installation guide
• A Sentry account with access to the projects you want to manage
• A Sentry auth token with appropriate scopes
• clawhub CLI installed for skill management

Verify your setup:

# Check OpenClaw version
openclaw --version

# Check Sentry CLI version
sentry-cli --version

# Verify Sentry authentication
sentry-cli info

Installing Sentry CLI

Choose the method that fits your environment:

# macOS / Linux (auto installer)
curl -sL https://sentry.io/get-cli/ | sh

# macOS (Homebrew)
brew install getsentry/tools/sentry-cli

# NPM
npm install -g @sentry/cli

# Windows (Scoop)
scoop install sentry-cli

How to Install the Sentry CLI Skill

Install the Sentry CLI skill with a single command:

npx clawhub@latest install sentry-cli

To verify the installation:

clawhub list

You should see sentry-cli in the list of installed skills. Preview the skill before installing with clawhub inspect sentry-cli.

Sentry CLI Skill Configuration

The Sentry CLI skill requires an authentication token to interact with the Sentry API. You can use either an organization token (recommended for CI/CD) or a personal auth token.

Creating an Auth Token

1. Go to sentry.io/settings/auth-tokens and create a new token.
2. For release management and source map uploads, grant these scopes:

| Scope | Purpose | |-------|---------| | project:releases | Create and manage releases | | org:read | Read organization data | | project:read | Read project information | | project:write | Upload source maps and debug files |

Environment Setup

# Set Sentry auth token
export SENTRY_AUTH_TOKEN=sntrys_your_token_here

# Set your organization and project (optional, avoids per-command flags)
export SENTRY_ORG=your-org-slug
export SENTRY_PROJECT=your-project-slug

# For self-hosted Sentry instances
export SENTRY_URL=https://sentry.your-company.com/

Important: Never hardcode tokens in configuration files. Use environment variables or a secret manager such as 1Password. Scope tokens to the minimum permissions required — use organization tokens over personal tokens when possible.

Sentry CLI Skill Usage Examples

1. Create a Release After Deploy

You: "Create a new Sentry release for version 2.4.0 with commits from the last release, upload source maps from the ./dist folder, and finalize it."

The agent runs a sequence of commands: sentry-cli releases new 2.4.0, sentry-cli releases set-commits 2.4.0 --auto, sentry-cli sourcemaps upload --release=2.4.0 ./dist, and sentry-cli releases finalize 2.4.0. It confirms each step and reports the total number of files uploaded.

2. Check Recent Errors After a Deploy

You: "Show me the unresolved issues from the last 24 hours on our frontend project, sorted by frequency."

The agent queries Sentry for recent unresolved issues, filters by the specified project and time window, and returns a summary table with issue titles, event counts, affected users, and links to each issue in the Sentry dashboard.

3. Register a Deployment

You: "Register a production deployment for release 2.4.0."

The agent runs sentry-cli releases deploys 2.4.0 new -e production to register the deploy. Sentry then tracks error rates before and after this deployment, enabling deploy health monitoring in the Sentry dashboard.

4. Monitor a Cron Job

You: "Set up Sentry monitoring for our nightly database backup script that runs at 2am."

The agent wraps the backup command with sentry-cli monitors run, configuring it to report check-ins to Sentry Crons. If the job fails or misses its schedule, Sentry sends an alert.

Security & Best Practices

The Sentry CLI skill interacts with your error monitoring data and release pipeline. Follow these guidelines to stay safe:

• Use organization tokens over personal tokens. Organization tokens are scoped to a single org and can be revoked independently without affecting your personal access.
• Grant minimum required scopes. For read-only monitoring, org:read and project:read are sufficient. Only add project:releases and project:write when you need release management.
• Rotate tokens regularly. Set an expiration date on auth tokens and rotate them at least every 90 days.
• Protect sensitive error data. Sentry issues may contain PII, stack traces, or environment details. Be mindful when sharing summaries or logs generated by the agent.
• Use .sentryclirc carefully. If you use a config file, ensure it is in .gitignore and not committed to version control.
• Review release actions before confirming. Always verify the release version and target project before finalizing a release or uploading source maps to avoid publishing to the wrong project.

Troubleshooting Common Errors

"error: API request failed — 401 Unauthorized"

Your auth token is missing, expired, or lacks the required scopes.

1. Verify authentication with sentry-cli info.
2. Check that SENTRY_AUTH_TOKEN is set in your environment.
3. Confirm the token has the necessary scopes at sentry.io/settings/auth-tokens.

# Quick authentication check
sentry-cli info

"error: Could not find organization"

The organization slug does not match your Sentry account, or the token does not have access to that organization.

1. Verify the org slug with sentry-cli organizations list.
2. Check that SENTRY_ORG matches an organization your token can access.
3. For self-hosted instances, ensure SENTRY_URL points to the correct server.

"error: No source maps found in the specified path"

The source map files are missing from the upload directory, or the path is incorrect.

1. Confirm the build output directory contains .map files.
2. Check that your build tool is configured to generate source maps.
3. Use an absolute path or verify the relative path from your current working directory.

# List files in the build directory to verify
ls -la ./dist/*.map