project-artifact

Generate and publish tabbed project status pages as shareable claude.ai artifacts.

35.8k|4.0k|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/anthropics/claude-plugins-official --skill project-artifact
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-artifact
Source: https://github.com/anthropics/claude-plugins-official/tree/main/plugins/project-artifact/skills/project-artifact
Command: npx skills add https://github.com/anthropics/claude-plugins-official --skill project-artifact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-workstream projects (migrations, launches, research efforts) outgrow single status updates, and keeping teammates aligned means repeatedly re-writing the same overview. This Skill generates a structured, tabbed HTML status page and publishes it to a default-private claude.ai artifact URL that can be refreshed in place, so the page stays current without re-minting links.

Core Features & Use Cases

  • Opinionated tabbed status page: Generates a self-contained HTML page from a template with Overview, Workstreams, Attention, Background, Plan, Risks, and FAQ tabs, including a status banner, next-steps strip, and status pills.
  • Refresh with deltas: Stores a per-project config and an embedded machine-readable state block, so each refresh re-gathers live state (e.g. via gh pr list / git log for PR-driven projects), redeploys to the same URL, and reports only what changed.
  • Software specialization: A companion swe.md defines the X.Y PR-numbering convention, live PR-state queries (CI, unresolved review threads), and per-PR detail blocks for engineering projects.
  • Use Case: You are driving a 12-PR database migration. Ask for a project artifact and get a shareable page with the PR sequence, per-PR verification notes, risks, and next steps; a week later, ask to refresh it and receive the same URL plus a short delta of merged and newly blocked PRs.

Quick Start

Ask the assistant to create a project status artifact for your current multi-workstream project and publish it as a shareable claude.ai page.

Frequently Asked Questions about project-artifact

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

FAQPage Schema
How do I create a shareable project status page with Claude?

Invoke the project-artifact skill with your project name; it gathers live state from your sources, fills a tabbed HTML template, and publishes it with the Artifact tool to a default-private claude.ai URL you can share with teammates from the viewer.

How do I update a published project status artifact?

Ask to refresh the artifact. The skill reads the previous render's embedded state block, re-gathers live data, edits the existing HTML in place, redeploys to the same URL, and replies with only the delta since the last as-of timestamp.

Does the project status page work for GitHub PR-based projects?

Yes. The swe.md specialization pulls open and merged PRs with gh, checks required CI status and unresolved review threads via GraphQL, and numbers PRs with an X.Y convention that encodes dependencies without drawing a diagram.

Can teammates open my artifact page right after publishing?

No. First publishes are private to the owner; teammates get a 404 until the owner shares the page from the claude.ai viewer. Redeploys preserve the sharing setting once it is granted.

Why can't the artifact page load external scripts or images?

Artifact pages are served under a strict CSP that blocks all external hosts, so the page must be one self-contained HTML file with inlined CSS, data-URI images, and at most one small inline script for tab switching.

When should I not use a project status artifact?

Skip it for single-PR changes or one-off updates, for public documentation, and in headless non-interactive sessions where the Artifact tool is unavailable and publishing cannot be completed.