
Export Standalone
- 39 installs
- 98 repo stars
- Updated April 20, 2026
- bluzir/claude-code-design
Export-standalone is a Claude Code skill that bundles an HTML artifact into a single self-contained offline file using the monolith CLI.
About
Export-standalone inlines all of an HTML artifact's CSS, JS, and images into a single self-contained file using the monolith CLI. The result works offline and can be dropped in email or chat, at the cost of a larger file. A developer runs it to produce a portable, dependency-free deliverable.
- Bundles an HTML artifact into one self-contained offline file with monolith
- Uses --isolate CSP and --no-metadata to block remote loads and strip metadata
- Preserves interactivity (React + Babel still run) while network fetches fail by design
Export Standalone by the numbers
- 39 all-time installs (skills.sh)
- Ranked #394 of 688 Office & Documents skills by installs in the Skillselion catalog
- Data as of Aug 1, 2026 (Skillselion catalog sync)
export-standalone capabilities & compatibility
Free; requires the monolith CLI (brew install monolith)
- Capabilities
- export pdf · export pptx · make deck
- Platforms
- macOS
- Pricing
- Free
What export-standalone says it does
Bundle an HTML artifact into a single self-contained file with all CSS/JS/images inlined as data URLs. Requires `monolith` CLI (brew install monolith).
Interactivity preserved (React + Babel still run at load time), but network fetches fail by design
npx skills add https://github.com/bluzir/claude-code-design --skill export-standaloneAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 39 |
|---|---|
| repo stars | ★ 98 |
| Last updated | April 20, 2026 |
| Repository | bluzir/claude-code-design ↗ |
What it does
Bundle an HTML artifact into one offline file with everything inlined so it can be shared over email or chat.
Who is it for?
Skip if: Keeping small file size or HMR (bundled files are 5-10x larger, no live reload)
When should I use this skill?
when an artifact needs to be shared as one portable offline file
What you get
One self-contained HTML file that works offline with no external dependencies.
- single self-contained HTML file
By the numbers
- single-file output
- 5-10x larger than original
Files
Export Standalone
Produce a single HTML file that works offline (no external dependencies). Uses monolith — a Rust CLI that inlines everything.
Preflight
1. Bash(which monolith) — check installed. If missing:
- Tell user: "
monolithnot found. Install withbrew install monolith(macOS) and rerun." - Stop.
Steps
1. Resolve paths:
$0= input HTML (required)$1= output HTML (default:<input>-standalone.html)Bash(mkdir -p $(dirname <output>))if needed
2. Run monolith:
Bash(monolith "<input>" --isolate --no-metadata -o "<output>")Flags:
--isolate— CSP to prevent any remote resource loads after bundling--no-metadata— strip<!-- saved from ... -->metadata
3. Report:
Bash(stat -f%z "<output>")orBash(ls -la "<output>")for size- "Bundled
<input>→<output>(<size>KB). Works offline."
Tradeoffs
- Pros: single file, drop in email/chat, no CDN dependency, survives archive
- Cons: larger file size (5-10× original), no HMR, fonts often inlined as base64 (bigger)
- Interactivity preserved (React + Babel still run at load time), but network fetches fail by design