Web Artifacts Builder

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — None to install this skill — no account, no key, no payment, and its scripts are not run at install time. To USE it I need Node.js 18 or later on my machine, and I should know that its init and bundle scripts, only when I ask to build an artifact, download public packages from the npm registry (installing pnpm globally first if it is missing) and create project files locally. No credentials are involved. Install "Web Artifacts Builder" for me. It builds complex claude.ai HTML artifacts with React 18, TypeScript, Vite, Tailwind CSS 3.4 and shadcn/ui: first its init script scaffolds a new project (path aliases, Tailwind and PostCSS configuration, Vite version pinned for Node 18 when needed, and more than 40 shadcn/ui components unpacked from the tarball bundled in this folder); then the artifact is developed in that project; then its bundle script installs the bundling tools, builds with Parcel without source maps and inlines everything into a single self-contained bundle.html that can be shared as an artifact. Testing the artifact afterwards is optional and only on request. It is for artifacts that need state management, routing or shadcn components, not for simple single-file HTML. Repository: https://github.com/anthropics/skills (the skill is the whole skills/web-artifacts-builder/ folder at the pinned commit: SKILL.md, LICENSE.txt and the scripts/ folder with its component archive, 5 files in total) Pinned version: install the code at commit dbd4588f9e1033efb41dad4bef2f7947c8993d44 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/anthropics/skills into a temporary folder, check out commit dbd4588f9e1033efb41dad4bef2f7947c8993d44, and copy the skills/web-artifacts-builder/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - LICENSE.txt: SHA-256 bc6b3af2f331cbc7fb0da1344efb2cbe5877a31498b4d70dbc7000f3405a1362 - SKILL.md: SHA-256 81c5002c6643b0de7b8710b00e7a9038daa6fb9b68d59870ee6adb12da8d10f8 - scripts/bundle-artifact.sh: SHA-256 abf0e480bf6585b56fab8526a407dfb7dc740812bddd70c636e1e8f3df5f9618 - scripts/init-artifact.sh: SHA-256 355e5dd4382aaaee91f01f1627eaeab30b2676ffa8d9b3ec328a1ae450ebccaa - scripts/shadcn-components.tar.gz: SHA-256 1296f069e825de7933de7e8ac63672495cacce3f88f2dc45554dbcddbcbca60f If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 5 files: SKILL.md, LICENSE.txt (Apache-2.0), two shell scripts under scripts/ (init-artifact.sh and bundle-artifact.sh) and the shadcn-components.tar.gz archive they unpack at use time. I read both scripts as part of this listing's review: they scaffold and bundle a local project and install public npm packages; they are copied as-is and are not run during installation. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No project is created, no package is installed and no script runs during installation. - At use time, and only when I ask to build an artifact, the scripts work on my machine: they create a project folder, may install pnpm globally if it is missing, download public dependencies from the npm registry, and produce one local HTML file. No credentials are read or sent, and nothing is deployed or hosted. - Do not run either script, do not create any project, and do not use the skill in any way during this install: using it is a separate step that only starts when I actually ask for an artifact. 3. When I say "yes, install", install it as a skill: copy the whole web-artifacts-builder folder into the agent's skills directory, in a folder named exactly "web-artifacts-builder", keeping its 5 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: web-artifacts-builder), the 5 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that using it needs Node.js 18 or later and downloads public npm packages on my machine when I build an artifact, and that no script was run during this install; using the skill is a separate step that only starts when I ask for it, and the use-time downloads disclosed above happen only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.