Publish a multi-repo portfolio sweep as a living, shareable status page
Grade a portfolio of repos worst-signal-wins first, then hand the verdicts to a page that stays current on re-runs instead of republishing a wall of unshareable local HTML each time.
Also usesclaude-plugins-official
self-assess-portfolio's own output is deliberately narrow: one grade per repo, worst-signal-wins, written once to a local file with no sharing and no delta tracking across sweeps. project-artifact adds exactly what that file lacks -- a shareable URL, status pills, an Attention tab for what's blocked, and a refresh that reports only what changed since the last sweep instead of re-narrating every repo. Run the sweep first; a Gray verdict means "not yet assessed," and the status page must not smooth that over into an invented grade.
Start here
Sweep every repo in this portfolio directory and grade each one's health worst-signal-wins first, then publish that sweep as a shareable status page that keeps itself current on re-runs instead of a one-shot local file I have to re-send every time.Needsself-assess, project-artifact
Beats
Run these in order. Each prompt is copy-pasteable straight into Claude Code.
self-assess:self-assess-portfolioGrades every repo in an explicit portfolio directory Red/Amber/Green/Gray by worst-signal-wins, refuses to synthesize a placeholder grade for an unassessed repo, and writes a one-shot self-assess-portfolio.html into the portfolio directory itself -- local, unshareable, and with no memory of the previous sweep.
Run this beat on its own
promptsweep every repo under ~/LocalDocuments/GitHub_Forks and grade each one's self-assess healthproject-artifact:project-artifactTurns that one-shot local file into a living claude.ai page -- status pills, an Attention tab for what's blocked, and a delta-only refresh that reads the previous render's embedded state block -- none of which self-assess-portfolio's own static HTML does on its own.
Run this beat on its own
promptpublish that portfolio sweep as a shareable status page I can send the team, and keep it current when I re-run the sweep
Worked example
Grounded in — why this beat order is trustworthy
the user's own ~/LocalDocuments/GitHub_Forks directory holds roughly 150 git repositories, including werkstoff itself -- exactly the shape of "explicit portfolio directory" self-assess-portfolio's own Step 1 scope gate requires, since it refuses to infer a git repo's parent as the portfolio.
Do / Don't
- Grade every repo in an explicit portfolio directory, worst-signal-wins, before publishing anything.
- Publish the sweep as a page with a delta-only refresh, so re-running it reports only what changed rather than re-narrating everything.
- Let a Gray verdict mean 'not yet assessed' and keep it that way on the status page -- never smooth it into an invented grade.
- Don't infer a portfolio directory from a single git repo's parent -- the grading step refuses to and needs an explicit directory.
- Don't republish a full wall of local HTML on every re-run -- that's exactly the unshareable, no-memory output the status-page step exists to replace.
- Don't let an unassessed repo's Gray verdict get smoothed into an invented grade on the published page.