sn-ppt-workbench

Start or reuse the AI PPT editing WebUI for an existing HTML slide deck. The helper prefers Hermes/canvas/port-forward URLs when available. Without a forwarded URL, native hosts bind to localhost by default, while Docker/WSL bind to 0.0.0.0 so remote users can reach the WebUI through the host network.

Use Cases

• The user already generated a deck and asks to open the WebUI/editor/workbench.
• The user provides a deck_dir containing task_pack.json, slides/slide_NN.html, pages/page_NNN.html, or a root-level HTML deck.
• The user says to inspect or edit previously generated slides without regenerating them.

Hard Rules

1. Do not run sn-ppt-entry, sn-ppt-standard, page-html, batch-page-html, or export.
2. Do not edit slide files directly. The WebUI handles user-visible editing.
3. If deck_dir is missing, auto-detect only under $(pwd)/ppt_decks. Other roots are considered only when the caller explicitly passes --search-root; never scan home folders by default.
4. If no usable deck is found, ask the user for the absolute deck_dir.
5. Workbench startup is best-effort. If it skips or fails, report the reason and do not attempt generation as a fallback.
6. Prefer a forwarded/canvas URL over localhost when the user may be on SSH, IM, or another remote device.
7. When launched from the unified PPT flow, use the exact absolute task_pack.deck_dir; opening the Workbench must not create or switch tasks.
8. Treat task_pack.json as progress/resume state and outline.md as the user-editable Story. Existing runtime builds may expose only part of these artifacts; report compatibility gaps instead of regenerating the deck.

Invocation

Use the helper directly:

python3 $SKILL_DIR/scripts/open_workbench.py --deck-dir "<deck_dir>" --agent-session-id "${HERMES_SESSION_KEY:-}"

On native Windows where python3 is unavailable: