CtrlK
BlogDocsLog inGet started
Tessl Logo

ce-babysit-pr

Babysits an open GitHub PR until merge-ready. Use when asked to watch a PR over time — not for one-shot comment resolution or one CI failure. GitHub (incl. Enterprise) only.

71

Quality

87%

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 exceptionally well-structured instruction-only skill: terse, concrete, and explicitly sequenced with validation checkpoints and real one-level-deep references. Its only shortcoming is a couple of dense run-on paragraphs that slightly tax the reader.

Suggestions

Split the dense Step 3 paragraph into a short bulleted list of true-stop conditions so the failure-mode guidance ('stopping the run there is the primary failure mode') stands out.

Break the long 'Authority comes from the babysit invocation' boundary sentence into labeled Downward/Upward sub-points for faster scanning.

DimensionReasoningScore

Conciseness

Dense and operational with no padding or explanation of concepts Claude already knows, assuming competence throughout; a few run-on sentences (notably the Step 3 paragraph) could be tightened, keeping it just below the lean anchor 5.

4 / 5

Actionability

Provides concrete executable commands ('gh run rerun <run-id> --failed -R <host>/<owner>/<repo>', 'gh stack merge', 'ce-resolve-pr-feedback mode:pipeline') and exact stop-condition predicates (MERGEABLE, CLEAN, open_needs_human == 0) covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced four-step process with an explicit ordering invariant, validation checkpoints (terminal check, stale-SHA cancellation), enumerated stop conditions, and feedback loops for the destructive/batch-style push and branch mutations.

5 / 5

Progressive Disclosure

SKILL.md is a concise overview with well-signaled one-level-deep references to real bundled files (references/tick.md, envelope.md, settle.md, etc.) and the pr-snapshot script; content is appropriately split and easy to navigate.

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, third-person description with explicit what/when guidance and sharp negative triggers that carve out a distinct niche. It is slightly under-specified on the range of concrete actions performed, which is the only weakness.

DimensionReasoningScore

Specificity

Names the domain and a single concrete action ('Babysits an open GitHub PR until merge-ready') but does not enumerate multiple specific actions, fitting anchor 3 over the multi-action anchors 4-5.

3 / 5

Completeness

Explicitly answers both 'what' (babysits a PR until merge-ready) and 'when' with concrete trigger phrases and explicit negative guidance ('Use when asked to watch a PR over time — not for one-shot comment resolution or one CI failure').

5 / 5

Trigger Term Quality

Natural phrases a user would say ('watch a PR over time', 'one CI failure', 'one-shot comment resolution') give good coverage, but some synonyms (review, monitor) are missing, placing it just below comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche (long-term GitHub PR babysitting) with negative triggers that distinguish it from one-shot comment resolution and single-CI-failure skills, giving minimal conflict risk.

5 / 5

Total

17

/

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.

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.