CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-issue

Review an incoming external issue (and any gated-closed PR behind it) and decide whether to assign the contributor or decline. Use when the maintainer says "look at this issue", "review issue

Quality

97%

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

96%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 an exemplary instruction-only skill: lean and information-dense, with copy-paste gh commands for every common action, a clearly sequenced procedure with validation checkpoints and error-recovery guidance, and well-signaled repo references. The only minor tension is that all policy lives in one moderately long file with no offloading to reference files.

DimensionReasoningScore

Conciseness

The body is dense, repo-specific policy throughout (e.g., 'Behavior that only appears by mutating construction-time state or relying on internals is a property of the code, not a defect') with no explanation of concepts Claude already knows and no padding. Not 4: no over-explanatory passages were found that could be trimmed.

5 / 5

Actionability

Every operational step has copy-paste-ready gh commands with explicit --json field lists (e.g., 'gh issue edit N --repo PrefectHQ/fastmcp --add-assignee <login>' and 'gh issue comment ... --body-file /tmp/triage-reply.md'), covering orient, contributor checks, assign, and decline. Not 4: the common cases are all fully executable; only 'record the accepted approach' is softly specified.

5 / 5

Workflow Clarity

A clearly sequenced 7-step procedure with validation checkpoints ('check that the tests fail without the fix'), an explicit error-recovery loop ('If that run fails, the gate misbehaved: investigate the run rather than re-assigning'), a final 'Check before finishing' checklist, and authorization gates on the outward-facing decline action. Not 4: checkpoints and feedback loops are present, so no cap applies.

5 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep references (require-issue-link.yml, the contribution policy, the sibling review-pr skill) and no bundle files to split. Not 5: the ~72-line body exceeds the under-50-line simple-skill exception, so it is a well-structured single-file procedure with minor organization tension rather than content appropriately split across files.

4 / 5

Total

19

/

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 specific, complete, and highly triggerable: it names the concrete actions, gives explicit quoted 'Use when' trigger phrases, and explicitly distinguishes itself from the adjacent review-pr skill. It is concise with no filler or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — reviewing an incoming external issue and any gated-closed PR, deciding to assign or decline, and the auto-reopen side effect of assignment — with comprehensive coverage and no vague language. Not 4: there are no coverage gaps in what the skill does.

5 / 5

Completeness

Explicitly answers both what (review issue and gated PR, assign or decline, assignment reopens the PR) and when ('Use when the maintainer says...' with concrete trigger phrases), in third-person voice. Not 4: the 'when' clause is explicit and specific rather than improvable.

5 / 5

Trigger Term Quality

Quotes four natural maintainer phrasings ('look at this issue', 'review issue #N', 'should we take this', 'whether to assign someone') plus the 'incoming-issue triage' term. Not 4: no commonly used trigger phrasing for this domain is missing.

5 / 5

Distinctiveness Conflict Risk

States 'the entry point for incoming-issue triage — distinct from review-pr, which assesses the full change and follows CI and review feedback', explicitly separating the closest sibling skill. Not 4: triggers are triage-specific with minimal conflict risk.

5 / 5

Total

20

/

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

relative_links

Relative link issues: 6 suspicious

Warning

Total

15

/

16

Passed

Repository

PrefectHQ/fastmcp

Path

.agents/skills/review-issue/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.