CtrlK
BlogDocsLog inGet started
Tessl Logo

babysit-pr

Shepherd an already-open pull request to a mergeable state — poll CI, triage review comments, verify each one against the source, push fixes, and keep the branch current. Use when the user asks to "babysit", "monitor", "watch", "shepherd", or "drive" a PR, asks you to "fix the CI on my PR", "handle the review comments", "get this PR green", or "wait for checks and address feedback". Picks up where the `file-pr` skill leaves off. Does not approve, merge, or close anything.

77

Quality

98%

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

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

Excellent operational skill body: lean, fully executable, with a clearly sequenced loop, explicit stop conditions, safety rails (Rule 0 untrusted-input handling, Never list), and validation-before-action rules throughout. The only structural note is that at ~120 lines with zero progressive disclosure, a couple of the longer blocks could live in reference files, though the current split is defensible for a cohesive single-purpose workflow.

Suggestions

Move the multi-line graphql review-thread query and/or the reply template into a references/ file (e.g. references/queries.md) and link to it, slimming SKILL.md to the decision logic and letting it qualify for the simple-skill top score on progressive_disclosure.

Consider stating where the one-line-per-pass report output should go (chat vs. a running summary) so the 'report in one line' loop step is unambiguous about its destination.

DimensionReasoningScore

Conciseness

Every section earns its place: no explanation of concepts Claude already knows, no padding, and the reply section even shows a minimal two-line template instead of describing style rules in prose. Commands carry the information, not exposition.

5 / 5

Actionability

Fully executable throughout: complete gh/git commands (including a full graphql query with --jq filter for unresolved threads), copy-paste rebase/force-with-lease snippet, and a concrete reply template. Triage decision rules are stated as if/then branches with commands attached.

5 / 5

Workflow Clarity

The loop is explicitly sequenced ('gather → triage → fix → push once → report in one line') with hard stop conditions, validation checkpoints ('Verify every finding against the source before changing anything', 'check gh run list --branch $BASE' when a failure is out of scope), and error-recovery feedback (rerun infra failures 'at most twice', stop after two failed fix attempts). Rule 0 adds an explicit validation gate for untrusted PR content.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clear, navigable sections and one legitimate cross-link to the file-pr skill; no bundle files exist so nothing is misfiled. It sits at ~120 lines with everything inlined (e.g., the graphql query and reply template), which exceeds the 'under 50 lines, no external references needed' case for a top score, but the content is cohesive operational guidance rather than reference material that should be split.

4 / 5

Total

19

/

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.

A model description: concrete third-person action list, an explicit 'Use when' clause rich with natural user phrasings and synonyms, clear handoff positioning relative to the file-pr skill, and explicit non-goals that eliminate conflict risk. Nothing to add or trim.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'poll CI, triage review comments, verify each one against the source, push fixes, and keep the branch current' — which comprehensively cover the skill's capabilities, and adds explicit non-goals ('Does not approve, merge, or close anything').

5 / 5

Completeness

Explicitly answers both: what ('Shepherd an already-open pull request to a mergeable state' plus the concrete action list) and when (a full 'Use when the user asks to...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Quoted trigger phrases read like real user requests with synonym coverage: 'babysit', 'monitor', 'watch', 'shepherd', 'drive a PR', 'fix the CI on my PR', 'handle the review comments', 'get this PR green', 'wait for checks and address feedback'.

5 / 5

Distinctiveness Conflict Risk

Clear niche — post-PR-creation shepherding ('Picks up where the file-pr skill leaves off') with explicit boundaries ('Does not approve, merge, or close anything') that separate it from generic PR or CI skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository
RoleModel/rolemodel-skills
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.