assistant-claw/atlas/skills/README.md
Vega (Atlas scaffolding) ce9f27320a Add Atlas profile under atlas/ — boss-perspective project execution radar
This adds the full Atlas (总助 Claw / 老板视角项目执行雷达) scaffolding as a
sibling profile to the existing Vega general-purpose assistant. All Atlas content
lives under atlas/ to keep the existing top-level skeleton intact.

What's included:

- atlas/IDENTITY.md, SOUL.md, USER.md, AGENTS.md, MEMORY.md, BOOTSTRAP.md,
  HEARTBEAT.md, TOOLS.md (+ zh-CN mirrors) — full OpenClaw 8-piece set
  matching the zero-cca convention
- atlas/skills/ — 6 sub-skills with frontmatter:
  claw-email-parser / claw-project-tracker / claw-people-observer /
  claw-customer-radar / claw-boss-distiller / claw-report-writer
- atlas/skills/claw-boss-distiller/ — adapter notes for nuwa-skill, 5-layer
  boss_skill seed template (23 rules across Expression DNA / Mental Models /
  Decision Heuristics / Anti-Patterns / Honest Boundaries), and a complete
  synthetic distillation demo (10 input emails -> validated 5-layer output)
- atlas/mcp-tools/email-extractor/ — Python implementation of stages 1-3
  (fetch + decode + dequote), 7 pytest tests passing, CLI: atlas-extract
- atlas/state-schemas/ — formal JSON schemas for project / person / customer
  cards with the no-employee-rating hard constraint baked in
- atlas/client-deck/ — 2-page client-facing pitch document
- autopilots/atlas-*.yaml — 5 autopilot configs (daily / weekly / monthly /
  quarterly + andon event-triggered) for a future Multica-side scheduler

Notes:

- nuwa-skill (MIT, https://github.com/alchaincyf/nuwa-skill) NOT vendored;
  fetch at deploy time via instructions in
  atlas/skills/claw-boss-distiller/upstream/README.md
- Vega-side prompts/skills/tools/autopilots/docs scaffold left untouched
- Top-level README.md updated with a brief Atlas pointer; rest preserved
2026-05-09 17:00:29 +08:00

47 lines
2.3 KiB
Markdown

# 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).