History

Atlas refactor bd0be97630 Refactor: drop Vega framing, promote Atlas to repo root This repo IS Atlas (总助 Claw / 老板视角项目执行雷达). The earlier two-profile framing (Atlas + Vega placeholder) was a misread — Vega is the agent persona answering Multica issues, not the product. Vega has no relationship to assistant-claw the product. Changes: - Move atlas/* to top-level (git mv preserves history) - Remove empty Vega placeholders prompts/.gitkeep, tools/.gitkeep - Delete atlas/ wrapper directory (now empty) - Update path references in INTEGRATION-hermes.md, scripts/mirror-...sh, docs/decisions/0001-mirror-nuwa-skill.md - Rewrite README.md as Atlas-only, remove dual-profile language After this commit: - Top-level OpenClaw 8 files (IDENTITY/SOUL/USER/AGENTS/TOOLS/MEMORY/ BOOTSTRAP/HEARTBEAT + CLAUDE symlink + zh-CN mirrors) - skills/{6 sub-skills + DESCRIPTION + README} - mcp-tools/{spec + Python implementation} - state-schemas/{project, person, customer + README} - autopilots/{5 atlas-*.yaml} - client-deck/, docs/decisions/, scripts/ The ~/.hermes/skills/atlas/ destination convention preserved (atlas as a skill namespace on the operator's machine, distinct from source path).		2026-05-09 17:54:18 +08:00
..
claw-boss-distiller	Refactor: drop Vega framing, promote Atlas to repo root	2026-05-09 17:54:18 +08:00
claw-customer-radar	Refactor: drop Vega framing, promote Atlas to repo root	2026-05-09 17:54:18 +08:00
claw-email-parser	Refactor: drop Vega framing, promote Atlas to repo root	2026-05-09 17:54:18 +08:00
claw-people-observer	Refactor: drop Vega framing, promote Atlas to repo root	2026-05-09 17:54:18 +08:00
claw-project-tracker	Refactor: drop Vega framing, promote Atlas to repo root	2026-05-09 17:54:18 +08:00
claw-report-writer	Refactor: drop Vega framing, promote Atlas to repo root	2026-05-09 17:54:18 +08:00
DESCRIPTION.md	Refactor: drop Vega framing, promote Atlas to repo root	2026-05-09 17:54:18 +08:00
README.md	Refactor: drop Vega framing, promote Atlas to repo root	2026-05-09 17:54:18 +08:00

README.md

Atlas Skills Roster

Atlas is one Agent operating six sub-skills. Each skill is a focused module that takes structured input from the previous stage and produces structured output for the next.

[email-extractor]
        ↓
   canonical Email JSON
        ↓
[claw-project-tracker] ──→ projects/*.json
        ↓                       ↓
[claw-people-observer] ──→ people/*.json
        ↓                       ↓
[claw-customer-radar] ──→ customers/*.json
        ↓                       ↓
        └─────→ [claw-report-writer] ──→ runs/YYYY-MM-DD.json + Brief
                       ↑
              [claw-boss-distiller] ──→ boss_skill.md (quarterly)

Skill List

Skill	Owns	Reads	Writes
`claw-email-parser`	email extraction (delegates to `email-extractor` MCP tool)	raw MIME	canonical Email JSON
`claw-project-tracker`	project state	Email JSON	`state/projects/*.json`
`claw-people-observer`	people observation (no rating!)	Email JSON + project state	`state/people/*.json`
`claw-customer-radar`	customer health	Email JSON + project state	`state/customers/*.json`
`claw-boss-distiller`	mental model distillation	boss outgoing email corpus	`boss_skill.md` (drafts; boss confirms)
`claw-report-writer`	brief / rollup / monthly rendering	all state	`state/runs/*.json` + rendered Brief

Skill Contract Discipline

Every skill has its own SKILL.md with: purpose, inputs, outputs, judgment rules, failure modes, and a 5-row sample I/O.
Skills do not share state via in-memory variables; they communicate only through state/.
Skills can be tested in isolation by feeding canned input.
Skills cite rules: every output that contains a judgment includes a rule_refs field.

Why split into 6 instead of 1 monolithic skill

Each skill stays small (< 500 lines of prompt) — better LLM accuracy per task
Independent iteration — can update claw-customer-radar without touching others
Independent eval — each skill has its own gold-standard test set
Customer-perceived "AI team" — boss sees Project Manager, People Observer, Customer Radar, Boss Distiller, Report Writer working together

See ../AGENTS.md for orchestration order under each entry point (A/B/C/D/E).