HTML Communication

Create a readable artifact for a human outside the terminal. This skill communicates work; it does not add HTML to the product.

Choose the right artifact

Use this skill for a plan, spec, findings, report, comparison, or static set of UI mocks. If the question requires the user to exercise behaviour, push a state model through cases, or judge UI inside the real product context, call the Skill tool with "prototype" instead.

Build one stable file

Write one self-contained HTML file with inline CSS and JavaScript and no required network dependencies. Put it in the OS temp directory unless the user asks for it in the repository. Choose a descriptive stable path for the task and overwrite that same file on revisions so the link or path does not move.

Resolve the temp directory from $TMPDIR, then /tmp on Unix-like systems or %TEMP% on Windows. Do not overwrite an unrelated existing artifact.

Write it like a document

Optimize for comprehension rather than landing-page aesthetics: