agentsclimarketplace

Web artifacts builder

Skill rauleburro/skills/skills/web-artifacts-builder

Personal collection of agent skills for Claude Code and the open agent skills ecosystem (skills.sh)

Install
npx -y skills add rauleburro/skills --skill web-artifacts-builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Build polished, self-contained HTML artifacts with React, Tailwind CSS, and shadcn/ui using Bellbird's Warm Tech visual system by default. Use for complex artifacts with state, multiple views, or rich data presentation; not for simple static HTML.

The file declares its own license as Apache-2.0. See LICENSE.txt.. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.3 KB, 673 tokens by cl100k_base, as published. Nobody here has run it

Bellbird Web Artifacts Builder

This is a Bellbird-customized derivative of Anthropic's web-artifacts-builder skill. The original source and Apache 2.0 license are retained in this directory; see UPSTREAM.md.

Workflow

  1. Initialize a React artifact with scripts/init-artifact.sh <project-name>.
  2. Build the artifact using the Bellbird Warm Tech system below.
  3. Run pnpm build and bundle it with scripts/bundle-artifact.sh.
  4. Share the resulting bundle.html and visually inspect it when presentation matters.
  5. When running in Codex, open the completed artifact in the Codex in-app browser and keep that tab available for the user. If the browser blocks direct file:// navigation, do not bypass the policy: clearly report the limitation and provide the artifact link/path instead.

Bellbird Warm Tech System (default)

Use this visual system unless the user explicitly requests another brand.

Palette

  • Navy #08375A — dominant brand color; use for headers, high-impact panels, and formal milestones.
  • Teal #188BA1 — accent only; use for CTAs, key labels, icons, arrows, and focus states.
  • Warm Gray #787472 — secondary text, annotations, metadata, and technical detail.
  • Arena #ECE5DE — primary page background and light editorial panels.
  • White — readable content surfaces when separation is required.

Typography and layout

  • Use an offline system serif stack (Georgia, Times New Roman, serif) for display titles and key statements; it approximates Cormorant Garamond without external font requests.
  • Use an offline system sans-serif stack (Arial, Helvetica, system UI) for body text, data, code, and controls; it keeps dense information legible.
  • Make titles editorial and spacious, but keep body copy compact and readable. Use a mono stack only for paths, IDs, commands, and technical metadata.
  • Prefer Arena backgrounds for roughly 70% of explanatory content and Navy panels for the remaining high-impact sections, warnings, conclusions, or milestones.
  • Use square-to-soft corners (4–8px), restrained shadows, strong alignment, and generous whitespace. Avoid gradients, centered-card dashboards, excessive pills, and generic SaaS styling.

Contrast and accessibility

  • Use Navy text on Arena/white surfaces; use Arena/white text on Navy surfaces.
  • Never use Warm Gray as primary body text on Navy. Reserve Teal on Navy for large labels, icons, or clearly contrasted CTAs.
  • Keep data/code on clean solid backgrounds. Do not place thin text over textured or image backgrounds unless a solid backing panel exists.
  • Provide visible focus states and semantic controls. Do not rely on color alone for status; pair it with text or iconography.

Bundle requirements

  • Artifacts must work without external fonts, image CDNs, or runtime UI dependencies after bundle.html is generated.
  • Keep all interactive behavior client-side unless a user explicitly requests an integration.
  • Before delivery, run pnpm build; then bundle to one bundle.html using the provided script.

Gives 1 of the 12 instructions most css styling skills give in 673 tokens

Counted across 586 of the 596 authors here whose files we hold, read 2026-08-06

  • avoid excessive centered layoutsin 55 of 586, across 12 files
  • bundle code into single HTML filehere, and in 54 of 586, across 14 files
  • Respect prefers-reduced-motion user settingsin 52 of 586, across 35 files
  • avoid purple gradientsin 51 of 586, across 11 files
  • avoid uniform rounded cornersin 51 of 586, across 11 files
  • avoid Inter fontin 51 of 586, across 11 files
  • edit generated files to develop artifactin 50 of 586, across 10 files
  • animate only transform and opacity propertiesin 43 of 586
  • Make touch targets at least 44x44 pixelsin 41 of 586, across 15 files
  • Ensure minimum color contrast of 4.5:1in 39 of 586, across 10 files
  • use tailwind cssin 39 of 586, across 24 files
  • Use SVG icons instead of emojisin 38 of 586, across 11 files

Said here and by no other author read

  • Initialize artifact using provided script
  • Use offline system font stacks only
  • Use Warm Tech palette by default
  • Keep approximately seventy percent background Arena
  • Run pnpm build before bundling
  • Provide visible focus states and semantic controls

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.