Investigate Sentry issues, project activity, and organization-wide error trends over time. For errors captured inside the app, inspect grouped issues, their occurrences and context, then resolve, ignore, or reopen them during triage.
Track external Sentry errors and issues, and route first-party captured errors to Agent-Native Analytics. Use this skill when the user asks about errors, exceptions, error trends, or application health.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
https://sentry.io/api/0SENTRY_ORG_SLUG or pass orgSlug to the sentry action when a user needs a specific Sentry organization.Authorization: Bearer $SENTRY_SERVER_TOKEN (internal integration token, NOT user auth token or DSN)SENTRY_SERVER_TOKEN (falls back to SENTRY_AUTH_TOKEN)alerts:read, event:read, org:read, project:distribution, project:read, team:readserver/lib/sentry.ts| Function | Description |
|---|---|
listProjects() | List all projects in the org |
listIssues(projectSlug?, query?, statsPeriod?) | List issues (project-scoped or org-wide) |
getIssueEvents(issueId) | Events for a specific issue |
getOrganizationStats(statsPeriod?, category?) | Org-level error stats over time |
Use sentry for all agent-facing Sentry work. Do not call /api/sentry/*
directly from the agent.
| Mode | Args | Description |
|---|---|---|
organizations | List organizations visible to the token | |
issues | statsPeriod, project, query, orgSlug | Frequent issues, sorted by frequency |
projects | orgSlug | List projects |
issue-events | issueId, orgSlug | Events for a specific issue |
stats | statsPeriod, category, orgSlug | Org-level stats |
| Route | Description |
|---|---|
GET /api/sentry/projects | List projects |
GET /api/sentry/issues | List issues |
GET /api/sentry/issue-events | Events for an issue |
GET /api/sentry/stats | Org error stats |
/adhoc/sentry — Sentry Error Health dashboardAgent-Native Analytics has its own Sentry-style error store, separate from the
external Sentry connection. Browser configureTracking() and server
captureError() can both emit $exception events when their Analytics keys are
configured; Analytics groups them under Monitoring -> Errors without an
external Sentry credential.
Use these authenticated actions for first-party issues:
| Action | Purpose |
|---|---|
list-error-issues | Find grouped captured issues, filtered by status or search. |
get-error-issue | Read occurrences, stacks, tags, breadcrumbs, and replay links. |
resolve-error-issue | Resolve, ignore, or reopen an issue after triage. |
Use query-agent-native-analytics only for bounded analytics_events or
$ai_generation correlation; it does not expose the error_issues or
error_events tables.
getOrganizationStats uses stats_v2 endpoint with field=sum(quantity), groupBy=outcome, default category errororgSlug explicitly in the action call.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generate, refine, export, and place brand images or videos from an Assets library into another app. The skill covers choosing a library, handling image batches and video runs, and updating selected assets after feedback.
Prepare a customer account health, renewal, or contract usage readout. Verify the account identity, use approved metric definitions, compare contracted capacity with actual usage, and trace findings to sources, time windows, and known gaps.
Create focused app actions that agents can call as tools and frontend code can use through client hooks. Use them to add provider integrations or fetch UI data, with validated inputs and structured results.
Use this checklist when adding a feature or integration to an agent-native app. It covers the user interface, agent-callable actions, instructions, and app-state sync so both the user and agent can work with the capability consistently.
Investigate complex questions by combining data from multiple sources, then summarize patterns, metrics, and evidence in a clear report. Save requested analyses as dashboards with instructions for future refreshes.
Use the Analytics admin surfaces to inspect and change workspace feature flags, review dashboard ownership and usage activity, or browse and edit databases connected from other agent-native apps. The skill guides administrators to the relevant view and actions.