CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-monitor

Monitors Dependabot and Snyk dependency upgrade PRs, automatically merging them when builds pass. Handles javax/jakarta compatibility validation and provides detailed status reporting. Use when the user says "monitor PRs", "watch builds", "auto-merge PRs", "merge passing PRs", or "watch dependency PRs".

70

Quality

85%

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

71%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 content is well-structured and actionable with concrete commands and a clear monitoring workflow, but it leans slightly long and references a bundled script that is absent from the skill bundle. Progressive disclosure is the weakest area due to the missing referenced file and inlined auxiliary content.

Suggestions

Ship the referenced pr-monitor.sh in a scripts/ directory so the documented invocations actually exist in the bundle.

Trim or externalize the Example Session and full output-format blocks to reduce inline length and improve conciseness.

Resolve the inconsistency between 'Merge immediately' guidance and the --auto flag (which queues rather than merges immediately), or clarify the intended behavior.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable command examples, but the Example Session and Notes sections repeat information already conveyed elsewhere, adding mild padding.

4 / 5

Actionability

It provides concrete, mostly copy-paste-ready gh commands and exact script invocations, but the referenced pr-monitor.sh is not present in the bundle and the passing-merge instruction ('Merge immediately' vs '--auto' queue) is slightly inconsistent.

4 / 5

Workflow Clarity

A clear four-step sequenced workflow with state-based handling and a monitoring loop is present, with validation (build status, jakarta checks) before merging; minor gaps remain in explicit merge-success verification.

4 / 5

Progressive Disclosure

The skill is a single ~150-line inline document with no actual bundle files present; the referenced pr-monitor.sh does not exist in the bundle, and content like full output samples and the Example Session could be separated.

3 / 5

Total

15

/

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 excellent: it concisely states concrete capabilities, names the specific tools involved, and provides a comprehensive set of natural trigger phrases. It cleanly answers both 'what' and 'when' with minimal conflict risk.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions (monitors, auto-merges, javax/jakarta validation, status reporting) tied to named systems (Dependabot, Snyk), giving comprehensive coverage of capabilities.

5 / 5

Completeness

It explicitly answers both what the skill does and when to use it, with concrete trigger phrases matching the anchor-5 example.

5 / 5

Trigger Term Quality

It provides five natural phrasings users would actually say ("monitor PRs", "watch builds", "auto-merge PRs", "merge passing PRs", "watch dependency PRs") as explicit triggers.

5 / 5

Distinctiveness Conflict Risk

The dependency-upgrade-PR monitoring and javax/jakarta niche is clearly distinct with specific triggers, creating minimal overlap risk with other skills.

5 / 5

Total

20

/

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
mock-server/mockserver-monorepo
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.