visualize — beautiful, on-brand HTML artifacts Agent Skill

Generate beautiful, on-brand HTML artifacts — reports, diagrams, diff reviews, slide decks, plans, recaps, dashboards.

Context cost
875.6k tokensestimated from the bundle; more than a 200k window holds
Bundle
159 of 798 fileshanded out here; the rest is at its source
Licence
MITthe author’s own terms
Last change
—v0.7.0
Servers it uses
Noneruns standalone

What it does

Generate beautiful, on-brand HTML artifacts — reports, diagrams, diff reviews, slide decks, plans, recaps, dashboards. Loads on creation intents ("create a plan", "make me an implementation plan", "generate a diagram", "build a slide deck", "draft a recap", "visualize this", "render this as HTML", "make me a status update") and exploration intents ("show me three layouts", "explore document shapes", "compare visual treatments", "explore a new design system", "compare replacement brand directions") and iteration intents ("make this beautiful", "polish this report", "make this less generic"…

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

design
Filed under

Design & Media

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md29.4 kB · preview
--- name: visualize version: 0.7.0 license: MIT user-invocable: true argument-hint: "[teach | explore | simplify | bolder | quieter | animate | polish | review | publish] [<topic-or-path>]" allowed-tools: - Bash(node $SKILL_DIR/scripts/detect.mjs*) - Bash(node $SKILL_DIR/scripts/browser-contrast.mjs*) - Bash(node $SKILL_DIR/scripts/browser-diagram.mjs*) - Bash(node $SKILL_DIR/scripts/render-mermaid.mjs*) - Bash(node $SKILL_DIR/scripts/palette.mjs*) - Bash(node $SKILL_DIR/scripts/teach.mjs*) - Bash(node $SKILL_DIR/scripts/generate-image.mjs*) - Bash(node $SKILL_DIR/scripts/record-image.mjs*) - Bash(bash $SKILL_DIR/scripts/publish.sh*) - Bash($SKILL_DIR/scripts/publish.sh*) - Bash(node */visualize/scripts/detect.mjs*) - Bash(node */visualize/scripts/browser-contrast.mjs*) - Bash(node */visualize/scripts/browser-diagram.mjs*) - Bash(node */visualize/scripts/render-mermaid.mjs*) - Bash(node */visualize/scripts/palette.mjs*) - Bash(node */visualize/scripts/teach.mjs*) - Bash(node */visualize/scripts/generate-image.mjs*) - Bash(node */visualize/scripts/record-image.mjs*) - Bash(bash */visualize/scripts/publish.sh*) - Bash(*/visualize/scripts/publish.sh*) ---
45# visualize — beautiful, on-brand HTML artifacts
46
47Generate self-contained HTML artifacts composed from templates/*/template.md contracts against the resolved visual context. The project's DESIGN.md, PRODUCT.md, and sidecar tokens.css provide the default; artifact themes below allow reference systems within the user's approved scope. Shared pattern recipes live in patterns/ and are read only when the selected template and user ask make them relevant; shell mechanics are loaded automatically only when a template declares shell: <slug>.
48
49## Design judgment
50
51Find the artifact's organizing idea before choosing its visual treatment. Look for a relationship, contrast, sequence, decision, or object in the source that the composition itself can make easier to understand. Use that idea to shape the opening, section rhythm, and any explanatory primitive. When the source has no useful spatial or structural idea, prefer a restrained reading experience over manufacturing one.
52
53Artifact mode describes how the reader consumes the information, not the aesthetic family it must use. A document can use product-native, application-like, spatial, editorial, or technical-drawing grammar when that grammar serves the source, reader, and brand. Do not equate document with editorial publishing, or canvas with diagram chrome.
54
55Visual conviction can come from composition, typography, density, spatial rhythm, imagery, interaction, or color. Do not add hues, decoration, or components merely to make an artifact feel designed. A restrained palette can carry a strong point of view when another dimension does the expressive work.
56
57Before responding to feedback, compare the observation with the artifact's reader, purpose, source, and approved brief where one exists. Distinguish an implementation defect, a design that fails its existing requirements, and evidence that a requirement or assumption has changed. The current composition is a solution, not a constraint.
58
59Make authorized corrections within the existing brief directly. If feedback implies a change to established requirements that the user has not already approved, explain the proposed change and obtain agreement before editing. When several structural or visual directions remain plausible, recommend explore artifact within its supported scope. When the direction is established, use the ordinary creation or refinement workflow. Follow that workflow's approval requirements; a small correction does not need a new exploration.
60
61Evaluate proposed fixes together against the reader's task. Do not turn every critique finding into an addition or treat a small diff as evidence that the direction is sound. Preserve decision-relevant deferred observations in existing review or task notes.
62
63## Commands
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md4,124 words
Files159
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈540
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
875,060
on trigger
The instruction body and 158 supporting files, read only when the skill fires.
4.4×
a 200k window
It does not fit in the window: loaded whole, it would need more room than the model has.
050k100k150k200k context window

875.6k tokens, estimated from the bundle at four bytes to the token — more than the whole window, so it cannot all be held at once: the model reads SKILL.md when the skill fires and the other files only as the instructions call for them. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md asks for Bash, which can write files and reach the network alike, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

The allowed-tools line of this skill’s own SKILL.md asks for Bash, which could do either, so neither is ruled out. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

The download carries 159 of the 798 files in its source folder; the list here names 159 files, 3967.1 kB on disk. Mostly text — the instructions the model reads — with 20 scripts in it that your client would run only if the instructions tell it to. The other 639 are not in the download — the first 100 are listed after these, with why.

  • SKILL.md29.4 kB
  • AUTHORING.md7.7 kB
  • NOTICES.md3.6 kB
  • bin/_import-common.mjs15.6 kB
  • design-systems/AUTHORING-FLOW.md41.2 kB
  • design-systems/AUTHORING.md42.1 kB
  • design-systems/animation-patterns.md9.4 kB

Not in the download

The first 100 are named here, those the skill reads first. Not carried is a type a skill download does not hold and over the limit is past 200 files or 4 MB a skill. Marked read: its SKILL.md or scripts name the file, so without it the skill works only in part. Take them from its source.

  • bin/jq-linux-amd64read · not carried
  • bin/jq-linux-arm64read · not carried
  • bin/jq-macos-amd64read · not carried
  • bin/jq-macos-arm64read · not carried
  • bin/jq-windows-amd64.exeread · not carried
  • fixtures/diagrams/flow-valid.mmdread · not carried
  • fixtures/diagrams/invalid-mermaid-source.mmdread · not carried
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 20 scripts beside the text, so the download is 159 files — not the whole of its source: at least 639 files are left out, and the skill reads 100 of them. The first 100 are listed under the files, with why. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# visualize — beautiful, on-brand HTML artifacts · 875.6k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/visualize-beautiful-on-brand-html-artifacts/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/visualize-beautiful-on-brand-html-artifacts" ] && { [ ! -e .claude/skills/visualize-beautiful-on-brand-html-artifacts ] || { mv .claude/skills/visualize-beautiful-on-brand-html-artifacts "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/visualize-beautiful-on-brand-html-artifacts" .claude/skills/ && echo "Installed .claude/skills/visualize-beautiful-on-brand-html-artifacts"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add display-dev/visualize-beautiful-on-brand-html-artifacts

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/visualize-beautiful-on-brand-html-artifacts/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/visualize-beautiful-on-brand-html-artifacts/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/visualize-beautiful-on-brand-html-artifacts" ] && { [ ! -e ~/.claude/skills/visualize-beautiful-on-brand-html-artifacts ] || { mv ~/.claude/skills/visualize-beautiful-on-brand-html-artifacts "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/visualize-beautiful-on-brand-html-artifacts" ~/.claude/skills/ && echo "Installed ~/.claude/skills/visualize-beautiful-on-brand-html-artifacts" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/visualize-beautiful-on-brand-html-artifacts/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as visualize in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, visualize-beautiful-on-brand-html-artifacts. Not in this download: at least 639 files of its source, 100 of them read by its SKILL.md or scripts (the list, and why). Take them from its source.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version0.7.0
Publishedno release date on file
PriceFree
Referencedisplay-dev/visualize-beautiful-on-brand-html-artifacts

Versions

v0.7.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v0.7.0
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v0.7.0 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Who wrote it

DD
display-dev

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0
Claim this skill