CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

monitor-pr

Monitor one or more GitHub PRs and maintain a live status table showing title, link, check status, resolved/total comments, and reviewer approval. Shows a Windows dialog when a PR is ready to merge. Input: a comma-separated list of PR numbers, "mine", or "all".

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

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.

A dense, highly actionable single-file skill that teaches genuinely non-obvious specifics (GraphQL review threads, ADO anonymous timeline API, ETA estimation, flake classification) with strong validation and error-recovery paths. Its main weaknesses are mild redundancy around the polling mandate and monolithic length where reference files would help.

DimensionReasoningScore

Conciseness

Nearly all content is non-obvious operational detail Claude cannot infer (GraphQL pagination, ADO anonymous API access, ETA computation, flake classification) with no padding about concepts Claude already knows. The one trimmable redundancy is the polling mandate restated three times ('MANDATORY: You MUST implement a continuous polling loop', 'Do NOT stop for any other reason', and the Guidelines bullet), which keeps it below the 'every token earns its place' 5 anchor.

4 / 5

Actionability

Guidance is copy-paste executable throughout: complete `gh pr view --json` / `gh pr list` commands, a full GraphQL query with a jq filter, working curl commands for the ADO timeline API, and a ready-to-run PowerShell MessageBox command. A concrete example output table covers the common rendering case, matching the fully-executable 5 anchor.

5 / 5

Workflow Clarity

The process is clearly sequenced (prerequisites → resolve PR list → build table → classify failures → poll loop) with explicit validation checkpoints (verify `gh auth status`, validate each PR exists, check PowerShell availability) and genuine error-recovery feedback loops (skip dialogs if PowerShell is missing, paginate when totalCount > 100, flake vs real-failure decision procedure). This matches the score-5 anchor including its validation-steps requirement for the git-push operation.

5 / 5

Progressive Disclosure

A single well-sectioned file with clear headers, no nested or dangling references (no bundle files exist), and easy linear navigation. It scores 4 rather than 5 because at ~227 lines the Checks-ETA procedure and ADO log-fetching detail are self-contained subtopics that could be split into reference files, and the 'simple skill' full-score exception only applies under 50 lines.

4 / 5

Total

18

/

20

Passed

Description

71%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 with concrete enumerated capabilities, undermined by the complete absence of a 'when to use it' trigger clause and slightly thin keyword synonym coverage. Fixing the trigger guidance is the highest-leverage improvement.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to monitor PRs, watch CI checks, or be notified when a pull request is ready to merge.'

Broaden natural trigger vocabulary with synonyms such as 'pull request', 'CI checks', 'CI status', and 'merge readiness'.

Consider mentioning the polling/refresh behavior in the description so it is distinguishable from one-shot PR lookup skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with an enumerated output surface: 'Monitor one or more GitHub PRs and maintain a live status table showing title, link, check status, resolved/total comments, and reviewer approval' plus 'Shows a Windows dialog when a PR is ready to merge'. Coverage of the skill's capabilities is comprehensive, matching the score-5 anchor rather than the 'minor gaps' of score 4.

5 / 5

Completeness

The 'what' is clearly stated (live status table, merge alerts, dialog notification) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric says caps completeness at 3. It does not fall to 2 because the 'what' is specific and the input format is documented, unlike the vague-what example at anchor 2.

3 / 5

Trigger Term Quality

Natural terms like 'GitHub PRs', 'check status', 'reviewer approval', and 'ready to merge' are present, but common variations users would say are missing — 'pull request' spelled out, 'CI checks', 'CI status'. This fits 'good keyword coverage; a few natural terms missing' (4) rather than the synonym-complete 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The PR-monitoring/live-status/merge-alert niche is mostly distinct from other skills, with only minor overlap risk against PR review or code-review skills. It is not a 5 because phrases like 'check status' and 'reviewer approval' could plausibly surface review-focused skills too.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BabylonJS/Babylon.js

Path

.github/skills/monitor-pr/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.