SkillAgentSearch skills...

catalog-babysitter-users

Discover public GitHub repositories that import defineTask from @a5c-ai/babysitter-sdk and maintain a deduplicated catalog of those repositories in docs/repo-with-babysitter-processes.md. Excludes any repo named "babysitter" (to filter out forks of this monorepo).

Install / Use

npx skills add a5c-ai/babysitter --skill catalog-babysitter-users

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Universal

Our assessment of catalog-babysitter-users

catalog-babysitter-users scores 89/100 on our quality scale, 1619th of 4,700 Development & Engineering skills we index (top 35%).

Its SKILL.md is 5.7 KB long, well organised into 14 sections with 4 code examples: a solid amount of guidance for an agent.

With 1,809 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so catalog-babysitter-users is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

catalog-babysitter-users compared with similar skills

All 4 of these similar skills score higher than catalog-babysitter-users; compare them before choosing.

SkillScoreStarsUpdatedFormat
catalog-babysitter-users (this skill)by a5c-ai891.8k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md

Frequently asked questions

How do I install catalog-babysitter-users?
Run npx skills add a5c-ai/babysitter --skill catalog-babysitter-users. The install tabs above show the steps for each supported agent.
Which AI agents does catalog-babysitter-users work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is catalog-babysitter-users safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is catalog-babysitter-users still maintained?
The repository was last updated about 2 months ago, so catalog-babysitter-users is actively maintained.

name: catalog-babysitter-users description: Discover public GitHub repositories that import defineTask from @a5c-ai/babysitter-sdk and maintain a deduplicated catalog of those repositories in docs/repo-with-babysitter-processes.md. Excludes any repo named "babysitter" (to filter out forks of this monorepo). Invoke when asked to find, discover, catalog, or refresh "repos using babysitter", "babysitter in the wild", or "who else is using babysitter".

Catalog Babysitter Users

Produce a curated, deduplicated catalog of public GitHub repositories that import defineTask from @a5c-ai/babysitter-sdk, stored at docs/repo-with-babysitter-processes.md. Refresh the catalog in-place when re-run; do not delete entries that no longer match (mark them as "last seen" instead, so the catalog is additive over time).

When to use

  • User asks "who's using babysitter in the wild?", "find repos with babysitter processes", "refresh the catalog", "update the babysitter-users list".
  • After a release, to see whether new adopters have appeared.
  • Before a retrospective across external runs (see the sibling skill retrospect-external-babysitter-run).

Prerequisites

  • gh CLI installed and authenticated (gh auth status must be OK). GitHub code search requires an authenticated user.
  • Writable working tree (the catalog file gets updated).

Exact search

Search the literal import statement across public code:

gh search code \
  "import { defineTask } from '@a5c-ai/babysitter-sdk'" \
  --json repository,path,url \
  --limit 200

Also run the double-quote variant to catch formatter differences:

gh search code \
  'import { defineTask } from "@a5c-ai/babysitter-sdk"' \
  --json repository,path,url \
  --limit 200

Union the two result sets. If the CLI caps out at 100 per query, paginate by adding language:javascript, language:typescript, and extension:js, extension:ts qualifiers to split the search space.

Filtering rules (apply in order)

  1. Drop any hit whose repository.name (case-insensitive) equals babysitter. This excludes forks of this monorepo.
  2. Drop any hit whose repository.nameWithOwner starts with a5c-ai/ -- those are first-party and already known.
  3. Drop archived repos (repository.isArchived === true). Enrich via gh api repos/<owner>/<name> if the search JSON lacks it.
  4. Dedupe by repository.nameWithOwner -- one entry per repo, even if multiple files match. Keep the count of matching files as evidence.
  5. Drop private-visible-as-public fluke hits (repository.visibility !== 'public').

Enrichment per surviving repo

For each repo, fetch:

gh api repos/<owner>/<name> \
  --jq '{nameWithOwner, description, stargazerCount: .stargazers_count, pushedAt: .pushed_at, defaultBranch: .default_branch, license: .license.spdx_id, topics}'

Also record:

  • processFiles: the list of matching file paths from the search (cap at 10 per repo in the catalog; note total count if higher).
  • firstSeen: if the repo is new to the catalog, today's date (ISO). If already present, preserve the existing value.
  • lastSeen: today's date (ISO) for every repo that matched this run.

Catalog file format

Maintain docs/repo-with-babysitter-processes.md as an additive, idempotent document. Structure:

# Repositories Using Babysitter

<!-- Generated by .claude/skills/catalog-babysitter-users. Re-run the skill to refresh. -->

Last refreshed: YYYY-MM-DD
Total repos tracked: N
New this run: M
No longer matching: K

## Active

| Repository | Stars | Description | License | Pushed | Process files | First seen | Last seen |
|------------|-------|-------------|---------|--------|---------------|------------|-----------|
| [owner/name](https://github.com/owner/name) | 123 | ... | MIT | 2026-04-01 | 3 | 2026-03-15 | 2026-04-12 |

### owner/name

- Default branch: `main`
- Topics: `a5c`, `orchestration`
- Matching files:
  - [`src/processes/build.js`](https://github.com/owner/name/blob/main/src/processes/build.js)
  - ...

## Stale (no longer matching at last refresh)

| Repository | Last seen | Notes |
|------------|-----------|-------|
| ... | ... | Import removed / repo archived / ... |

Rules when updating:

  • Preserve every existing entry's firstSeen.
  • Move a repo from Active to Stale only if it didn't match this run AND was Active last run. Include the reason if derivable (archived, 404, import removed).
  • Never delete a Stale entry; only update its lastSeen note if the situation changes (e.g. re-matched -> move back to Active).
  • Sort Active rows by stars descending, then by pushedAt descending.
  • Keep the summary counters at the top accurate.

Procedure

  1. Read the current docs/repo-with-babysitter-processes.md (if absent, treat as an empty catalog).
  2. Parse existing entries into a map keyed by nameWithOwner.
  3. Run both gh search code queries above; union results.
  4. Apply the filtering rules.
  5. Enrich each surviving repo via gh api repos/....
  6. Build the merged catalog: existing entries + new entries; move absent-this-run Active entries to Stale.
  7. Write the updated markdown file.
  8. Print a short summary to the user: N total, M new, K moved to stale, top 5 new repos by stars.

Notes on rate limits

gh search code is throttled (30 req/min for authenticated users). If the first pass returns the default cap, split by language: qualifier and by file extension: rather than spamming retries. Always include --limit 100 (max) and paginate via qualifier-splitting, not --page (code search doesn't page).

After running

Suggest the sibling skill retrospect-external-babysitter-run to go deeper on any specific entry -- "pick a repo from the catalog and retrospect on one of its runs".

Related Skills

View on GitHub
GitHub Stars1.8k
CategoryDevelopment
Updated2mo ago
Forks110

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions