plan-artifact

Publishes plan HTML files to claude.ai artifacts with stable republishable URLs.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/shawn-sandy/agentics-kit --skill plan-artifact-shawn-sandy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-artifact
Source: https://github.com/shawn-sandy/agentics-kit/tree/main/kit/plugins/artifact-tools/skills/plan-artifact
Command: npx skills add https://github.com/shawn-sandy/agentics-kit --skill plan-artifact-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Sharing an implementation plan with a team usually means sending a file or link that goes stale the moment progress changes. This Skill publishes a plan-agent HTML plan to claude.ai and republishes updates to the same URL, so viewers watch steps check off live at a link they already have. ## Core Features & Use Cases - Stable URL publishing: Records the artifact URL in the plan spec's frontmatter so every later session republishes to the same page instead of minting a new link. - Title validation: Checks the plan title against the plugin's title rules before publishing, fixing the markdown spec rather than hand-editing generated HTML. - Render verification and fallback: Fetches the published URL to confirm the page rendered, and offers GitHub Pages or local gallery alternatives when publishing fails. - Use Case: A developer finishes a plan-agent plan, publishes it once, shares the URL with the team, then republishes after each status update so stakeholders always see current progress. ## Quick Start Publish my plan at docs/plans/add-auth-flow.html to claude.ai and give me the shareable URL.

Frequently Asked Questions about plan-artifact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a plan to claude.ai as an artifact?▼

Provide the path to the plan HTML file, or let the skill glob docs/plans/*.html and ask which plan to publish. It publishes via the Artifact tool with a description and favicon, then returns the shareable URL.

How do I update a published plan without getting a new URL?▼

The skill writes the returned artifact-url into the plan spec's frontmatter on first publish. On later runs it passes that URL to the Artifact tool, so the same page updates instead of a new one being created.

Can I edit the plan HTML directly before publishing?▼

No. The plan HTML is generated from the sibling markdown spec, and any hand edit is overwritten on the next rebuild. Edit the .md spec's title or steps and let the plan rebuild before publishing.

What happens if publishing to claude.ai fails?▼

The skill reports that publishing did not happen and why, leaving the local plan HTML as the deliverable. It offers two fallbacks: publishing to the repo's GitHub Pages artifacts gallery or using the local docs/plans/index.html gallery.

Why does the skill fetch the URL after publishing?▼

A returned URL is not proof the page rendered, since a blank artifact also returns a URL. The skill fetches the page with WebFetch and confirms the plan title appears before reporting success.