CtrlK
BlogDocsLog inGet started
Tessl Logo

ce-babysit-pr

Babysits or watches an open GitHub PR until merge-ready, continuously reacting to review comments, CI failures, and routine base movement throughout the PR's life. Use when asked to 'babysit the PR', 'watch the PR', monitor, or keep an eye on a PR over time — not a one-shot request to resolve review comments or debug one CI failure (those are separate skills). GitHub only, including GitHub Enterprise.

74

Quality

92%

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

85%Weight 40%Scale 1-3

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

A highly actionable, validation-gated orchestration skill with executable commands, a clear sequenced workflow, and a sound one-level-deep reference split. Its one weakness is conciseness: several load-bearing invariants are restated verbatim across sections and bash setup boilerplate is duplicated, so the 247-line body is longer than necessary without adding clarity.

Suggestions

State each core invariant once — e.g. the 'don't serialize comments and CI' principle and 'ending the loop on a needs-human residual is the primary failure mode' — in the core-principle section, then reference it from Step 2/3/5 instead of restating full paragraphs 3–4 times.

Extract the repeated bash setup boilerplate (SKILL_DIR/SCRATCH_ROOT/STATE_DIR/PY detection, ~7 lines duplicated across ~5 command blocks) into watch-loop.md or a single canonical snippet the later blocks assume, cutting a large fraction of the body length.

Move the detailed merge-ready wake-protocol branches and the full review-still-expected guard into references/watch-loop.md, keeping only the decision rule and the stop ceilings inline in SKILL.md.

DimensionReasoningScore

Conciseness

The body is accurate and operationally dense with no basic-concept padding, but core invariants are restated multiple times — the 'don't serialize comments and CI' principle appears in the intro, the core-principle block, and Step 2, and 'ending the loop the moment one item needs a human is the primary failure mode' is repeated ~4 times — so it 'could be tightened' rather than being lean with every token earning its place.

2 / 3

Actionability

Provides fully executable bash with exact flag names ('pr-snapshot snapshot --pr <N> --repo ... --start-invocation --invocation-budget-seconds <seconds>'), exact gh commands ('gh run rerun <run-id> --failed -R <host>/<owner>/<repo>'), and an exact REST endpoint ('PUT /repos/{owner}/{repo}/pulls/{number}/update-branch' with expected_head_sha) — copy-paste ready, matching the score-3 anchor.

3 / 3

Workflow Clarity

Clear sequence (Steps 1–5 plus an 8-step ordering invariant) with explicit validation checkpoints — head-SHA capture and stale-SHA cancellation, OID revalidation before mutation, the managed-stack atomicity gate, abort-on-conflict residuals — and feedback loops (fix → re-validate), matching the score-3 anchor; the rubric's destructive/batch cap does not apply since validation is pervasive.

3 / 3

Progressive Disclosure

Clean one-level-deep reference structure: watch-loop.md is a genuine terminal reference (no nested refs) signaled at clear points ('Read references/watch-loop.md for the mechanics / state schema / edge cases'), and scripts/pr-snapshot is the referenced executable helper — matching the score-3 anchor of well-signaled one-level-deep references with easy navigation; the inline length is a conciseness concern, not a disclosure-structure failure.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 strong, well-constructed description: it states concrete actions, gives explicit natural-language triggers users would say, answers both what and when, and carves out a clear niche with negative scope that separates it from sibling skills. Third-person voice is used throughout with no first/second-person slip.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions/objects — 'reacting to review comments, CI failures, and routine base movement' — rather than vague language; matches the 'lists multiple specific concrete actions' anchor and is not merely a domain label like the score-2 example.

3 / 3

Completeness

Explicitly answers both what ('Babysits or watches an open GitHub PR until merge-ready, continuously reacting to...') and when ('Use when asked to...'), with an explicit 'Use when' trigger clause plus negative scope, matching the score-3 anchor; not the score-2 'has what, when implied' case.

3 / 3

Trigger Term Quality

Provides good coverage of natural phrases a user would actually say — 'babysit the PR', 'watch the PR', 'monitor', 'keep an eye on a PR over time' — matching the score-3 'good coverage of natural terms' anchor rather than technical jargon or a single keyword.

3 / 3

Distinctiveness Conflict Risk

Clear niche (continuous PR watching) with distinct triggers, and it explicitly distinguishes itself from named sibling skills ('not a one-shot request to resolve review comments or debug one CI failure (those are separate skills)'), making wrong-skill triggering unlikely — matches the score-3 clear-niche anchor.

3 / 3

Total

12

/

12

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.

Validation15 / 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
EveryInc/compound-engineering-plugin
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.