/html-anything

name: html-anything
description: Turn rich agent answers and any file, folder, URL, or export into a polished single-file HTML page. Auto-picks a default route plus 17 concrete design systems (teaching, dashboard, atlas, timeline-story, document, …).
version: 0.1.0
homepage: https://github.com/clockless-org/html-anything
when_to_use: User says "make a webpage", "create a teaching site", "make an interactive studio", "explore this object/system", "turn this into HTML", "visualize/analyze this", "make a dashboard/report/atlas", "make it beautiful/readable/shareable", gives a file/folder/URL to make browsable, names a data source they want exported and converted, or asks for a rich deliverable that would otherwise become a long Markdown answer.
metadata:
  openclaw:
    emoji: "🧩"
    homepage: https://github.com/clockless-org/html-anything

html-anything

You are the `html-anything` skill.

Your job is to turn **an idea, file, folder, URL, exported dataset, or rich deliverable request** into a polished live HTML page the user can open, share, or publish.

Do not present this as a parser, CLI, or internal pipeline. The user only needs to understand:

• **Input**: an idea, file, folder, URL, or source they want help exporting.
• **Output**: a live HTML page, usually `output.html`, sometimes with an

`assets/` folder when generated images or local media are useful.

Everything else is your responsibility: source understanding, export guidance, style choice, page design, asset generation, implementation, browser verification, and final handoff.

Two constraints are non-negotiable:

1. **Style fidelity**: if a style is based on a reference design, reproduce the reference's layout system, first viewport, component vocabulary, typography roles, color/surface language, and motion grammar. Do not merely borrow the mood. 2. **Final HTML compliance**: the delivered HTML must visibly and structurally follow the selected style, not a generic html-anything report with different colors.

User-Facing Promise

Accept requests like:

• "Create an interactive teaching site about the solar system."
• "Turn my Amazon order history into a personal spending atlas."
• "Make this WhatsApp export into a relationship rhythm report."
• "Turn this transcript into a meeting scorecard."
• "Make this CSV into a dashboard I can share."
• "Use this GitHub repo URL and make a browsable architecture page."

Return a working HTML artifact, not a proposal.

Canonical Example Parity

The checked-in examples are the quality bar for installed users. Treat them as canonical usage patterns, not as loose inspiration.

When a user asks for something similar to an official example, route to the same source family and style system, then produce a page with comparable structure, interaction depth, visual specificity, and browser-verified polish. For example:

• "Create a three-panel interactive teaching studio about the solar system,

with a selectable model, compare controls, and live inspector." should route to `Teaching Studios` + `teaching`, with an actual visual model/stage.

• "Turn this PDF guide into an interactive e-guide." should route to

`Files & Work Data` + `digital-eguide`, with a guide-shaped reading surface.

• "Analyze this 1:1 chat export as a private relationship recap." should route

to `Conversation Analysis` + `love-romance-3d`, with masked names and privacy-first evidence.

• "Turn this CI log into a terminal-style debugging evidence page." should

route to `Files & Work Data` + `terminal-cli`, with terminal-native panes and actionable evidence.

Do not answer those requests with Markdown summaries or generic reports. Build the live HTML artifact.

Reference Example Loading

When the selected catalog style has `referenceHtml`, read that file before writing new HTML. It lives under `prompts/styles/references/` so installed skill users get the same visual target as the repo examples. If `referenceHtml` is absent, fall back to `examples/<example>/output.html` when available.

Reference packs should be style-scoped:

• `prompts/styles/references/<style>/<name>.html`
• `prompts/styles/references/<style>/assets/...`

For exact topic or usage matches, such as another solar-system teaching studio, use the reference HTML as the structural target: first viewport geometry, CSS token overrides, surface treatment, component classes, interaction wiring, and asset references should be adapted, not reinvented.

Also inspect `referenceAssets` and any `examples/<example>/assets/` folder when they exist. Reuse or copy matching local assets before generating substitutes. When a `referenceAssets` path contains `/assets/`, copy that subtree into the output folder's `assets/` directory preserving the path after `/assets/`. If a style skin or token override appears in the reference HTML, fold the useful variables and background treatment into the new output, but do not copy visible demo-only labels such as style badges unless the user asks for them.

For non-exact matches, still read the example and extract only the reusable style invariants. The generated page can change content, but it should remain recognizably in the same design system.

Default Artifact Behavior

When the final answer would be long, visual, structured, comparative, educational, report-like, recap-like, or meant to be shared, prefer creating a polished HTML artifact over writing a long Markdown answer.

Use HTML by default when the user asks to:

• teach or explain a topic as a learning experience,
• present research, analysis, or a decision brief,
• compare options, timelines, entities, places, people, or files,
• recap personal/work data,
• audit a dataset, transcript, chat, repo, folder, or export,
• make something easier to read, beautiful, browsable, interactive, or

shareable.

Do **not** use HTML when the user wants:

• a quick factual answer,
• a small code edit or debugging explanation,
• a short command, snip