CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

childhood

Babysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.

Quality

94%

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 exceptionally tight operational skill: every clause is a concrete instruction, the workflow is phased with explicit verification gates and a repair feedback loop, and the structure is fully navigable at its short length with no external references needed. No dimension shows anchor-level weakness.

DimensionReasoningScore

Conciseness

Every line is imperative instruction with concrete parameters ("Poll pending or changing checks every 30–60 seconds", "Keep individual waits at most 60 seconds") and zero concept re-teaching or padding — every token earns its place.

5 / 5

Actionability

Fully actionable instruction-only guidance: a per-surface evidence table, exact intervals and observation windows, exact tool-call sequences ("search for an index, timeline for context, and get_observations for only the selected records"), and a precise pointer to "version-bump ... step 13".

5 / 5

Workflow Clarity

Four clearly sequenced phases (establish → verify → observe/repair → finish) with explicit validation gates ("Verify each finding before changing code"), a repair feedback loop ("After a repair ships, restart observation ... and rerun its affected user path"), and explicit finish criteria plus partial-verification handling.

5 / 5

Progressive Disclosure

At 43 lines with well-organized sections, a scannable per-surface table, and only clearly signaled one-level cross-skill links ([version-bump], [babysit]), the body needs no bundle files — none exist — and is fully navigable as-is.

5 / 5

Total

20

/

20

Passed

Description

87%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: it names concrete verification surfaces, states explicit trigger events for when to use it, and even routes users away from the sibling pre-release skill. The only gaps are the unmentioned repair capability and a few missing natural synonyms like "monitor" or "watch".

DimensionReasoningScore

Specificity

Lists several concrete actions ("Verify published packages, production behavior, installed plugins, and late CI or user reports") but omits the repair/fix capability the body covers — a minor coverage gap that matches the 'several specific actions' anchor rather than fully comprehensive.

4 / 5

Completeness

The 'what' is explicit (verify published packages, production behavior, installed plugins, late CI/user reports until the observation window is clean) and the 'when' is given as concrete trigger events ("after merge, publication, or deployment"), plus explicit routing ("use babysit for PR readiness before release").

5 / 5

Trigger Term Quality

Natural terms users would say are present ("release", "deployment", "published packages", "production", "CI", "merge") including synonyms for the release event, but common variants like "monitor", "watch", or "post-release check" are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear post-release observation niche with distinct triggers (shipped release, merge, publication, deployment) and an explicit disambiguation from the closely related pre-release skill ("use babysit for PR readiness before release"), minimizing conflict risk.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

thedotmack/claude-mem

Path

plugin/skills/childhood/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.