--- name: interactive-json-form description: Build a self-contained, single-file interactive HTML page (explanations + multiple-choice votes + rank + free-form comments) whose responses round-trip as downloadable/importable JSON — no backend, no tracking — and publish it privately on your own host behind noindex + an unguessable path. allowed-tools: Read, Write, Edit, Bash --- # Interactive JSON Form — decision/survey pages with a client-side JSON round-trip > **Self-Evolving Skill**: This skill improves through use. If instructions are > wrong, parameters drifted, or a workaround was needed — fix this file > immediately, don't defer. Only update for real, reproducible issues. A **single self-contained `.html` file** that presents extensive explanations, lets a small known audience (e.g. a CEO + data scientists) **pick options, rank them, and comment**, then hands their input back as a **downloadable / copyable / re-importable JSON** — with **no server, no submit endpoint, and no tracking**. Published privately on your own host behind a `noindex` header + an unguessable path, so it is reachable by whoever has the linkTelus-direct door) but blocked from crawlers/indexing. ## When to use this skill - You need a few named humans to make **structured choices + free-form comments** on a set of options, and you want their answers back as **machine-readable JSON** you ingest directly. - Mobile-friendly, re-openable (import a prior JSON to resume), zero tooling for the responder, and **no backend to stand up**. - The audience is small and known → a downloadable JSON they send you beats a hosted collector; a public form would over-expose. ## When NOT to use it - Anonymous mass surveys / thousands of respondents (use a real survey backend). - You need server-side aggregation in real time (add a collector, or use Lark Base — see `../../lark-automation` for the Base decision-harness alternative). - Multi-page sitemap sites with no JS → use the sibling **`page-template`** skill. ## Why this over Lark Base / Forms / cards (decided by research 2026-07-13) Lark Base grids truncate long text (row-height/width are NOT API-settable), Forms are read-only after submit with no create API, and cards are one-shot with a 30-day window + a callback webhook. A self-contained HTML page has **none** of those limits: full text wraps natively, edits are unlimited, and the JSON round-trip is pure client-side. The cost is that responses come back as files, not a live table — acceptable for a small known audience. ## The pattern (what makes it work) 1. **Data-driven options.** An `OPTIONS` array at the top of the inline `