Chat: Taos Skills And Mcp Plan (Taos Tooling)

**Chat log** from Bead: Taos Tooling · [canonical source](https://redfish.acequia.io/guerin/.agents/221f3fe2-f3ef-43e3-994d-c67f69d3da47/2026-06-10/chats/2026-06-10-taos-skills-and-mcp-plan.md) · session 2026-06-10 · discussion: Talk: Taos Tooling *Verbatim chat log: immutable provenance. The bead's copy is ground truth; wiki edits here are a fork, never the record.*

**Bead:** `221f3fe2-f3ef-43e3-994d-c67f69d3da47` (`taos-tooling`) · **Date:** 2026-06-10 **Modality:** CE (Claude Code extension — writer). Incremental log.

**Injected context (turn 1):** IDE had `#main-context` `about.md` (`c38c1239`) open. **User (verbatim):** > start-bead then make a plan to make skills and mcp for taos-engine > > info and skills in peer beed called #taos-engine. you're in the same directory **User (verbatim, mid-turn):** > read redfish.acequia.io\skills **Assistant (summary):** - Read the bead protocol (`.agents/beads.md`) and surveyed existing beads (27 `about.md`s). Identified the opened bead as `#main-context` and the peer source bead as `#taos-engine` (`c66cbd1d`). - Read `#taos-engine`: `about.md`, the build plan (`taos-misb-build-plan.md` incl. the 2026-06-10 API-confirmation pass), and step-0 README. Captured the confirmed API: `Engine.create`, `GeoScene`, `addRasterDemTerrain`/`add3DTiles`/`addVectorTiles`, `Projector` (`source:{kind:'video',…}`, `focalLength`/`fovY`/`aspect`/`crop`/`blend`), `FlyControls`, ECEF frame helpers, and the MISB-FOV intrinsics mapping. - Read `redfish.acequia.io/skills/` per the second prompt: `substrate-spine.md`, `beads/SKILL.md`, `webdav-context/SKILL.md` — established the substrate SKILL.md format and the "skill = catalyst / autocatalytic set" frame. - Grounded against the **real clone** at `c:/Users/steph/Documents/src/taos-engine`: `docs/api-guide.md`, `docs/modules/{core,geo,terrain,physics,audio,sdf}.md`, generated typedoc API ref, 67 `samples/*.ts`, real `src/geo/` + `src/renderer/features/projector_feature.ts`, and existing `server/` (WS) + `editor/` subprojects (candidate MCP transports). - **Started this bead** (`taos-tooling`, GUID `221f3fe2…`), birth-parent `#main-context`, reading from `#taos-engine`. Scaffolded `about.md` + this chat log. - Wrote the deliverable: [2026-06-10/notes/taos-skills-and-mcp-plan.md](https://redfish.acequia.io/guerin/.agents/221f3fe2-f3ef-43e3-994d-c67f69d3da47/2026-06-10/notes/taos-skills-and-mcp-plan.md) — five skills (A1 bootstrap, A2 geo-scene, A3 projector, A4 camera-control, A5 verify-webgpu) + a two-phase MCP (B1 `taos-api` source/knowledge server kills `#taos-engine` Q6; B2 `taos-scene` live cataloging interface, CDP→WebDAV-catalog), with sequencing and four decisions for Stephen. - No skill/MCP code written — plan only, per the ask. Held at the four §5 decisions.

**User (verbatim):** > give me a url reference to the skills and mcp **Assistant (summary):** Gave the canonical URIs the plan assigns each deliverable (bead-draft skill paths + promoted `/skills/` paths; MCP artifact paths). Flagged they only resolve after sync. **User (verbatim):** > yes bead-sync. then what is the best url to point a denovo agent to that wants to build someting with taos-engine **Assistant (summary):** First sync of this fresh bead — PROPFIND 404 → MKCOL root (201) → webdav-sync (3 files, 200s). Answered the denovo-agent question: today → `#taos-engine` about.md (richest existing entry, has working step-0); by design → the A1 `taos-engine-bootstrap` skill (its whole job is that cold-start URL), then unbuilt. Noted the gap: building A1 is what makes that URL real. **User (verbatim):** > create skills and mcp for taos-engine in the bead and sync. **Assistant (summary):** Built all five skills + the B1 MCP. Discovered the clone had moved (`Downloads/TaosEngine-src` → `Documents/src/taos-engine`); re-pulled authoritative API from real source (`docs/api-guide.md`, `docs/modules/geo.md`, `src/engine/components/projector.ts`, `src/renderer/projector_source.ts`, `samples/projector_test.ts`, `samples/geo_osm_buildings.ts`). **Corrections vs the reverse-engineered build plan:** control class is `CameraController` (not `FlyControls`); `lookRotation` is sample-local (port it); confirmed the full `Projector` property surface and `addRasterDemTerrain(AWS_TERRARIUM,{imagery:ESRI_WORLD_IMAGERY})`. Wrote skills A1–A5 in `skills/`. Wrote the `taos-api` MCP (dep-free Node, MCP stdio JSON-RPC, 6 tools) in `artifacts/taos-api-mcp/` with a `smoke.mjs` — `node smoke.mjs` → **SMOKE PASSED** (6/6 against the clone). Fixed the stale clone path in the plan + chat. Updated `about.md` (built-status, capabilities, limitations). Re-synced the bead.