OpenParable
Skip to content
← Back to skills

Sentry

DevOps & Security
sentry

Sentry is an Agent Skill for devops & security published in the Expensify/App repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Analyze Sentry issues, spans, crashes, and performance metrics. Use when user requests check in Sentry, asks about performance metrics and spans or asks about crash rates.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Expensify/App/blob/HEAD/.claude/skills/sentry/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sentry, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Sentry

When to Use This Skill

Use Sentry skill when:

  • User requests any data from Sentry
  • User asks about performance metrics or span summary
  • User want to compare metrics between any date ranges
  • User asks about latest production crashes and issues
  • User want to investigate profiles or traces from production sessions

Sentry MCP

The Sentry MCP server is configured in .mcp.json and gives Claude Code direct access to Sentry.

Prerequisites

Setup (one-time per engineer): On first use, Claude Code will open a browser OAuth login to Sentry. Sign in and authorize — no manual token setup required.

Available MCP Tools

Use these tools for data analysis:

ToolPurpose
mcp__sentry__find_releasesFind release versions for scoping queries
mcp__sentry__search_issuesSearch for errors/crashes by query, project, date range
mcp__sentry__search_eventsQuery raw events/spans (performance data, durations)
mcp__sentry__search_issue_eventsGet individual events for a known issue ID
mcp__sentry__get_issue_tag_valuesInspect tag distributions (e.g. device, version) on an issue
mcp__sentry__get_sentry_resourceFetch a specific Sentry resource by URL/ID

Do not use mcp__sentry__analyze_issue_with_seer — AI analysis is out of scope for this skill.

Always use:

  • org slug: expensify
  • project slug: app

Example uses

  • "Search Sentry for crashes in the last 24h related to expense creation"
  • "Get details on Sentry issue APP-123"
  • "Compare P90 of ManualAppStartup durations between last two weeks"