CtrlK
BlogDocsLog inGet started
Tessl Logo

baby-sit

Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.

69

Quality

85%

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.

The body is a tight, highly actionable runbook with explicit validation checkpoints and clean section structure, well-matched to a single-purpose skill that needs no external references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's intelligence — no explanations of what CI, gh, or webhooks are — and nearly every token is actionable guidance, with no padding.

5 / 5

Actionability

Fully executable commands throughout — 'gh pr view', 'gh pr checks --json name,bucket,state,workflow,link', 'gh run view <run-id> --log-failed', 'gh run rerun <run-id> --failed', and manage_baby_sit action calls — cover the common cases concretely.

5 / 5

Workflow Clarity

Sequenced phases (start/stop, diagnosis, rerun, stop conditions) carry explicit checkpoints — 'Confirm the failure belongs to the current head SHA', classification with stop branches, permission-failure handling — including validation/feedback loops for the destructive rerun operation.

5 / 5

Progressive Disclosure

A single ~50-line SKILL.md with no external references needed, organized into clearly headed sections; per the rubric's simple-skill guidance this scores 5 with just well-organized sections.

5 / 5

Total

20

/

20

Passed

Description

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

The description is specific and distinct with strong natural trigger terms, but it omits an explicit 'when to use' clause, which the rubric caps at completeness 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when monitoring CI on a pull request, diagnosing failed checks, or rerunning flaky GitHub Actions jobs.'

Include a couple of natural synonyms users say, such as 'unblock CI' or 'fix failing checks', to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (GitHub PR CI) and several concrete actions — 'Monitor a GitHub pull request until CI is green', 'diagnose failures', and 'rerun only evidence-backed flaky GitHub Actions jobs' — with only minor coverage gaps.

4 / 5

Completeness

The 'what' is clearly stated, but the description contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Strong natural phrases users would say ('monitor a GitHub pull request', 'CI is green', 'diagnose failures', 'flaky GitHub Actions jobs'), though a few common synonyms like 'unblock CI' are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche — baby-sitting one PR's CI with evidence-backed flaky reruns — with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

16

/

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
langchain-ai/open-swe
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.