Artifact organizer share
Skill keepYaoung/artifact-organizer/skills/artifact-organizer-share
Agent skill that turns semantic JSON into self-contained, themed HTML — then stacks your artifacts into one persistent, restyleable dashboard. Zero dependencies, opens offline.
npx -y skills add keepYaoung/artifact-organizer --skill artifact-organizer-shareAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 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
Deploy a previously rendered Artifact Organizer HTML file to Vercel and return a live shareable URL. Use whenever the user asks to "share", "publish", "deploy", or "send" a Artifact Organizer output. Requires the `vercel` CLI (`npm i -g vercel`, then `vercel login`) and the `artifact-organizer` skill for the share script.
The file declares its own license as MIT. 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, as published. Nobody here has run it
Artifact Organizer — Share mode
Deploys an existing .html file (typically from ~/.artifact-organizer/out/) to Vercel and returns a public URL. Thin wrapper over the artifact-organizer skill's scripts/share.sh.
When to use
- User just rendered a Artifact Organizer page and says "share this", "send me a link", "can I send this to someone".
- User explicitly asks to deploy an HTML file.
- User wants a public URL for an existing output.
Do not use for: generating new pages (use hyperscribe or hyperscribe-slides), deploying arbitrary sites (this only handles Artifact Organizer outputs).
Preconditions
vercelCLI must be on PATH. If missing, the script exits 127 and tells the user:npm i -g vercel && vercel login.- An
.htmlfile must exist at the path you pass. - User should have run
vercel loginat least once (interactive — don't try to do it yourself).
Resolve the HTML path
- Explicit path given — use it (verify it exists).
- "last" / "just now" / no path — find the most recent output:
If nothing exists, ask the user to render one first withHTML=$(ls -1t ~/.artifact-organizer/out/*.html 2>/dev/null | head -1)hyperscribe/hyperscribe-slides/hyperscribe-diff.
Deploy
# Locate the share script (installed alongside the hyperscribe skill).
SHARE=$(for p in \
./.claude/skills/artifact-organizer ~/.claude/skills/artifact-organizer \
./.codex/skills/artifact-organizer ~/.codex/skills/artifact-organizer \
./.cursor/skills/artifact-organizer ~/.cursor/skills/artifact-organizer \
./.opencode/skills/artifact-organizer ~/.opencode/skills/artifact-organizer \
~/.claude/plugins/cache/artifact-organizer-marketplace/*/plugins/artifact-organizer
do [ -f "$p/scripts/share.sh" ] && { echo "$p/scripts/share.sh"; break; }; done)
if [ -z "$SHARE" ]; then
echo "artifact-organizer share script not found. Install with: npx skills add keepYaoung/artifact-organizer" >&2
exit 1
fi
bash "$SHARE" "$HTML"
On success, the script prints Deployed: https://<id>.vercel.app. Extract that URL and report it back.
Report to user
After a successful deploy, tell them:
- The live URL.
- That the page is
cleanUrls: trueon Vercel's edge network. - That re-running this skill issues a fresh URL (old ones remain live unless deleted).
Failure modes
| Exit | Cause | Fix |
|---|---|---|
| 127 | vercel CLI missing | npm i -g vercel && vercel login |
| 2 | path missing/invalid | Check ~/.artifact-organizer/out/ exists; render something first |
| 1 | deploy ran but no URL parsed | Read the full deploy log (path printed in stderr) |
Avoid
- Deploying HTML containing secrets — if the content has API keys or credentials, warn the user first.
- Running
vercel loginyourself — it's interactive; the user must do it. - Deploying files outside
~/.artifact-organizer/out/unless the user explicitly asks.