CtrlK
BlogDocsLog inGet started
Tessl Logo

review-pr

Follow an existing FastMCP PR through CI and automated review, evaluate feedback, and verify the current head before reporting readiness.

61

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/review-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-structured guide with executable commands, clear sequencing, and validation checkpoints for a risky merge operation. The only gaps are a few trims for conciseness and one command given as prose rather than code.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence without explaining what a PR or CI is, but a few caveat-dense sentences ('Green CI means...', 'A generic request for human review is not...') could be trimmed, placing it at anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Provides executable commands ('gh pr view ...', 'gh api ... --paginate') plus concrete decision guidance, but inspecting failed job logs is described rather than given as a command, leaving a minor gap at anchor 4 rather than the copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

A clear sequenced process (monitor → fetch checks/reviews → read feedback → assess/fix → verify → final report/merge) with validation checkpoints ('recheck title, body, labels, head, and checks immediately before an authorized merge') and a CI retry/diagnose feedback loop; it is prose sections rather than an explicit numbered checklist with error-recovery, so it sits at anchor 4.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with well-organized sections and a single one-level reference to the code-review skill; with no bundle files needed, the simple-skill exception lets a well-organized body score 5.

5 / 5

Total

17

/

20

Passed

Description

66%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 and distinct, naming a clear domain and several concrete actions with natural trigger terms. Its main weakness is the absence of an explicit 'when to use' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to track an existing FastMCP pull request through CI and review, or to report whether a PR is ready to merge.'

Expand 'PR' to 'pull request (PR)' on first use and include 'checks' among the natural terms to broaden trigger coverage.

Consider naming the readiness/merge-decision outcome more concretely (e.g. 'report merge readiness') to sharpen the 'what'.

DimensionReasoningScore

Specificity

Names the domain (FastMCP PR, CI, automated review) and several concrete actions ('follow... through CI', 'evaluate feedback', 'verify the current head', 'report readiness'); falls at anchor 4 with minor coverage gaps rather than the comprehensive list of anchor 5.

4 / 5

Completeness

The 'what' is clear, but there is no explicit 'Use when...' trigger clause or equivalent guidance for when to invoke the skill; per the rubric guideline, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say ('PR', 'CI', 'review', 'feedback', 'head') are present, but 'PR' is not expanded to 'pull request' and 'checks' is absent, so a few natural synonyms are missing (anchor 4 rather than 5).

4 / 5

Distinctiveness Conflict Risk

Tied to a specific niche (FastMCP PRs through CI/review) it is clearly distinguishable with only minor overlap risk against general code-review skills, matching anchor 4 rather than the fully distinct anchor 5.

4 / 5

Total

15

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
PrefectHQ/fastmcp
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.