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.

61

Quality

71%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands, a complete parameter table, and a clearly sequenced workflow with explicit error/scope validation checkpoints, backed by a real bundle script. Its only weakness is mild redundancy in the Tips section, which restates the priority categories.

DimensionReasoningScore

Conciseness

The body is mostly lean with concrete commands and tables, but the Tips section re-explains each priority category already covered in "Priority Categories", and the "When to Use" trigger list plus repeated CRITICAL/IMPORTANT callouts add padding that could be tightened.

2 / 3

Actionability

Quick Start gives copy-paste-ready `pwsh ...query-reviewable-prs.ps1` invocations with flags, the Script Parameters table enumerates every flag with values and defaults, and the referenced script bundle exists at scripts/query-reviewable-prs.ps1.

3 / 3

Workflow Clarity

The three-step workflow is explicitly sequenced with validation checkpoints: script failure triggers STOP/report/retry, Step 2 checks for the read:project scope warning to surface, and Step 3 mandates presenting all categories with required columns.

3 / 3

Progressive Disclosure

The body is a well-organized overview (When to Use, Quick Start, Parameters, Workflow, Tips) with a single one-level-deep reference to the bundle script at scripts/query-reviewable-prs.ps1, which exists; no deeply nested references and content is appropriately scoped to one file.

3 / 3

Total

11

/

12

Passed

Description

57%

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 clearly niche-scoped to two named repositories, but it lacks an explicit "Use when..." trigger clause and leans on embedded keywords rather than natural user phrasings. Tightening the action verbs and adding explicit trigger guidance would lift completeness and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause naming natural triggers such as "find a PR to review", "show milestoned PRs", or "find partner/community PRs".

Replace the abstract phrase "good candidates for review" with concrete enumerated actions (e.g. "lists, sorts, and categorizes open PRs by priority").

Surface natural user phrasings ("PRs waiting for review", "ready-to-review PRs") rather than only internal label names.

DimensionReasoningScore

Specificity

Quotes like "Finds open PRs in the dotnet/maui and dotnet/docs-maui repositories" and "prioritizing by milestone, priority labels, partner/community status" name the domain and several concrete prioritization criteria, but the governing action "good candidates for review" stays somewhat abstract rather than enumerating multiple distinct actions.

2 / 3

Completeness

It clearly states what the skill does (finds and prioritizes reviewable PRs) but provides no "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Terms such as "PRs", "review", "milestone", "priority labels", "partner", and "community" are natural, but the description relies on these embedded nouns and omits common phrasings a user would actually say (e.g. "find a PR to review", "waiting for review"), missing common variations.

2 / 3

Distinctiveness Conflict Risk

The description is scoped to the specific dotnet/maui and dotnet/docs-maui repositories with domain-specific prioritization signals, giving it a clear niche unlikely to conflict with unrelated skills.

3 / 3

Total

9

/

12

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.