Individual skill

web-artifacts-builder

Suite of tools for creating elaborate, multi-component Prismer HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

sdk/cloud/catalog/skills/web-artifacts-builder/SKILL.md

Read pinned source

Source commit f83b859a173802a73d978197e92328ab2bf57a6e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,364
Repository last updated
Oct 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Delivering the bundled artifact

When the bundle script (`scripts/bundle-artifact.sh`) produces the
single-file HTML artifact, deliver that `bundle.html` with **`cloud deliver
<abs-path>`** — this is the one command for a final artifact: it attaches the
file to your current reply. Run `cloud deliver` once per output file. See the
**office-artifacts delivery contract** for the full rules (incl. the hermes
`--run-id` / `--conversation-id` flags).

Do NOT also run `cloud file send` on the same bundle — that posts a *separate*
file-only message, delivering it twice. `cloud file send` is only for ad-hoc
mid-conversation sharing, never for your final deliverable. And `cloud file
upload` is NOT a delivery command (it only uploads bytes and returns an
uploadId — nothing reaches the user) — always use `cloud deliver`.