CtrlK
BlogDocsLog inGet started
Tessl Logo

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep watching open PRs so fresh review feedback is surfaced promptly. Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR.

79

1.72x
Quality

80%

Does it follow best practices?

Impact

95%

1.72x

Average score across 2 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/babysit-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable guide with a clear monitoring loop and real reference files; its main weakness is repetition across sections that inflates token usage without adding information.

Suggestions

Consolidate the repeated 'restart --watch immediately after a push' and 'process review before flaky rerun' guidance into a single authoritative section instead of restating it in Core Workflow, Review Comment Handling, Git Safety, and Monitoring Loop Pattern.

Move the polling cadence + stop-conditions detail into references/heuristics.md and keep only the essentials inline to reduce the body length.

Add the exact shell-level polling loop invocation (sleep + --once/--watch timing) as an executable snippet so Claude can copy-paste the cadence rather than infer it.

DimensionReasoningScore

Conciseness

Mostly efficient but noticeably repetitive — the push/restart-watch guidance and 'review before flaky rerun' priority are restated across Core Workflow, Review Comment Handling, Git Safety, and Monitoring Loop Pattern, which could be tightened.

3 / 5

Actionability

Provides concrete, copy-pasteable commands (python3 .../gh_pr_watch.py --pr auto --watch) and specific gh/API invocations; minor gaps around exact polling-loop shell invocation and timing control.

4 / 5

Workflow Clarity

Clear sequenced loop with explicit validation/checkpoints (stop conditions, failed-jobs-before-run-completes diagnosis, retry budget of 3, resolve-thread policy); minor gaps from some duplication rather than missing checkpoints.

4 / 5

Progressive Disclosure

Good one-level-deep references to heuristics.md and github-api-notes.md (both real files) plus a watcher script; the body is long and could offload more detail to references, but navigation is clear.

4 / 5

Total

15

/

20

Passed

Description

92%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 strong, concrete description that covers what it does, when to use it, and distinct trigger phrases in third person. Minor improvement possible by including a couple more natural synonyms, but it lands at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'polling review comments, CI checks/workflow runs, and mergeability state', 'Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what (continuous polling, diagnosis, retry, auto-fix) and when ('Use when the user asks Codex to monitor a PR, watch CI, handle review comments, or keep an eye on failures and feedback on an open PR').

5 / 5

Trigger Term Quality

Includes natural phrases users say ('monitor a PR', 'watch CI', 'handle review comments', 'keep an eye on failures and feedback'), though it misses a few common synonyms like 'babysit' as a standalone trigger term beyond the name.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (persistent post-creation PR monitoring/CI babysitting) with distinct triggers unlikely to fire for unrelated skills.

5 / 5

Total

19

/

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
openai/codex
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.