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

94%

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 content is a strongly actionable, well-sequenced workflow with explicit validation gates and security handling for untrusted Sentry data. Its only weaknesses are mild redundancy in restating security constraints and no use of progressive disclosure to move reference material out of the main file.

Suggestions

Consolidate the untrusted-input guidance: state it once in Security Constraints and reference it briefly (e.g., "per Security Constraints") in Phases 2 and 4 instead of restating the full rule three times.

Move the Quick Reference tool list and Common Patterns section into a references/ file (e.g., references/tools.md), keeping SKILL.md as a lean workflow overview with a clearly signaled pointer.

The "Invoke This Skill When" section duplicates the frontmatter description; since the skill is disable-model-invocation: true, consider trimming it to reduce token cost.

DimensionReasoningScore

Conciseness

The body is dense and efficient — tool/parameter tables, checklists, and a report template with no padding about concepts Claude already knows — but the untrusted-input security rule is restated three times (Security Constraints table, Phase 2 reminder, Phase 4 cross-reference paragraph), which is trimmable redundancy keeping it just below anchor 5.

4 / 5

Actionability

Guidance is fully executable: copy-paste-ready MCP calls with concrete parameters (e.g., `search_issues` with `naturalLanguageQuery: "unresolved TypeError errors"`), specific commands (`git log`, `git blame`), a pre-fix checklist, a verification audit table, and a fill-in report template — per the rubric's instruction-skill note, this qualifies for the top anchor without code samples.

5 / 5

Workflow Clarity

Seven phases are clearly sequenced with explicit validation checkpoints: user confirmation before proceeding (Phase 1), a codebase cross-reference stop check (Phase 4), a pre-fix checklist (Phase 5), and a verification audit with self-challenge feedback loop (Phase 6), matching the anchor-5 pattern of sequence + validation + feedback loops.

5 / 5

Progressive Disclosure

No bundle files exist and the ~120-line body is well-sectioned and self-contained, but it exceeds the under-50-line simple-skill exception and keeps everything inline (e.g., the Quick Reference tool list and Common Patterns section could live in a reference file); anchor 4's "good structure, minor organization gaps" fits better than anchor 5, which requires well-signaled one-level-deep references.

4 / 5

Total

18

/

20

Passed

Description

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

The description is exemplary: concrete third-person capabilities, an explicit "Use when" clause with multiple natural trigger phrases, and a clearly scoped Sentry/MCP niche. It closely follows the strongest reference pattern in the rubric.

DimensionReasoningScore

Specificity

The description lists multiple concrete, domain-specific actions in third person — "Find and fix issues from Sentry using MCP" and "analyzes stack traces, breadcrumbs, traces, and context to identify root causes" — covering discovery, fixing, multi-source analysis, and root-causing comprehensively, matching the anchor-5 example rather than the minor-gaps anchor 4.

5 / 5

Completeness

It explicitly answers both questions: "what" (find/fix Sentry issues, analyze stack traces/breadcrumbs/traces/context) and "when" ("Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry"), with concrete trigger phrases mirroring the anchor-5 example exactly.

5 / 5

Trigger Term Quality

It includes natural trigger phrases with synonym variation — "fix Sentry errors", "debug production issues", "investigate exceptions", "resolve bugs" — covering the ways users would naturally request this skill; only marginal terms like "crashes" are absent, so anchor 5 fits better than anchor 4.

5 / 5

Distinctiveness Conflict Risk

"Sentry" recurs in every clause, establishing a clear niche with distinct triggers and minimal conflict risk against generic debugging or code-fixing skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

14

/

16

Passed

Repository

openclaw/clawhub

Path

.agents/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.