html-confirm

Generates self-contained HTML decision pages for visual approvals and report reviews.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/joydai2026-del/skills --skill html-confirm-joydai2026-del
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: html-confirm
Source: https://github.com/joydai2026-del/skills/tree/main/html-confirm
Command: npx skills add https://github.com/joydai2026-del/skills --skill html-confirm-joydai2026-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a decision-maker must look at images, designs, storyboards, renders, or a report to decide, plain chat is not enough, yet building a page for every small choice creates friction. This Skill draws the line between HTML pages and chat, and produces a single openable HTML file that captures the decision and returns the answers reliably. ## Core Features & Use Cases - Surface selection rule: Decides between an HTML page and plain chat based on whether the decision requires looking at a visual artifact or reacting to a report. - Self-contained decision page: Produces one UTF-8, CJK-safe HTML file with inline styles, the decision stated up top, options with tradeoffs, a marked recommendation, and embedded visuals. - Reliable answer capture: Writes exports into a selectable textarea, avoids sandboxed iframes that break localStorage and downloads, and falls back to a short lettered chat list when the page cannot be opened. - Use Case: You generated three cover design variants and need the owner to pick one. The Skill builds <project>/docs/cover-confirm.html showing all three side by side with a marked recommendation, opens it locally, and waits for the reply. ## Quick Start Ask the agent to make a confirm page comparing the design options so you can pick one.

Frequently Asked Questions about html-confirm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an HTML approval page for design options?▼

Build one self-contained HTML file that states the decision up top, shows the options side by side with one-line tradeoffs, and marks a recommendation. Save it to the project docs folder and open it locally so the reviewer can reply with a letter or tweak notes.

When should I use an HTML page instead of chat for confirmations?▼

Use an HTML page when the decision-maker must look at an image, design, render, or report to decide, or when per-item notes span many rows. Use chat for a few text options, yes/no gates, scoping questions, or one-line clarifications.

Can the HTML confirm page use React, Vue, or Tailwind?▼

No. The page must be a single self-contained file with inline styles only, no React, Vue, or Tailwind. It must be UTF-8 and CJK-safe, reference local images by relative path, or base64-embed them when portability is required.

Why do answers from an HTML review page get lost?▼

Answers are lost when the page runs in a sandboxed iframe, which breaks localStorage, downloads, and the clipboard. Serve a local file opened directly, and write the export into a selectable textarea so a blocked download still yields the text.

What happens if the HTML confirm page cannot be opened?▼

Do not re-send the same page. Put the decision in chat as a short lettered list answerable in three lines, and ask whether a different format such as PDF or plain text works better for that device.