Guide · Agent skill
How to use the Project Status Page agent skill (project-artifact)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The project-artifact skill lets an agent turn a project that has several workstreams into a tabbed status page, publish it with the built-in Artifact tool to a claude.ai link, and keep that same link current when you ask for a refresh. It is aimed at project leads, engineers tracking related pull requests, and teams that want one consistent status link. After this guide you will know what the skill does, how to install it, how to phrase a request so it triggers, and what to check for safety.
Project Status Pageanthropics/claude-plugins-official · Apache-2.0 Download the skill Quick start
- 1Download the ZIP. Get the project-artifact ZIP from the directory page.
- 2Unzip into a skills folder. Unzip into ~/.claude/skills/ for personal use or into your project's .claude/skills/ folder for one project.
- 3Or upload in the Claude apps. Go to Settings → Capabilities → Skills and upload the ZIP.
- 4Confirm the requirements. Make sure you have a claude.ai login for the Artifact tool and, for PR-based projects, gh and git available.
- 5Ask for a status overview. Describe a project with several workstreams and ask for a shareable, kept-current status page.
- 6Open and share the page. Open the published link on claude.ai and share it with teammates from the viewer, since it is private at first.
- 7Refresh later. Ask for a refresh to update the same link and see what changed.
What the project-artifact skill makes the agent do
The skill produces one kind of artifact: a status page for a project too big for a single update, such as a migration, launch, research effort or org initiative with parallel or dependent workstreams. The agent gathers current state from sources such as pull requests, git history or docs, then builds a single self-contained HTML file with tabs.
The tabs are chosen from a catalog. Overview and the workstream sequence are almost always included. Attention, Background, Plan, Risks and open questions, and Decisions/FAQ appear only when they have real content, so a simple project may end up with just two tabs.
- Publishes with the built-in Artifact tool to a URL of the form https://claude.ai/code/artifact/<uuid>.
- The page is private by default. The owner can share it with teammates from the viewer.
- Each project keeps a small config file, so a refresh reuses the same URL and reports only what changed.
Install the skill from the ZIP
You can install the skill in either of two ways. Download the ZIP from the directory page, then choose the option that fits how you work.
For a personal install that applies everywhere, unzip the download into ~/.claude/skills/. To limit it to one project, unzip it into that project's .claude/skills/ folder instead. If you use the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/
- Single project: <your project>/.claude/skills/
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
Check the requirements before you start
The skill needs the built-in Artifact tool, which requires a claude.ai login. It also needs a plugin data directory, where the per-project config and the rendered page are stored. The skill's files are SKILL.md, swe.md and template.html.
If your workstreams are pull requests, the skill also uses the GitHub CLI (gh) and git, as described in swe.md. Those are not needed for non-software projects that track work in a document or spreadsheet.
- Built-in Artifact tool with a claude.ai login
- A plugin data directory for config and page files
- GitHub CLI (gh) and git, only for software projects whose workstreams are PRs
Trigger the skill with a natural request
You do not need a special command. Describe a project that spans several workstreams and ask for a shareable, kept-current overview. The skill is meant for work where you want a link that teammates can open, not a long chat summary.
If you already have a published page for the project, say so. The agent can record that existing URL instead of creating a new one. If you name the project, the agent loads its saved config; a saved config means the next request is a refresh.
- "Make a status page for the payments migration. It has five workstreams and I want a link my team can open."
- "Refresh the project status artifact for the search rewrite."
- "We already have a status page for the launch from another machine. Record its URL and update it."
See what a run looks like
For a software project, the agent pulls open pull requests and recent history live with gh and git rather than from memory. It writes the HTML from the skill's template, checks the output for clipped or overflowing text, and publishes it. You then open the page on claude.ai and share it.
On a refresh the agent reuses the same URL and the same favicon emoji, and it reports only the delta from the last render. The page is designed as an internal status tracker.
- First build: gathers state, writes page.html and config.md, publishes, then reports the URL and the tabs filled.
- Refresh: re-gathers state, redeploys to the recorded URL, reports what changed.
- Conflict: if another session published a newer version, the agent fetches the current page, reconciles, then publishes again.
Safety notes: scripts and network access
The skill does not run scripts, according to its listing. It does use the network: it reads live state from sources such as GitHub through gh and git, and it publishes through the Artifact tool. Review the commands the agent runs before approving them, and check that it can reach the data it needs.
Because the page is private by default, only you can open it until you share it. Be deliberate about sharing, since the page may contain PR titles, owners and internal risks. The skill is not intended for public documentation.
- No scripts are run, according to the listing.
- Network use is required for live state and publishing.
- Content stays private until you share it from the viewer.
Tips for getting a useful page
Give the agent a clear goal and a list of workstreams, or let it read the project doc. The page is only as current as the sources, so a stale doc or missing repo access produces a stale page. For PR-based projects, the skill expects a X.Y numbering convention where the first number marks the stage and the second marks parallel work within that stage.
Keep the same favicon emoji and project name across refreshes, so teammates can find the page again. Use a hub or bookmark to link the URL for teammates, since the slug is generated by the server.
- Use the X.Y PR numbering convention from swe.md: X for blocked stages, Y for parallel PRs.
- Skip the skill for a single pull request or a small change.
- Add the URL to a project hub or bookmark so the team can find it.
What people use it for
- A project lead tracking a large migration with several dependent stages and a single link for the team.
- An engineer following a set of related pull requests who wants a readable status page instead of a long chat summary.
- A research or launch effort where owners, risks and open questions need to be shared and updated in place.
Frequently asked questions
How do I install the project-artifact skill?
Download the ZIP from the directory page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder for one project. In the Claude apps you can instead upload the ZIP under Settings → Capabilities → Skills.
What does the project-artifact skill require?
It needs the built-in Artifact tool with a claude.ai login and a plugin data directory for storing config and the rendered page. For software projects whose workstreams are pull requests, it also uses the GitHub CLI (gh) and git.
Is it free, and what is the licence?
The listing states the licence is Apache-2.0. This guide does not state pricing, so check the directory page and your claude.ai plan for any cost of the Artifact tool.
Is the status page public?
No. The page is private by default, and teammates get a 404 until you share it from the viewer. Redeploys keep the sharing setting.
When should I not use this skill?
Do not use it for a single pull request or small change, where a page adds little value. It is also not suited to public documentation, or to projects where the agent cannot reach the source data.
How does it compare to just asking for a chat summary?
The skill builds a persistent, shareable HTML page at one link that is refreshed in place and reports only what changed. A chat summary is a one-off message that does not update a shared URL.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you run a project with several parallel or dependent workstreams and want a private, shareable status link that updates in place. Skip it for single pull requests, small changes, public docs, or projects where the agent cannot reach the source data.
Download the skill