← ClaudeAtlas

widget-previewlisted

Open a marvin widget as a real rendered panel with this project's own data, on any host — renders the bound ui:// widget plus its live payload into one self-contained HTML file under .marvin/preview/ and opens it in a browser. Use when the user says "show me the widget", "open the help widget", "I want to see the dashboard as a widget", "покажи виджет", "/marvin:widget-preview", or asks why a widget is not showing up in the terminal.
real-case/marvin-toolkit · ★ 0 · AI & Automation · score 68
Install: claude install-skill real-case/marvin-toolkit
# Widget Preview Render one of marvin's `ui://` widgets — with this project's live data — into a file the user can open, and open it. ## Why this exists A widget only appears when the MCP host resolves the tool's `_meta.ui.resourceUri`. The Claude Code CLI does not implement that at all, so `/marvin:help` renders its markdown fallback there and every widget in the family is unreachable from the terminal. This command does what a rich host would do — call the tool, fetch the widget document, run the handshake, hand over the payload — and leaves the result as a self-contained file (ADR-0034). Do not explain the widget's contents afterwards. The panel is the output; the user reads it. ## Input `$ARGUMENTS` — optionally the widget to open, and optionally arguments for its tool as JSON. ## Bound widgets `help`, `dashboard`, `reports`, `task-list`, `task-detail`, `task-summary`, `tracker-list`, `handoffs`, `audit`. The list is not hard-coded anywhere: running the command with an unknown name prints the widgets the installed server actually binds. Prefer that over guessing. ## Workflow ### 1. Resolve the widget Map what the user asked for to a widget name. "the help widget", "the welcome screen" → `help`; "the toolbox state", "the dashboard" → `dashboard`; "my reports" → `reports`; "the board" → `task-list`. If the request is ambiguous, ask once, offering the two closest names — do not render several. ### 2. Run the command The script ships inside the plugin. Invoke it