# Atlas

> Front door for atlas, the team knowledge-base tool. Explains what atlas is, helps create a workspace for a team or find the one you already have, and says which folder to open in Cursor. Use when someone types /atlas, asks how to get started with atlas, or wants to onboard to a team and has no atlas workspace open.

- Skill: `chauthehienp3c1/atlas` (Agent Skill)
- Install (CLI): `npx get-skill add chauthehienp3c1/atlas`
- Raw SKILL.md: https://api.skillmd.com/api/skills/chauthehienp3c1/atlas/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: chauthehienp3c1 (https://skillmd.com/u/chauthehienp3c1)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/chauthehienp3c1/atlas

---

<!-- atlas-global-skill: installed by team-atlas install.sh and refreshed by `atlas self-update`. Do not edit; changes are overwritten. -->

# atlas (front door)

This skill is installed once per machine. It does one thing: get the person from "I have heard of atlas" to "I have a team workspace open in Cursor". The real work (ingesting sources, onboarding, questions, refresh) is done by the `/atlas-*` skills that live **inside each team's workspace**, pinned to that workspace's engine version. Do not do that work here.

## Step 1: Where are we?

Look at the open folder. It is an **atlas workspace** if it contains `atlas.config.yaml` and `.atlas/engine.lock.json`.

### Inside a workspace

Read `atlas.config.yaml` (`team`, `engine_version`) and say, in a few lines: which team this is, and that the workspace has its own skills. If `atlas` is on the PATH, `atlas status` (read-only) tells them where the workspace stands and the one next thing to do. Then hand over, without doing their work:

- nothing ingested yet (`sources/manifest.yaml` lists no sources, `kb/` pages say "placeholder") -> `/atlas-ingest` with the team's code repository first, then `/atlas-onboard`
- a new member -> `/atlas-onboard`
- a question -> `/atlas-ask`
- read the orientation but unsure what to ask -> `/atlas-explore` (it acts as a curious newcomer in their role and proposes the questions this system raises)
- stale pages -> `/atlas-refresh`; a long requirement or story -> `/atlas-shape`; documents and code that disagree -> `/atlas-reconcile`

If `atlas` is on the PATH, run `atlas list`: if this workspace's engine is older than the installed one, tell the person that `atlas upgrade .` followed by a pull request brings it up to date. Do not run it yourself.
If the workspace's `/atlas-*` commands do not appear, the folder may not be the Cursor workspace root: ask them to open this exact folder.

### Not in a workspace

Say what atlas is, in three lines at most: a team keeps a knowledge base in a git repository (a **workspace**); every statement in it cites its source, so a new member can catch up on code, documents, transcripts and pull requests without being given invented facts; one workspace per team.

Then find out which of these applies, by asking, and act on only that one:

1. **The team already has a workspace.** Run `atlas list` (if `atlas` is not found, say the installer's PATH line has not been applied and show `~/.local/bin/atlas`). If their workspace is listed, give its folder. If not, ask for the repository URL and tell them to `git clone <url>`, then `atlas add <folder>` so it is remembered. Either way: **open that folder in Cursor** (File > Open Folder) and run `/atlas-onboard` there.
2. **No workspace exists for this team.** Ask for the team's display name and a short workspace name (lowercase letters, digits and hyphens, for example `<team>-atlas`), and where on disk to put it (not inside another git repository). Check that nothing sensitive is about to be ingested: if the team handles health, finance or HR data, tell them to check company policy first and to keep the workspace on the company's own git host, because ingested text is committed. Then run, with each value quoted:

   ```bash
   atlas init <name> --team "<Team display name>"
   ```

   Tell them to open the new folder in Cursor, add sources with `/atlas-ingest` (the code repository first), run `/atlas-onboard`, and push the folder to a repository their team can reach (a private one on the company's git host).
3. **Just curious.** Point at the README at https://github.com/chauthehienp3c1/team-atlas and stop.

## Rules

- Never write into `kb/`, ingest anything, or run another workspace's scripts from here.
- Never edit a workspace's engine files (`AGENTS.md`, `.cursor/skills/atlas-*`, `scripts/`, `templates/`, `.atlas/`).
- Only run `atlas init`, `atlas add`, `atlas list`, `atlas status` and `atlas --version`. Never run `atlas upgrade` or `atlas self-update` for the person; tell them the command.
- Never create a workspace inside another workspace or inside an unrelated git repository.
- One workspace per team. A second team gets a second workspace, never a copy of the engine.

