CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

babysit

Drive an open PR to mergeable. Watch CI, fix real failures at the root, triage review comments (fix, dismiss, or ask), and resolve conflicts. Use for /babysit, "babysit this PR", or right after opening a PR.

77

Quality

97%

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

100%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 exemplary instruction-only skill body: it specifies exact gh/git commands, a clear classification scheme for CI failures and review comments, explicit validation checkpoints within a feedback loop, and safety guardrails — all in a lean ~27 lines with no padding. Nothing material is missing at this scope.

DimensionReasoningScore

Conciseness

Every line is a directive, decision rule, or guardrail ("Don't poll with sleeps", "A second failure of the same shape is not a flake; treat it as real", "Never plain force-push a shared branch") with zero re-teaching of concepts Claude already knows, matching the lean anchor 5 rather than anchor 4's "minor instances of over-explanation".

5 / 5

Actionability

The body is fully executable with exact commands and flags throughout — `gh pr view <number> --json number,headRefName,baseRefName,mergeable,reviewDecision,statusCheckRollup`, `gh pr checks <number> --watch --fail-fast`, `gh run view <run-id> --log-failed`, `gh api repos/{owner}/{repo}/pulls/<number>/comments`, and `push with --force-with-lease` — covering the common cases for each loop step.

5 / 5

Workflow Clarity

A numbered six-step loop with explicit validation feedback — re-watch CI after every push, "rerun the local checks" after a rebase, a rerun-once flake policy with escalation to real failure — plus a defined exit condition ("until the exit condition holds or two consecutive rounds make no progress"), matching the anchor-5 feedback-loop pattern.

5 / 5

Progressive Disclosure

The body is under 50 lines with no need for external references (none exist in the bundle) and is cleanly organized into focused sections (intro contract, "## Loop", "## Guardrails"), which per the rubric's simple-skill guideline merits a 5.

5 / 5

Total

20

/

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 description that states concrete capabilities in third person and gives explicit, natural trigger guidance including the slash command and a quoted phrase. The only weakness is modest synonym coverage in the trigger clause (e.g., no spelled-out "pull request" or failing-CI phrasing), which keeps trigger term quality just short of comprehensive.

DimensionReasoningScore

Specificity

"Watch CI, fix real failures at the root, triage review comments (fix, dismiss, or ask), and resolve conflicts" lists multiple concrete actions covering the full domain (checks, failures, comments, conflicts), matching the comprehensive-coverage anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

The description explicitly answers both what ("Drive an open PR to mergeable" plus enumerated actions) and when ("Use for /babysit, 'babysit this PR', or right after opening a PR") with concrete trigger phrases, exactly the anchor-5 pattern; anchor 4's caveat about a less-specific 'when' does not apply.

5 / 5

Trigger Term Quality

Triggers "/babysit", "\"babysit this PR\"", and "right after opening a PR" are natural phrases users would say, but common variations like "pull request" spelled out, "failing checks", or "watch my PR" are missing, so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Drive an open PR to mergeable" with babysit-specific triggers carves a clear niche (owning a PR through CI, comments, and conflicts) with minimal overlap risk against review- or fix-focused skills; it is not merely "mostly distinct" as anchor 4 describes.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

adamsardo/pstack-claude

Path

plugins/pstack/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.