gantry: Skill for Claude Code

Adding a v2 Action — Gantry Server

1. The dispatch model

v2 consolidates the game's tools into a handful of namespaced MCP tools — spacemolt (default/core gameplay), spacemolt_market, spacemolt_catalog, spacemolt_storage, spacemolt_battle, spacemolt_salvage, spacemolt_ship, spacemolt_social, spacemolt_facility, spacemolt_faction, spacemolt_auth (login/logout only, intercepted separately) — instead of 60+ individually named v1 tools. Each namespaced tool takes an action string param (or, for spacemolt_catalog, a type param) that selects the behavior: spacemolt(action="jump", id="sirius"), spacemolt_storage(action="deposit", item_id="iron_ore", qty=10).

Stale doc warning: AGENTS.md says "6 namespaces." The actual v1→v2 alias table (V1_TO_V2_DISPATCH in server/src/proxy/dispatch-v1-to-v2.ts) covers 9 distinct spacemolt_* tool names, and the live namespace count isn't fixed by gantry code at all — createGantryServerV2() registers whatever tool names the live game server advertises (shared.v2Tools, fetched per-preset in schema.ts). Don't cite a namespace count — grep V1_TO_V2_DISPATCH, or check the running server's GET /health (tools_v2 count, v2_presets list) for the live figures.

Most namespaced tools' action param is a bare string with no enum — withPrayerScriptSchema() in gantry-v2.ts notes this explicitly for spacemolt: "client-side Zod accepts any string... proxy actions validate without enum injection." That means adding a new action usually requires zero schema changes, just a dispatch branch. The one namespace that does enum-constrain its dispatch key is spacemolt_catalog (type has a real enum) — see §5.

2. Which of three categories are you adding?

A. Proxy-computed helper action (no game-server round trip). The action is answered entirely from gantry's own state (SQLite, in-memory caches, computed from existing data) — e.g. find_local_route, find_item_market, recent_snapshot, snapshot_coverage, craft_chains, arbitrage_routes. This is the pattern demonstrated by the canonical example commit — see §3. You add an if (action === "your_action") { ... return textResult(...); } branch inside the big per-tool dispatch chain in createGantryServerV2() (server/src/proxy/gantry-v2.ts).