fvtt-mcp-molten5e: Skill for Claude Code

Tom Cartos import

A judgment layer over read-pack + the scene/journal/asset tools that turns a Tom-Cartos-style scene-pack module — a module.json plus LevelDB/NeDB compendiums holding fully-authored scenes (thousands of walls, hundreds of configured lights, a journal of numbered legend keys) — into real scenes in the user's own world, without enabling the module as a permanent dependency.

Strategy is extract-and-recreate, not install-as-module: Molten's hosting blocks flipping a module's enable-flag and the bridge has no enable-module driver, so "drop the folder and enable it" dead-ends. We read the pack off disk, upload its images, and recreate the documents through the tools. See docs/tom-cartos-import-plan.md for the full design.

Tools used: read-pack (the off-line extractor/detector — owns all the LevelDB/NeDB reading, era detection, tile discovery, and asset path-rewrite math), upload-asset / upload-asset-tree (Plane B — single file vs whole subtree), create-scene, remap-teleporters (the second-pass teleporter fixer), create-journal / add-journal-image, create-folder / move-documents, list-scenes / list-journals. To boot the world first, hand off to start-session.

🎯 OWNER DEFAULT — MAPS ONLY (directed 2026-07-08): the owner repurposes pack maps into his own setting (e.g. Ostenwold → Greenrest), so an import delivers pre-made scenes with their walls, doors, lights, and mood — nothing else. SKIP Step 5 (pack journals), scene→journal links, and the legend→map-pins pass entirely unless the owner explicitly asks for them that session — the pack's lore/names must not enter the world. Teleporters (when a pack ships regions) and tiles remain in scope; folder/naming follow the owner's campaign convention (his chapter folders, his scene names), not the pack's. Stamp every imported town/social map with flags["fvtt-mod-autoexplore"].enabled: true (pass it in create-scene's flags alongside the provenance flag) — the house autoexplore module renders the scene born-explored (architecture through fog, tokens still LOS-gated); the GM can untick it per scene in the Custom tab.

Scope — all eras: this skill imports modern (v13/LevelDB), mid (v10–v11), and legacy (≤v9 / NeDB .db) packs. read-pack detects the era and normalizes the on-disk shape for you: a modern pack's split walls / config{} lights / environment{} mood and cross-scene teleporters (the stairs/portals), or a legacy pack's sense walls, flat torch lights, flat grid/mood, and img background. type:"Adventure" packs are in scope too — the modern premium format (e.g. tomcartos-ostenwold 2.x) ships ONE Adventure compendium whose Adventure doc(s) EMBED every scene/journal; read-pack harvests them into the same streams, stamps each scene with its adventure name (a pack can hold several — Ostenwold ships "Ostenwold" + "Ostenwold in Winter", with IDENTICAL scene names across them, so select by sourceId, never by name), dedupes the journal docs the adventures share, and resolves a v14 pack's background from its LEVEL (levels[initialLevel].background.src — v14 has no top-level Scene.background). The legend→map-pins feature (below) now runs BY DEFAULT whenever a per-map legend key is present (place the pins, then tell the user). Never reconstruct a wall, light, or region field-by-field — read-pack hands them back whole; pass them through whole (the dropped-sight/blown-out-lights trap).