Menü
Investigate and triage a Sentry error issue
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use swarm scripts for bulk SDK calls, repetitive fan-out, and context-efficient data processing.
Fetch a file attached to your current task in ONE call. Use whenever a task carries an attachment (an image, PDF, or other file the requester uploaded) and you need its bytes on disk — the dispatch prompt lists attachments with a ready-to-run curl command, but if you're improvising (resumed session, follow-up task, or the recipe scrolled out of context) use this skill instead of reaching for the `agent-fs` CLI directly.
Guide for running local E2E tests with API server, Docker lead/worker containers, task creation, log verification, UI dashboard, and cleanup
Canonical AgentMail send-message API reference for swarm agents. Pins the base URL, required field names, text-only rendering workaround, BCC policy, and ready-to-copy curl / swarm-script examples so agents do not rediscover the API surface at runtime.
How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and resolve contacts to swarm users. Canonical reference for ANY Kapso interaction beyond the thin `send-whatsapp-message` / `reply-whatsapp-message` MCP tools — for templates, media, reactions, typing, mark-as-read, signature verify, contact resolution, conversation history, drop to the REST recipes here. Use whenever a task references a WhatsApp message routed through Kapso, or when a workflow needs to reply on WhatsApp.
Per-app playbook for driving Gmail through Composio (toolkit slug `gmail`). Verified GMAIL_* tool slugs and argument shapes for reading, searching, sending, drafts, labels, and threads. Use alongside the `composio` hub skill whenever a task reads or sends Gmail for a connected user. Covers the metadata-first reads, the GMAIL_SEND_EMAIL HTML flag, and reply-to-thread.
| name | investigate-sentry-issue |
| description | Investigate and triage a Sentry error issue |
Investigate a Sentry issue to understand the error, gather context, and prepare for fixing or triaging.
SENTRY_AUTH_TOKEN and SENTRY_ORG must be set. Verify with sentry-cli info.
sentry-issue-url-or-id: A Sentry issue URL or just the issue ID (e.g., 123456)If given a URL (https://sentry.io/organizations/{org}/issues/{issue_id}/), extract the issue ID.
sentry-cli issues list --id <issue-id>
Use https://sentry.io/api/0/organizations/${SENTRY_ORG}/issues/<issue-id>/ for metadata (first/last seen, event count, user impact, status).
Use the recommended event endpoint: .../issues/<issue-id>/events/recommended/
Key jq paths for the response:
.entries[] | select(.type == "exception") — exception with stacktrace.entries[] | select(.type == "exception") | .data.values[].stacktrace.frames — stack frames.entries[] | select(.type == "breadcrumbs") — actions leading to the error.tags — environment, browser, OS info.context — custom context datasentry-cli issues resolve <issue-id> # Resolve
sentry-cli issues mute <issue-id> # Mute
sentry-cli issues unresolve <issue-id> # Unresolve
Use these filters with sentry-cli issues list --query:
| Filter | Example | Description |
|---|---|---|
is: | is:unresolved | Issue status |
lastSeen: | lastSeen:-2d | Seen within time range |
message: | message:undefined | Match error message |
issue.category: | issue.category:error | Error category |