retrospect-external-babysitter-run
For a repository in the babysitter-users catalog, locate its babysitter processes and any committed runs (.a5c/runs/<runId>/) and perform a retrospective on a chosen run -- what went well, what failed, process suggestions, quality of effect design, breakpoint patterns -- mirroring the /babysitter:retrospect workflow but applied to an external repo. Invoke when asked to "retrospect on repo X's run", "analyze how someone else used babysitter", or "review an external babysitter run".
npx skills add a5c-ai/babysitter --skill retrospect-external-babysitter-run --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Retrospect External Babysitter Run Analyse a babysitter run that lives in an external public repository, using the same lens as the in-repo `/babysitter:retrospect` command. Produce a written retrospective with concrete suggestions for the process author (or, if the insight generalizes, for the babysitter project itself). ## When to use - User names an external repo and asks for a retrospective. - User asks "find a babysitter run to retrospect on" (combine with the `catalog-babysitter-users` skill to pick one). - User asks "how are other people using babysitter processes? What do they get wrong?". ## Prerequisites - `gh` CLI authenticated. - `docs/repo-with-babysitter-processes.md` exists (if not, run the `catalog-babysitter-users` skill first). - A workspace directory where external repos can be shallow-cloned (default: `/tmp/babysitter-retrospect/` or `.a5c/tmp/external-runs/`). ## Phase 1 -- Target selection 1. Read `docs/repo-with-babysitter-processes.md` and list Active repos with stars + description. If the user already named a repo, skip to step 3. 2. Ask the user which repo to retrospect on (use AskUserQuestion in interactive mode; if non-interactive, pick the highest-sta
- When to use
- Prerequisites
- Phase 1 -- Target selection
- Phase 2 -- Discover processes and runs
- Phase 3 -- Pick a run to retrospect
- Phase 4 -- Load the run
- Phase 5 -- Retrospective analysis
- 5.1 Outcome
- 5.2 What went well
- 5.3 What went poorly
- 5.4 Process-quality review
- 5.5 Suggestions
- Phase 6 -- Write the retrospective
- Phase 7 -- Cleanup and callbacks
mkdir -p .a5c/tmp/external-runs cd .a5c/tmp/external-runs gh repo clone <owner>/<name> -- --depth 50 --single-branch cd <name>
What does the retrospect-external-babysitter-run skill do?
For a repository in the babysitter-users catalog, locate its babysitter processes and any committed runs (.a5c/runs/<runId>/) and perform a retrospective on a chosen run -- what went well, what failed, process suggestions, quality of effect design, breakpoint patterns -- mirroring the /babysitter:retrospect workflow but applied to an external repo. Invoke when asked to "retrospect on repo X's run", "analyze how someone else used babysitter", or "review an external babysitter run".
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill retrospect-external-babysitter-run --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.