save-as-standalone-html
Skill9 starsChanged 6 months agoMITView on GitHub
Single self-contained file that works offline
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- canvas-syncSkill
- cuj-guardianSkill
- frontend-designSkill
- grill-meSkill
- pr-evidenceSkill
- semantic-commitSkill
- ship-taskSkill
- verify-with-playwrightSkill
- animated-videoSkill
- create-design-systemSkill
- design-aesthetic-presetsSkill
- design-critiqueSkill
- design-md-authorSkill
- exportSkill
- frontend-designSkill
- handoff-to-claude-codeSkill
- interactive-prototypeSkill
- make-tweakableSkill
- send-to-canvaSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Don't bundle work that's still actively being iterated on — the standalone is for handoff/share, not for in-progress.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Save as standalone HTML
⚠️ STUB — this is a working theory of the skill body. The wrapped tool (
super_inline_html) gives the contract.
What it does
Bundles an HTML file and all its referenced assets (images, CSS, JS, fonts, ext-resource-dependency meta tags) into a single self-contained HTML file that works offline. Runs a deterministic browser-side bundler.
Required input
The source HTML must contain a <template id="__bundler_thumbnail"> with a simple, colorful, iconographic SVG preview (30% padding on each side). This is shown:
- as a splash while the bundle unpacks, and
- as the no-JS fallback.
A simple icon, glyph, or 1–2 letters is enough.
Workflow
- Open the source HTML, confirm it loads cleanly.
- Inject the
<template id="__bundler_thumbnail">if it's not there. Keep it minimal. - Call
super_inline_html({ input_path, output_path }). - Open the output to verify it renders standalone.
- Offer the bundled file via
present_fs_item_for_download.
Notes
- Don't bundle work that's still actively being iterated on — the standalone is for handoff/share, not for in-progress.
- The bundler is deterministic; same input → same output.
TODO
- Replace this with the real skill body once captured.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

