CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

babysit-pr

Monitor a pull request through review and CI. Use when the user asks to monitor, watch, or babysit a PR.

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An unusually tight operational skill: every section gives environment-specific instructions Claude could not infer, with executable commands, explicit exit-code contracts, and validation checkpoints around the risky merge operation. The only improvement space is trimming a couple of low-value framing lines.

DimensionReasoningScore

Conciseness

The body is dense and imperative and assumes Claude's competence throughout (no explanation of what PRs, CI, or review bots are), but lines like "Many repos have AI review bots. They're helpful, even if they are not always right." and "Screenshots and videos help as well..." are minor padding that could be trimmed.

4 / 5

Actionability

Guidance is copy-paste ready: a complete pr-wait invocation with flags and enumerated exit codes (0/1/2), exact commands (gh api rate_limit --jq .resources.graphql, gh api repos/<owner>/<repo>/pulls/<n>, git fetch), and concrete tool directives (Monitor tool with timeout_ms: 3600000).

5 / 5

Workflow Clarity

The sequence is clear (handle existing checks first, start exactly one watcher, act on events, rebase when behind, gate the merge) with explicit validation before the destructive merge step ("run git fetch and check the PR again", "Never merge when it is BEHIND or DIRTY") and error-recovery loops (rate-limit reset handling, restart after an exit 1 or a push).

5 / 5

Progressive Disclosure

A well-sectioned single body whose only bundle reference, scripts/pr-wait (a real 556-line executable), is one level deep and clearly signaled with usage instructions ("Wait with scripts/pr-wait from this skill's directory (use its absolute path)"); the bulk of the script is appropriately kept out of SKILL.md.

5 / 5

Total

19

/

20

Passed

Description

82%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 concise, well-formed description with an explicit what and a strong Use-when clause containing natural trigger synonyms. Its only weakness is that the what-clause states a single action without listing the concrete capabilities the skill covers.

Suggestions

Expand the what-clause with one or two concrete capabilities, e.g. "Start a single watcher, handle review-bot findings and CI failures as they arrive, and gate the merge" — this would raise specificity without adding padding.

Consider adding one more natural trigger variant such as "keep an eye on" or "wait for checks" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Monitor a pull request through review and CI" names the domain (PR, review, CI) and one concrete action, but does not enumerate what monitoring involves (handling review comments, restarting watchers, gating merges), matching the 1-2-concrete-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

It explicitly answers both parts: a clear what ("Monitor a pull request through review and CI") and an explicit when with concrete trigger phrases ("Use when the user asks to monitor, watch, or babysit a PR"), matching the top anchor exactly.

5 / 5

Trigger Term Quality

"monitor, watch, or babysit a PR" gives natural synonym triggers users would actually say, but a few common variants (e.g. "keep an eye on", "wait for CI/checks") are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

PR monitoring with the distinct trigger verbs "monitor, watch, or babysit" carves a clear niche that is unlikely to fire for PR-creation or code-review skills, matching the minimal-conflict-risk anchor.

5 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

adamsardo/tstack-marketplace

Path

plugins/tstack/skills/babysit-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.