Skip to content

Project Status Page

Builds a shareable, tabbed status page for a multi-workstream project and republishes it on refresh.

Stars
45,770
Licence
Apache-2.0
Files
3 files

What it does

Once installed, when you ask the agent for a status overview of a project that has several parallel or dependent workstreams, it gathers the current state (from sources like pull requests, git history, or docs), builds a single self-contained HTML page with tabs such as Overview, Workstreams, Next steps and Risks, and publishes it with the built-in Artifact tool to a claude.ai link. The page is private by default and can be shared with teammates. On later refreshes it reuses the same link and reports only what changed, using a small saved config for each project.

Great for

  • Project leads who want a shareable overview of a large migration, launch or research effort that is kept up to date
  • Engineers tracking a set of related pull requests who want a readable status page instead of a long chat summary
  • Teams that want a consistent status link that updates in place rather than a new URL each time

Skip it if

  • Single pull requests or small changes, where a page adds little value (the skill itself says so)
  • Public documentation, since the pages are private by default and are designed as internal status trackers
  • Projects where the agent cannot reach the source data, because the page would be built from missing or stale information

Try asking

  • “Make a status page for our database migration project and share it with the team”
  • “Refresh the project status artifact for the checkout redesign and show me what changed since last time”
  • “Build a shareable overview of this launch's workstreams, next steps and open risks”
Step-by-step guide: how to use Project Status PageInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 3 original files, the Apache-2.0 licence and an attribution note.

    project-artifact.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip project-artifact.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip project-artifact.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Name the project explicitly on refresh so the right saved config is used when several artifacts exist
  • Share the artifact with teammates from claude.ai after the first publish, since teammates get a 404 until you do
  • Keep the same favicon emoji across redeploys so viewers can recognise the page

What's inside

  • SKILL.md
  • swe.md
  • template.html

Redistributed unmodified from anthropics/claude-plugins-official under the Apache-2.0 licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.