atlas
Atlas turns your STATED NEED into a real systems atlas by SCANNING your actual sources (Azure via `az`, git repos, local dirs) and process/data mining them, THEN enriching against the Atlas knowledge graph. Use this skill when asked to inventory/map your real systems, scan your cloud + repos + directories, mine the real processes or data they contain, or collect their real constraints/gotchas. (atlas, scan my systems, inventory our azure account, map my repos, real systems atlas, process mining, data mining, collect nuances, system discovery)
npx skills add a5c-ai/babysitter --skill atlas --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.
# atlas This skill turns a stated need into a **real systems atlas** by SCANNING your actual sources — Azure subscriptions (via read-only `az`), git repos, and local directories — and process/data mining them, THEN enriching the result against the Atlas knowledge graph. It is the brain of the `atlas` plugin. The scan is PRIMARY; the graph is SECONDARY. For non-trivial runs it delegates orchestration to `babysitter:babysit` using an atlas-specific `.a5c` process; for simple lookups it queries the graph directly. ## 1. Scan-first, graph-second The output you want is an evidence-backed inventory of **your** systems — e.g. `azure-inventory.json` (every real resource id + RG from `az`), `workspace-inventory.json` (real repo/dir scan), `processes.json` (real mined CI/CD/IaC/.a5c processes), and a cross-linked `SYSTEMS-ATLAS.md`. Every item must cite its REAL source. Generic catalog nodes are NOT the deliverable. - **Primary — scan the user's real sources.** Use `Bash` to run READ-ONLY scans: `az` (account/group/resource list + per-service list/show) for Azure; `git` + filesystem (`Read`/`Glob`) for repos and directories. NEVER invent resource ids, regions, SKUs, or file paths — if you di
- 1. Scan-first, graph-second
- 2. When to use
- 3. The need → real atlas pipeline (core method)
- 4. How to delegate
- 5. Guardrails
What does the atlas skill do?
Atlas turns your STATED NEED into a real systems atlas by SCANNING your actual sources (Azure via `az`, git repos, local dirs) and process/data mining them, THEN enriching against the Atlas knowledge graph. Use this skill when asked to inventory/map your real systems, scan your cloud + repos + directories, mine the real processes or data they contain, or collect their real constraints/gotchas. (atlas, scan my systems, inventory our azure account, map my repos, real systems atlas, process mining, data mining, collect nuances, system discovery)
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill atlas --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.