How do I install the Sentry skill?

Run npx skillmds@latest add tomevault-io/sentry in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sentry safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sentry?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sentry free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sentry?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sentry by tomevault-io — Agent Skill

Name: Sentry
Author: tomevault-io

Sentry

Sentry issue triage and investigation with automatic cross-linking. Handles issue investigation, AI analysis via Seer, and integration with Linear for tracking fixes. Use when triaging Sentry errors, investigating sentry.io URLs, or creating Linear issues from Sentry. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Sentry Issue Management

Triage, investigate, and resolve Sentry issues with enforced cross-linking to Linear and GitHub.

Organization: intexuraos-dev-pbuchman

Usage

/sentry                           # NON-INTERACTIVE: Triage unresolved issues
/sentry <sentry-url>              # Investigate specific issue
/sentry INT-123                   # Find Sentry issues linked to Linear issue
/sentry triage --limit 5          # Batch triage with limit
/sentry analyze <sentry-url>      # AI-powered root cause analysis via Seer

Core Mandates

Fail Fast: If Sentry, Linear, GitHub CLI, or GCloud are unavailable, STOP immediately
No Guessing: Surface-level fixes without identifying the source of corruption are FORBIDDEN
Cross-Linking: Every Sentry issue MUST be linked to a Linear issue and GitHub PR
Documentation in PR: Reasoning belongs in PR descriptions, not code comments
CI Gate: pnpm run ci:tracked MUST pass before PR creation

Invocation Detection

The skill automatically detects intent from input:

Input Pattern	Type	Workflow
`/sentry` (no args)	Batch Triage	triage-batch.md
`/sentry <sentry-url>`	Single Issue	triage-issue.md
`/sentry analyze <url>`	Seer Analysis	analyze-with-seer.md
`/sentry linear <sentry-url>`	Create Linear	create-linear-issue.md
`/sentry triage --limit N`	Limited Batch	triage-batch.md

Tool Verification (Fail Fast)

Before ANY operation, verify all required tools:

Tool	Verification Command	Purpose
Sentry MCP	`mcp__sentry__whoami`	Issue management
Linear MCP	`mcp__linear__list_teams`	Issue tracking
GitHub CLI	`gh auth status`	PR creation
GCloud	Service account verification	Firestore access

GCloud Verification

Service account key location: ~/.config/gcloud/sa-key.json

Check if credentials file exists
If gcloud auth list shows no active account, activate service account
Verify authentication

You are NEVER "unauthenticated" if the service account key file exists.

Failure Handling

If ANY required tool is unavailable, ABORT immediately:

ERROR: /sentry cannot proceed - <tool-name> unavailable

Required for: <purpose>
Fix: <fix-command>

Aborting.

Configured Projects

Issues are fetched from these Sentry projects:

intexuraos-development (backend services)
intexuraos-web-development (web app)

Cross-Linking Protocol (Critical)

Every Sentry issue must be traceable across all systems:

Direction	Method
Sentry → Linear	Comment on Sentry with Linear issue link
Linear → Sentry	`[sentry] <title>` naming + link in description
Linear → GitHub	PR title contains `INT-XXX`
GitHub → Linear	`Fixes INT-XXX` in PR body
GitHub → Sentry	Sentry link in PR description

References

Workflows: workflows/
Templates: templates/
Reference: reference/

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: sentrydescription: Sentry issue triage and investigation with automatic cross-linking. Handles issue investigation, AI analysis via Seer, and integration with Linear for tracking fixes. Use when triaging Sentry errors, investigating sentry.io URLs, or creating Linear issues from Sentry. Use when this capability is needed.---# Sentry Issue ManagementTriage, investigate, and resolve Sentry issues with enforced cross-linking to Linear and GitHub.**Organization:** `intexuraos-dev-pbuchman`## Usage```/sentry # NON-INTERACTIVE: Triage unresolved issues/sentry <sentry-url> # Investigate specific issue/sentry INT-123 # Find Sentry issues linked to Linear issue/sentry triage --limit 5 # Batch triage with limit/sentry analyze <sentry-url> # AI-powered root cause analysis via Seer```## Core Mandates1. **Fail Fast**: If Sentry, Linear, GitHub CLI, or GCloud are unavailable, STOP immediately2. **No Guessing**: Surface-level fixes without identifying the _source_ of corruption are FORBIDDEN3. **Cross-Linking**: Every Sentry issue MUST be linked to a Linear issue and GitHub PR4. **Documentation in PR**: Reasoning belongs in PR descriptions, not code comments5. **CI Gate**: `pnpm run ci:tracked` MUST pass before PR creation## Invocation DetectionThe skill automatically detects intent from input:| Input Pattern | Type | Workflow || ----------------------------- | ------------- | ---------------------------------------------------------- || `/sentry` (no args) | Batch Triage | [triage-batch.md](workflows/triage-batch.md) || `/sentry <sentry-url>` | Single Issue | [triage-issue.md](workflows/triage-issue.md) || `/sentry analyze <url>` | Seer Analysis | [analyze-with-seer.md](workflows/analyze-with-seer.md) || `/sentry linear <sentry-url>` | Create Linear | [create-linear-issue.md](workflows/create-linear-issue.md) || `/sentry triage --limit N` | Limited Batch | [triage-batch.md](workflows/triage-batch.md) |## Tool Verification (Fail Fast)Before ANY operation, verify all required tools:| Tool | Verification Command | Purpose || ---------- | ---------------------------- | ---------------- || Sentry MCP | `mcp__sentry__whoami` | Issue management || Linear MCP | `mcp__linear__list_teams` | Issue tracking || GitHub CLI | `gh auth status` | PR creation || GCloud | Service account verification | Firestore access |### GCloud Verification**Service account key location:** `~/.config/gcloud/sa-key.json`1. Check if credentials file exists2. If `gcloud auth list` shows no active account, activate service account3. Verify authentication**You are NEVER "unauthenticated" if the service account key file exists.**### Failure HandlingIf ANY required tool is unavailable, **ABORT immediately**:```ERROR: /sentry cannot proceed - <tool-name> unavailableRequired for: <purpose>Fix: <fix-command>Aborting.```## Configured ProjectsIssues are fetched from these Sentry projects:1. `intexuraos-development` (backend services)2. `intexuraos-web-development` (web app)## Cross-Linking Protocol (Critical)Every Sentry issue must be traceable across all systems:| Direction | Method || --------------- | ----------------------------------------------- || Sentry → Linear | Comment on Sentry with Linear issue link || Linear → Sentry | `[sentry] <title>` naming + link in description || Linear → GitHub | PR title contains `INT-XXX` || GitHub → Linear | `Fixes INT-XXX` in PR body || GitHub → Sentry | Sentry link in PR description |## References- Workflows: [`workflows/`](workflows/)- Templates: [`templates/`](templates/)- Reference: [`reference/`](reference/)---> Converted and distributed by [TomeVault](https://tomevault.io/claim/pbuchman) — claim your Tome and manage your conversions.

Frequently asked questions