CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sentry-top-issue

Pick the single highest-priority unresolved Sentry issue and hand it off to a fixer skill. Use when triaging Sentry errors, running automated issue triage, or when asked to fix the top Sentry issue in a project.

Quality

90%

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.

An exemplary procedural skill body: copy-paste-ready commands, a well-sequenced multi-phase workflow with explicit validation and terminal-state handling, and proper delegation of mechanics to bundled scripts. The only trims available are duplicated instructions (skip reasons, verbatim-echo rule) and a small path-convention gap in script references.

Suggestions

Deduplicate the preflight skip-reason list, which appears both in the skip-status branch and again in the scope-precedence paragraph of Phase 1a.

State the 'always echo raw JSON output verbatim' rule once (e.g., as a global convention near the top) instead of repeating it in Phase 1a and Phase 2 Step 1.

Reference the bundle scripts by a path convention that does not hardcode the skills/sentry-top-issue/ install location, or note that paths are relative to the repo root where the skill is installed.

DimensionReasoningScore

Conciseness

Operational throughout with no concept padding and rationale only where judgment calls need justification, but the skip-reason list is stated twice (Phase 1a) and the 'echo raw JSON verbatim' instruction is duplicated across Phase 1 and Phase 2, so it is not anchor 5's 'every token earns its place'.

4 / 5

Actionability

Fully executable guidance: exact bash invocations with flags, exact git log/grep commands with suffix-computation examples, explicit output schemas, and copy-paste-ready print templates; all three referenced scripts exist in the bundle and match the documented flags and behavior.

5 / 5

Workflow Clarity

Clear phased sequence with explicit validation checkpoints (preflight skip handling, three filters, PR cap), feedback loops (tier fallback, graceful degradation of gh/jq checks), and a terminal-states checklist covering every exit path.

5 / 5

Progressive Disclosure

Mechanics (scope parsing, API query construction, PR matching) are appropriately delegated to three real, one-level-deep bundle scripts clearly signaled via fenced invocations, but script paths assume the skills/sentry-top-issue/ install location rather than bundle-relative references, a minor organization gap that keeps it below anchor 5.

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: concrete, third-person, with an explicit 'Use when...' clause covering natural trigger phrasings and a distinct Sentry-triage niche. Its only gap is that keyword coverage misses a few synonyms and it compresses the skill's filtering/dedup behavior into two actions.

DimensionReasoningScore

Specificity

Two precisely qualified concrete actions ('Pick the single highest-priority unresolved Sentry issue', 'hand it off to a fixer skill') fully describe the skill's behavior, exceeding anchor 3's generic two-action example, but 'several' actions (anchor 5) are not listed.

4 / 5

Completeness

Clearly states what the skill does (pick the top-priority unresolved Sentry issue, hand off to a fixer) and explicitly when to use it via an explicit 'Use when' clause with three concrete trigger phrases, matching the anchor-5 example's shape.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('triaging Sentry errors', 'automated issue triage', 'fix the top Sentry issue'), but a few natural synonyms like 'error monitoring' or 'Sentry alerts' are missing, so it stops short of anchor 5's comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear Sentry-triage niche and explicitly distinguishes its picker role from the fixer skill it hands off to, so conflict risk with other skills is minimal.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

RoleModel/rolemodel-skills

Path

skills/sentry-top-issue/SKILL.md

Revision

81c5ba2

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill