CtrlK
BlogDocsLog inGet started
Tessl Logo

find-reviewable-pr

Finds open PRs in the dotnet/maui and dotnet/docs-maui repositories that are good candidates for review, prioritizing by milestone, priority labels, partner/community status.

62

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 ./.github/skills/find-reviewable-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-structured skill body with concrete commands and clear error-handling workflow steps. Its main weakness is conciseness: category information and command variants are repeated where the parameter table already suffices.

Suggestions

Collapse the eleven Quick Start command variants into 2-3 representative examples and rely on the parameter table for the rest, since the table already documents every flag.

Remove the standalone Tips section or fold it into the Priority Categories list, as it restates the same categories already defined above.

In Step 3, reference the canonical category list once instead of re-listing all nine categories a second time.

DimensionReasoningScore

Conciseness

Mostly efficient and free of over-explanation, but the category list is repeated across three sections (Priority Categories, Step 3, Tips) and the Quick Start lists eleven near-identical command variants already covered by the parameter table, so it could be tightened.

3 / 5

Actionability

Provides fully executable, copy-paste-ready pwsh commands with the concrete script path, plus a parameter table with explicit values and defaults covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced three-step workflow with explicit error handling on script failure (STOP / report / retry) and a mandatory warning check, though the presentation step lacks a final output-validation checkpoint.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections with a one-level-deep, clearly signaled reference to the bundled scripts/query-reviewable-prs.ps1; minor gaps in that some redundant inlined content could be consolidated.

4 / 5

Total

16

/

20

Passed

Description

70%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 specific, third-person description that clearly names its niche and prioritization criteria, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Trigger-term coverage is good but could add synonyms.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when the user asks to find a PR to review, find milestoned/partner/community PRs, or review docs-maui PRs').

Include the full synonym 'pull requests' alongside 'PRs' to broaden natural trigger-term coverage.

Briefly mention the output (a prioritized, categorized list of open PRs) so the 'what' includes the result, not just the search action.

DimensionReasoningScore

Specificity

Names the domain (finding reviewable PRs in specific repos) and several concrete prioritization criteria ('milestone, priority labels, partner/community status'), leaving only minor gaps in coverage.

4 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('PRs', 'review', 'milestone', 'partner/community'), but omits common synonyms such as the full 'pull requests' phrasing.

4 / 5

Distinctiveness Conflict Risk

Scoped to the specific dotnet/maui and dotnet/docs-maui repos with a distinct prioritization niche, giving it minimal conflict risk with other skills.

5 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/maui
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.