| name | share-artifact |
| description | Publish/host an app or artifact you built to Artifact Studio and get a public URL to share. Use after building an SVG/diagram, an interactive HTML widget, a Markdown one-pager, or a real multi-file React app (via esm.sh, no build) that you want to hand someone as a link — or when the user says "share this", "publish this", "host this", "give me a link", or "deploy this app". Apps go live at <slug>.jasonv.app. |
Share / host an app on Artifact Studio
Publishes to Artifact Studio and returns a public URL, https://<slug>.jasonv.app.
Three surfaces wrap one API; this skill drives the CLI. (Repo: jpvarbed/artifact-studio-tools.)
Announce at start: "Using share-artifact to publish this."
Setup
From a checkout of the artifact-studio-tools repo (bun install once), export your credentials:
export ARTIFACT_API_KEY="ak_…"
The CLI/MCP default to the hosted studio API; only set ARTIFACT_API_BASE to self-host.
If the key is missing, tell the user: sign in at studio.artifacts.jasonv.dev (email → one-time
link, no password), then Settings → API keys → Mint key (shown once). Apps published with that
key belong to their account and appear in the studio Mine tab. Run the CLI as
bun run cli <args> from the repo root (or bun cli/src/index.ts <args>).
Publish a single file (svg / html / markdown)
bun run cli share <file> --slug <slug> [--kind svg|html|markdown] [--title "..."] \
[--visibility private|unlisted|public] [--comments] [--llms ./llms.txt]
--kind is inferred from the extension. --slug is the URL. Default visibility unlisted (link
includes a ?k= token). Prints the URL — hand it back.
--llms <file> attaches an agent-readable manifest served at <slug>.jasonv.app/llms.txt (the
llms.txt convention) so other agents can understand the app. Recommended for anything non-trivial.
To update an existing app, re-run with the same --slug — it updates in place (same URL + token),
not a new app. A slug you don't own or a retired one errors taken (pick another). Options you omit
are preserved, so to keep the current visibility just leave --visibility off.
Deploy a multi-file app — real React, no build step (esm.sh)
Write index.html + JS modules that import deps from a CDN at runtime (no bundler):
<script type="importmap">{"imports":{"react":"https://esm.sh/react@19","react-dom/client":"https://esm.sh/react-dom@19/client"}}</script>
<div id="root"></div>
<script type="module" src="./app.js"></script>
Then deploy the folder (must contain index.html; use relative or CDN-absolute paths):
bun run cli deploy <dir> --slug <slug> [--title "..."] [--visibility ...] [--comments]
Prefer a real build step? deploy just uploads a static folder, so build with Vite/etc. and point it
at the output: bun run cli deploy ./dist --slug <slug>. See the build-artifact-app skill (no-build vs
build-step) and examples/guestbook for a Vite + React + TypeScript app.
Re-running deploy with the same --slug deploys a new immutable version (same URL + token); files
you drop from the folder are simply absent in the new version. Undo with artifact rollback <slug>;
preview with deploy --staging then artifact promote <slug>. artifact versions <slug> lists them.
Optional managed backend (per-app key-value store)
bun run cli backend <slug>
From the app's frontend (same origin): fetch("/api/kv/<collection>/<key>", { method:"PUT", headers:{ "X-Data-Key": KEY }, body: JSON.stringify(v) }) (GET → {value}; /api/kv/<collection>
lists). App-shared by default; add an X-End-User: <per-visitor-secret> header to make rows private
to that visitor (ART-5). See the build-artifact-app skill for the per-user pattern.
Manage
bun run cli list
bun run cli get <slug>
bun run cli delete <slug>
Notes
- Apps run full-page on their own origin (network allowed; HTML/React apps run their JS live),
isolated from the studio's keys.
- Same actions are available as MCP tools (
mcp: publish_artifact, deploy_app,
provision_backend, list/get/delete_artifact) and a REST API at $ARTIFACT_API_BASE/v1
(/openapi.json). See cli/README.md and mcp/README.md.
