ce9f27320a
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
38 lines
1.7 KiB
Markdown
38 lines
1.7 KiB
Markdown
# MCP Tools Inventory
|
|
|
|
Atlas's hands. Skills are the brain; MCP tools (and CLI commands) are how the brain reaches the world.
|
|
|
|
| Tool | Status | Spec |
|
|
|------|--------|------|
|
|
| **email-fetch** | V0 | (in `email-extractor.md` Stage 1) |
|
|
| **email-extractor** | V0 — critical | [`email-extractor.md`](./email-extractor.md) |
|
|
| **state-io** | V0 | TBD — read/write `state/*.json` with optimistic locking |
|
|
| **report-render** | V0 | TBD — Markdown → PDF / HTML / WeChat-card |
|
|
| **email-send** | V0 (boss only) | TBD — sends Brief to boss only; refuses any other recipient in V0 |
|
|
| **rule-audit** | V0 | TBD — append-only audit log of which rules fired on which judgments |
|
|
| **wechat-fetch** | V0.5 | TBD |
|
|
| **feishu-fetch** | V1 | TBD |
|
|
|
|
## Why MCP and not just plain CLI
|
|
|
|
For V0, plain Python CLI tools are fine. We move to MCP-server style when:
|
|
|
|
1. The same tool needs to be callable by multiple Claws (e.g., Atlas + Zero both want to read state)
|
|
2. We want fine-grained per-tool permission gates
|
|
3. We deploy Atlas as a hosted multi-client SaaS
|
|
|
|
For now: **CLI commands callable from skill prompts via Bash** is the V0 model. MCP wrapping is a V0.5 refactor.
|
|
|
|
## Tool Authorization Matrix
|
|
|
|
| Tool | Can Atlas call autonomously? | Requires boss approval? |
|
|
|------|-----------------------------|--------------------------|
|
|
| email-fetch | ✅ | No (configured at install) |
|
|
| email-extractor | ✅ | No |
|
|
| state-io read | ✅ | No |
|
|
| state-io write | ✅ | No (state is Atlas's working memory) |
|
|
| report-render | ✅ | No |
|
|
| email-send (Brief to boss) | ✅ | No (auth granted at install) |
|
|
| email-send (anything else) | ❌ in V0 | Always |
|
|
| boss_skill.md write | ❌ in V0 | Always — boss audits diff |
|