CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sentry-fix-issues

Find and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry. Methodically analyzes stack traces, breadcrumbs, traces, and context to identify root causes.

Quality

89%

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

88%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.

The body is a highly actionable, well-sequenced workflow with concrete MCP tool usage, security handling for untrusted data, and explicit validation checkpoints at every risky step. Its only deductions are minor: some repetition of the untrusted-input rule across sections and a monolithic single-file structure slightly above ideal length for an overview.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no explanations of concepts Claude already knows, but the untrusted-input rule is repeated in three places (Security Constraints, Phase 2 reminder, Phase 4 "Before proceeding") and "Invoke This Skill When" duplicates the frontmatter triggers. Minor trimming would reach lean efficiency.

4 / 5

Actionability

Gives copy-paste-ready MCP invocations with exact parameters (e.g., `search_issues` with `naturalLanguageQuery: "unresolved issues"`, `get_issue_details` with `issueId: "PROJECT-123"`), concrete commands (`git log`, `git blame`), and a filled-in report template. The Quick Reference's common error patterns cover the frequent cases.

5 / 5

Workflow Clarity

Seven clearly sequenced phases with explicit validation checkpoints: user confirmation before proceeding (Phase 1), cross-referencing event data against the repo before Phase 4, a pre-fix checklist, and a Phase 6 verification audit with self-challenge. Validation is present throughout, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

A single well-organized file with clear sections, tables, and a Quick Reference; no nested or buried references. At ~130 lines it exceeds the under-50-line simple-skill exception, and the Quick Reference tool/pattern catalog could arguably live in a separate reference file, leaving minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

87%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 description in third person voice that clearly states capability and explicit usage triggers with natural phrasing and Sentry-specific distinctiveness. The only weaknesses are minor: the fixing side of the workflow is described less concretely than the analysis side, and a few natural trigger synonyms (e.g., "crashes") are absent.

DimensionReasoningScore

Specificity

"Find and fix issues from Sentry using MCP" and "Methodically analyzes stack traces, breadcrumbs, traces, and context to identify root causes" list several concrete actions. Falls short of 5 because "fix issues" stays generic and the fix-side activities (verification, reporting) aren't enumerated.

4 / 5

Completeness

Explicitly answers both: what ("Find and fix issues from Sentry using MCP... analyzes stack traces, breadcrumbs, traces, and context to identify root causes") and when ("Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases users would say are well covered — "fix Sentry errors", "debug production issues", "investigate exceptions", "resolve bugs reported in Sentry" — with synonym variety (errors/issues/bugs/exceptions). A few common terms like "crashes" or "error monitoring" are missing, keeping it below comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Sentry" is named in both the capability statement and every trigger phrase, creating a clear niche with minimal conflict risk against generic debugging or error-monitoring skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

.claude/cloud-profile/skills/sentry-fix-issues/SKILL.md

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.