CtrlK
BlogDocsLog inGet started
Tessl Logo

fix-sentry-issues

Use Sentry MCP to discover, triage, and fix production issues with root-cause analysis. Use when asked to fix Sentry issues, triage production errors, investigate error spikes, or clean up Sentry noise. Requires Sentry MCP server. Triggers on "fix sentry", "triage errors", "production bugs", "sentry issues".

76

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, actionable workflow skill: concrete tool calls and commands, a clearly sequenced three-phase process with real validation checkpoints, and a well-organized self-contained structure. The only minor weakness is slight rhetorical repetition in the Philosophy/Anti-patterns sections.

DimensionReasoningScore

Conciseness

Lean and directive with no re-explanation of concepts Claude already knows, but the Philosophy and Anti-patterns sections contain minor deliberate repetition (e.g. restating the "fallback is not a fix" point) that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout — concrete Sentry MCP tool calls, a literal `axiom query` command, a `git checkout -b fix/<descriptive-name>` recipe, and a triage-table template that covers the common cases.

5 / 5

Workflow Clarity

Three clearly sequenced phases with an ordered 6-step investigation and explicit validation checkpoints (tests fail before fix and pass after, lint, resolve in Sentry only after merge), including feedback loops for error recovery.

5 / 5

Progressive Disclosure

Self-contained with no bundle files and no need for them; well-organized into Philosophy, Anti-patterns, and three Phase sections that are easy to navigate without nested references.

5 / 5

Total

19

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that crisply states capabilities, gives explicit use-when guidance, and lists concrete natural-language triggers, with a clear Sentry-specific niche and minimal conflict risk.

DimensionReasoningScore

Specificity

Names the Sentry domain and several concrete actions ("discover, triage, and fix production issues with root-cause analysis") but stops short of the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

Explicitly answers both what ("discover, triage, and fix production issues with root-cause analysis") and when ("Use when asked to fix Sentry issues, triage production errors..."), plus an explicit "Triggers on" clause and a dependency note.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say — "fix sentry", "triage errors", "production bugs", "sentry issues", "investigate error spikes", "clean up Sentry noise" — covering synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

A clear Sentry-specific niche with distinct, branded triggers; minimal risk of firing for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
brianlovin/agent-config
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.