Remote script. The skill install command pulls the plannotator/artifact-server skill from GitHub, so review its contents before you run it in an environment with access to real project files.
Who it is forA developer using Claude Code to draft a plan or design doc who needs teammates to review it without it getting lost in a chat log.
The problemAgent-made HTML plans and mockups scatter across chats and local folders, so reviews and comments have no stable home.
The outcomeThe agent uploads the HTML file, returns a full-screen review link, and the review thread stays attached to that artifact.
What you need first
- Claude Code, for the Agent Skill flow named in the README
- Node.js 24.12 or newer and pnpm 10.34.3, if running from source
- A terminal and git
- For team hosting: an account on one of the listed deployment targets, such as Cloudflare, Kubernetes, AWS, or Google Cloud
Steps
- Start a local server, following the steps in the local run use case, or open a remote Artifact Server you already have access to.
- Run
artifactserver connect. - Run
npx skills add plannotator/artifact-server. - In Claude Code, send
/artifact-server upload that HTML design doc. - Open the full-screen review link the agent returns and leave a comment to test the review flow.
Prompt for your agent
In the plannotator/artifact-server repo setup, use the Artifact Server Skill to upload the HTML file at <path-to-design-doc.html> as a new artifact. Expected output: the full-screen review link returned first. Verify that the link opens and shows the uploaded document.
Caveat. The README says the Claude Code live session delivery needs a research-preview development flag and, on managed plans, an organization policy, so the basic skill upload is the path to rely on.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page