sentry
Read-only Sentry API queries for production error inspection and health summaries.
- Requires
SENTRY_AUTH_TOKENwith read-only scopes (project:read,event:read,org:read); supports optional org, project, and base URL environment variables - Core commands: list unresolved issues, fetch issue details, retrieve events for an issue, and inspect individual event data with automatic PII redaction
- Defaults to 24-hour time range, production environment, and 20-result limit (max 50); supports pagination and optional search queries
- Built-in Python script handles API pagination, transient error retries, and deterministic GET-only calls to five core Sentry endpoints
Sentry (Read-only Observability)
Quick start
- If not already authenticated, ask the user to run
sentry auth loginor setSENTRY_AUTH_TOKENas an env var. - The CLI auto-detects org/project from DSNs in
.envfiles, source code, config defaults, and directory names. Only specify<org>/<project>if auto-detection fails or picks the wrong target. - Defaults: time range
24h, environmentproduction, limit 20. - Always use
--jsonwhen processing output programmatically. Use--json --fieldsto select specific fields and reduce output size. - Use
sentry schema <resource>to discover API endpoints quickly.
If the CLI is not installed, give the user these steps:
- Install the Sentry CLI:
curl https://cli.sentry.dev/install -fsS | bash - Authenticate:
sentry auth login - Confirm authentication:
sentry auth status
- Never ask the user to paste the full token in chat. Ask them to set it locally and confirm when ready.
Core tasks (use Sentry CLI)
More from openai/skills
screenshot
Use when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are unavailable and an OS-level capture is needed.
2.7Ksecurity-best-practices
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
2.5Kfigma
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.
2.4Kplaywright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.
2.4Kpdf
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.
2.3Kfigma-implement-design
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.
2.2K