⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
claude-artifact-cli
>-
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
claude-artifact-cli
Publish, update, pull, list and inspect Claude Artifacts from the terminal, using the Claude Code login already on your machine.
What is this?
claude-artifact publishes an HTML page (plus any CSS, JS and images it uses) as a Claude Artifact and prints the link, and pulls an artifact's files back down to edit and republish. It talks to the same API the Claude Code Artifact tool uses and reuses the claude.ai login from claude /login. No API key, no config file, no dependencies beyond Python 3.10+.
Use it where the built-in tool can't reach: other coding agents (Droid, Codex, Cursor, OpenCode), subagents, shell scripts, Makefiles, git hooks and CI jobs.
[!NOTE] Unofficial and not affiliated with Anthropic. It uses a private, undocumented API that can change or break without notice.
Quick Start
uv tool install claude-artifact-cli # or: pipx install claude-artifact-cli
claude-artifact whoami # confirms the Claude Code login works
claude-artifact publish report.html --favicon 📊
# https://claude.ai/code/artifact/1c5586a4-acec-4266-a9aa-03dfa0912b43
Run it once without installing:
uvx --from claude-artifact-cli claude-artifact publish report.html
Commands
claude-artifact publish FILE|DIR [options] publish or update an artifact
claude-artifact pull SLUG_OR_URL [DIR] [--force] [-q]
download the artifact's files into DIR
claude-artifact status [PATH] [--slug S | --url U]
compare local files with what's live
claude-artifact list [--scope mine|shared|all] [--limit N]
claude-artifact read SLUG_OR_URL [-o FILE] metadata + published file manifest
claude-artifact read SLUG_OR_URL --path P [--path P ... --out-dir DIR]
a published file's exact bytes
claude-artifact whoami check that auth works
claude-artifact update upgrade to the latest release now
claude-artifact --version
The URL goes to stdout and progress goes to stderr, so URL=$(claude-artifact publish page.html -q) captures only the link. Add --json to publish, status, list or read for raw output. Exit codes: 0 success, 1 API error, 2 auth error, 3 version conflict (HTTP 409), 130 interrupted.
Wherever a command takes a slug or URL (SLUG_OR_URL, --slug, --url), it accepts any of:
https://claude.ai/code/artifact/<uuid>https://claude.ai/artifact/<short id>, the form claude.ai and Claude Code's Artifact tool show- a bare UUID or a bare short id
publish
# new artifact; the title comes from the page's <title>
claude-artifact publish dashboard.html --favicon 📊 --description "Q3 numbers"
# update in place, same URL; published files you don't pass are kept
claude-artifact publish dashboard.html --url https://claude.ai/code/artifact/<slug>
claude-artifact publish dashboard.html --slug <slug>
# update, and make these files the whole artifact (anything else is removed)
claude-artifact publish dashboard.html --slug <slug> --mode replace --file app.css
# multi-file page
claude-artifact publish index.html \
--root ./site \
--file app.css --file app.js --file img/logo.png
# rename a file's published path, and drop one
claude-artifact publish index.html --slug <slug> \
--file styles.css=src/main.css \
--remove old.js
| Option | Meaning |
|---|---|
--slug, --url | Update this artifact. Without one, a publish creates a new artifact (a directory with .artifact.json updates its own). |
--title | Defaults to the page's <title>, else the file or directory name (for a typed directory, the title saved in .artifact.json). |
--favicon | Emoji for the tab. Set it on a first publish. |
--description | One-sentence subtitle. |
--icon, --label | Generic icon word; short name for this publish. |
--file PUB[=SRC] | Supporting file. Without =, published and source paths match. Repeatable. Not allowed with a directory. |
--root | Base directory for --file sources. Published paths are unchanged. Not allowed with a directory. |
--remove PATH | Delete a published file. Needs an existing artifact and patch mode; with no --mode, --remove uses patch. |
--mode patch|replace | patch overlays the manifest onto the base version, so published files you don't pass are kept. Default when updating a page. replace makes the manifest the whole artifact, so any published file you leave out is removed. Default for a new artifact and for the first publish of a directory. A directory with .artifact.json patches (see below). |
--base-version | The version this publish was made against. If a newer version is live, the publish is refused with exit code 3. Defaults to the version in a directory's .artifact.json (when publishing to the slug saved there). Without one, patch uses the live version and replace is not checked, so a concurrent publish goes undetected. |
--force | Publish even if a newer version is live, discarding it. |
-q, --quiet | Print only the URL. |
--json prints the deploy response with the artifact url added: {"url", "slug", "version", …}.
Publish a directory
claude-artifact publish ./site --favicon 📊 # new artifact; writes ./site/.artifact.json
claude-artifact publish ./site # later: updates the same artifact
Publishes every file under the directory, recursively, skipping dotfiles and dot-directories. index.html is required at the top level (except for a typed artifact, below); symlinks are refused. The first publish of a directory replaces: the directory is the whole artifact. Once .artifact.json lists its files, publish DIR patches: it sends the directory's files and removes the ones deleted locally since the last pull or publish, leaving files the directory never held (dot paths, a type's files) alone. --mode replace forces a full replace.
After each successful publish (and each pull) the CLI writes DIR/.artifact.json:
{
"slug": "…",
"url": "https://claude.ai/code/artifact/…",
"version": "…",
"title": "…",
"files": { "index.html": "<sha256>", "app.css": "<sha256>" }
}
files maps each published path to the sha256 of what was published or pulled; pull uses it as the merge base. It is never published (dotfile). The next publish DIR updates that slug without --slug and sends the saved version as the base version, so if someone else published in between, the publish fails with exit code 3 instead of overwriting their version. Commit it or ignore it as you prefer.
Typed artifacts. An artifact made from an Artifact type (Slides, Design, …) holds files the type supplies, index.html among them. They stay fixed and pull leaves them out, marking the directory "typed": true in .artifact.json. `publish DI
// HOW IT'S BUILT
KEY FILES