project-artifact
Generate and publish a project status artifact — an opinionated, tabbed status page for a project too big for one update (overview & success criteria, the workstream sequence, next steps, plus background, plan, risks & open questions, and decisions/FAQ when they earn a tab) — published with the built-in Artifact tool to a default-private claude.ai page the user can share with teammates. Use when a piece of work spans several workstreams and you want a shareable overview kept current. Each artifact is backed by a small per-project config in the plugin data dir, so refreshing it re-gathers live
Profile →npx skills add anthropics/claude-plugins-official --skill project-artifact --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Generates an HTML-based, self-contained tabbed status page representing a project too large for a single update and publishes it through the built-in Artifact tool to a private claude.ai page. It produces a stable HTML file, embeds a state block for delta-based refreshes, and writes a per-project config to track sources, owners, and tabs. The artifact is intended to be refreshed as workstreams evolve, re-deploying to the same URL and reporting only deltas.
How it works
- Resolve the artifact config and locate the project; determine whether this is a first build or a refresh. Gather goal, workstreams, owners, dates, and sibling docs from live sources (software projects use gh pr list, git log, gh pr view; other domains use project docs or trackers).
- Pick non-empty tabs from the catalog; include Overview and Workstreams by default, and add Attention, Background, Plan, Risks & open questions, and Decisions/FAQ only if substantive content exists.
- Generate HTML from template.html in the skill directory, fill the stubs for the chosen tabs, set a concise <title>, and write to the config's html path (default path under CLAUDE_PLUGIN_DATA). Embed a state block for delta-diffing on refresh.
- Review output for clipping; ensure content can scroll within its container and redeploy if needed.
- Publish with the Artifact tool using file_path = the HTML, favicon, label, and on refresh, url from the config. The tool returns the artifact URL.
- On first publish, write the config.md with artifact details. Report the URL, favicon, and filled tabs. Share and redeploy rules apply for later updates.
- Optionally register the artifact on a hub by appending the URL as instructed by the hub’s process.
- When refreshing, read previous render’s state, re-gather live data, update the existing HTML in place (not full regenerate unless structure changes), and publish with the same URL; report a concise delta.
When to use it
Use when a piece of work spans several workstreams and you want a shareable, current overview that can be refreshed over time. Not for single-PR changes or public docs.
What it can touch
Uses the built-in Artifact tool to publish HTML at a stable URL; reads live sources (PRs, commits, trackers, docs) to populate content; writes config.md and page.html in CLAUDE_PLUGIN_DATA/artifacts/<slug>/.
Caveats
Requires the built-in Artifact tool (Claude.ai login); default page is private until shared; per-project config is stored in CLAUDE_PLUGIN_DATA and may be moved between machines via the config.md mechanism. The SWE specifics for PR-driven projects are in swe.md and not included here.
# project-artifact — an opinionated project status page This skill produces one specific *kind* of artifact: a tabbed status page that represents a project too big for one update — a software migration, a research effort, a launch, an org initiative; anything with a set of parallel/dependent workstreams tracked over time. It generates the HTML (one file, self-contained — the Artifact CSP blocks all external hosts, so everything is inlined; the only `<script>` is the tab switcher) and publishes it with the built-in `Artifact` tool to `https://claude.ai/code/artifact/<uuid>`. The page is default-private; the viewer gives the owner a version picker and lets them share it with teammates. (The general "render any HTML/Markdown to a web page" capability is the built-in `Artifact` tool; this is the project-tracker structure on top — defining what an artifact *is* belongs to that tool, not here.) The SWE specifics for PR-driven projects are in `swe.md`, kept out of this file so the project-artifact structure stays domain-neutral. ## Workflow 1. **Resolve the artifact config, then locate the project.** Each project gets a directory at `${CLAUDE_PLUGIN_DATA}/artifacts/<slug>/` holding `confi
- Workflow
- The artifact config (one per project)
- Refreshing an artifact (deltas, not re-narratives)
- Freshness and trust
- Reading an existing artifact page
- Tab catalog (domain-neutral)
- Conventions (all domains)
- Specializations
- Files
What does the project-artifact skill do?
Generate and publish a project status artifact — an opinionated, tabbed status page for a project too big for one update (overview & success criteria, the workstream sequence, next steps, plus background, plan, risks & open questions, and decisions/FAQ when they earn a tab) — published with the built-in Artifact tool to a default-private claude.ai page the user can share with teammates. Use when a piece of work spans several workstreams and you want a shareable overview kept current. Each artifact is backed by a small per-project config in the plugin data dir, so refreshing it re-gathers live
How do I install it?
Run `npx skills add anthropics/claude-plugins-official --skill project-artifact --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From anthropics/claude-plugins-official, a repository with 33,027 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.