fvtt-mcp-molten5e: Skill for Claude Code

Table builder

The judgment + content layer for roll tables (design.md §5) — the random-generation backbone of an adventure: what wanders out of the woods, what's in the hoard, what the tavern is whispering about. As with every authoring skill: you decide; the tool does.

The line that matters — yours vs the tool's

• You (this skill) decide the CONTENTS — which entries are on the table, their relative weights, the theme, the flavor text (rumor wording, names, weather). That judgment IS the job.
• The tool only STRUCTURES — it renders each entry into the correct v14 TableResult (the description field), auto-assigns roll ranges from weights, defaults the formula to 1d<total weight>, and validates + renders real document links (@UUID). It never decides what's on the table and never invents an item.

Authoring policy — what compendium-first means HERE

Read _shared/authoring-policy.md (2024 · compendium-first · never SRD · ask-don't-invent). Two table-specific clarifications:

• Compendium-first governs the game CONTENT a result REFERENCES — the monster that ambushes, the magic item in the hoard, the spell a wild-magic surge mimics. Reference the real compendium entry by uuid (mix-and-match) so the table links the actual document with correct stats + art; never transcribe or invent its stats into the result text. This is exactly how the published DMG loot tables are built (each entry is an @UUID link to a real item).
• It does NOT constrain the flavor text you author — rumor wording, tavern names, weather, a hook's phrasing are yours to write. But don't fabricate game facts (a made-up item, a non-existent monster). If the user wants a loot table of items that aren't in the books → STOP and ASK (or offer the closest real items).

Tools

• create-rolltable — the structuring creator (your main tool). { name, results[], formula?, replacement?, displayRoll?, folderName?, description? }. Ranges auto-assign from weights and the formula defaults to 1d<total weight> unless you pass explicit ones.
• import-rolltable — copy a whole published table from a compendium into the world ({ packId, itemId, folderName? }). Roll tables are world-only at roll time, so a DMG treasure / magic-item table must be imported before you can roll it; its results (and their @UUID item links) come along intact. Premium-book packs only. This is the table version of import-item — prefer it over hand-rebuilding a book table.
• update-rolltable — change table fields and/or edit entries, two ways. To fix ONE entry (a typo, a re-link, a weight), use editResults — target it by roll (the die face, e.g. 7 on a d12) or resultId (from get-rolltable) and patch just its text/uuid/weight/range; the other entries — their ranges and @UUID item links — are left untouched. text REPLACES that entry's content: copy the raw text from get-rolltable, change only what you need, and keep any @UUID[...] enrichers you want preserved. Supplying results instead replaces the entire set (deletes + recreates all entries with fresh ranges) — right for a full re-theme, wrong for a typo.
• roll-on-table — preview a draw on a world table (evaluates without marking drawn / posting to chat). A drawn loot entry's @UUID items come back as importable (uuid + label) so you can pull them into the world with import-item (see physical-item-builder).
• list-rolltables — find tables + their ids (needed to target updates/deletes/rolls).
• delete-rolltable — remove tables by exact id/name (strict, no fuzzy match).