CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

babysit

Drive an open PR to merge-ready on the watch-pr verdict policy — watch checks and review state, fix CI, address comments; never merges, rebases, or force-pushes. For 'get this green' or 'babysit PR #N'.

Quality

79%

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

Fix and improve this skill with Tessl

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

Quality

Content

77%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 highly actionable, well-sequenced operational skill with excellent command-level specificity and validation checkpoints. Its weaknesses are structural: the two bundled reference files are orphaned (never referenced from the body, which duplicates their content inline), the ledger script is inlined rather than placed in scripts/, and the core safety constraint is repeated several times.

Suggestions

Link references/bugbot-triage.md and references/merge-safety.md from the body (e.g., in step 3's review lane and in Rules) and trim the inline duplicates, so the bundle's one-level-deep references are actually discoverable.

Move the step-4 ledger-writing node script into scripts/ (e.g., scripts/append-ledger.sh) and invoke it with the PR number, head SHA, and evidence as arguments, shrinking SKILL.md substantially.

State the never-merge/rebase/force-push constraint once in Rules and refer back to it from step 3 and the verdict policy instead of repeating it nearly verbatim four times.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious operational knowledge (gh exit-code quirks, `reviewDecision` empty-string semantics, `HAS_HOOKS` classification), but the never-merge/rebase/force-push constraint is repeated four times (intro, step 3, the verdict policy note, and Rules), and step 4 embeds a long inline node script that belongs in scripts/. It is mostly efficient but could be tightened, matching anchor 3 rather than 4.

3 / 5

Actionability

Every step carries exact executable commands (`gh pr view <N> --json state,mergeable,...`, `gh pr checks <N> --json name,bucket`, the branch-protection `gh api` call, the copy-paste-ready ledger node script with explicit placeholders) plus fully specified classification rules with field values and edge cases (bucket `cancel`, 60-second no-checks window, `HAS_HOOKS`). This matches anchor 5 — copy-paste ready commands covering the common cases — and not anchor 4, which expects minor gaps.

5 / 5

Workflow Clarity

The Loop is a clearly numbered sequence (read state → apply policy → act → ledger → report) with explicit validation checkpoints ("verify the checkout sits on that PR's head before mutating anything", "Confirm the first read reports the requested PR") and feedback loops (re-poll on UNKNOWN, "wait for its push before re-classifying", the no-checks confirmation window), with explicit stop conditions. This matches anchor 5; anchor 4's 'minor validation gaps' does not apply.

5 / 5

Progressive Disclosure

The bundle contains references/bugbot-triage.md and references/merge-safety.md, but the body never links to or signals either file — instead it inlines condensed duplicates of both (bot-triage rules in step 3 and Rules; merge-safety rules in the intro and Rules), and the ledger script that belongs in scripts/ is inlined. This matches anchor 3 ('references present but not clearly signaled; content that should be separate is inline') — not 4, since the references are not navigable from SKILL.md at all, and not 2, since the body itself has clear section structure.

3 / 5

Total

16

/

20

Passed

Description

75%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 description: third-person, concise, with a clear what, an explicit trigger clause, and honest scope boundaries. It sits solidly at anchor 4 across dimensions — the main gaps are thin trigger-synonym coverage and an unexplained internal term ('watch-pr verdict policy') in an otherwise concrete summary.

Suggestions

Broaden the 'when' clause with one or two more natural variations, e.g. "Use when the user says 'get this green', 'make CI pass', or wants a PR driven to merge-ready while they're away".

Replace or gloss the opaque internal term 'watch-pr verdict policy' with a plain-language phrase such as 'a strict green/blocked/waiting classification' so the description is self-contained.

DimensionReasoningScore

Specificity

The description names several concrete actions — "watch checks and review state, fix CI, address comments" — plus explicit exclusions ("never merges, rebases, or force-pushes"), matching anchor 4's 'several specific actions; minor gaps'. It is not 5 because "address comments" and "on the watch-pr verdict policy" are generic/opaque, and not 3 because the action list goes beyond 1-2 items.

4 / 5

Completeness

Both parts are present: a clear, bounded 'what' ("Drive an open PR to merge-ready... watch checks and review state, fix CI, address comments; never merges, rebases, or force-pushes") and an explicit 'when' with concrete trigger phrases ("For 'get this green' or 'babysit PR #N'"). This clears the missing-trigger cap of 3; it stops short of anchor 5 because the 'when' covers only two narrow phrasings and omits scenarios like driving a PR to merge-ready while the user is away or addressing review-bot comments.

4 / 5

Trigger Term Quality

It quotes two natural trigger phrases users would actually say — "'get this green' or 'babysit PR #N'" — which is good keyword coverage per anchor 4. It is not 5 because common synonyms are missing (e.g., "make CI pass", "fix failing checks", "address the review-bot comments"), and not 3 because the quoted phrases are directly usable rather than merely 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The babysitting/monitoring niche with distinctive triggers ('babysit PR #N', 'get this green') and the never-merge constraint set it apart from PR-creation and review skills, matching anchor 4's 'mostly distinct; minor overlap risk'. It is not 5 because "fix CI" and "address comments" overlap with standalone fix-ci and code-review skills.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

Yeachan-Heo/oh-my-claudecode

Path

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