I have 14 public repos. On my GitHub profile they were just names, and nobody clicks a name they don't understand.
So I pointed my own Claude skill, living-canvas, at my profile and asked it to show what every repo actually does.
Every repo became a TV channel with the same three-panel story: the problem → what the tool does → the result. Every example comes from the repo's own README.
The channels
| Channel | Repo | What goes in → what comes out |
|---|---|---|
| 📺 See it | devtv | 13 dev feeds → one TV page, no backend |
| living-canvas | any repo → animated SVG banner, ~7 KB | |
| gitcomics | any repo → 8-panel comic from real code | |
| 📖 Read less | leantext | 92,348 tokens → 755 |
| tokslayer | noisy README → just the product | |
| delta | 41-token prompt → 12 | |
| context-squirrel | 3,150-token history → 147 | |
| 💰 Spend less | token-sensei | task + budget → checkpoint: done / left |
| sir-shortoken | 1,500 words → the right 300 | |
| tactical | rambling incident reply → SITREP | |
| ✅ Trust it | implementation-scout | question → VERIFIED / NOT VERIFIED sources |
| ship-happens | YAML → tested on a real cluster first | |
| trooper | Claude fails → run continues on Ollama |
How it was made
living-canvas read every README, picked one story and one real number per repo, and drew it as a canvas page. I recorded it frame by frame in headless Chromium and encoded it with ffmpeg.
Its one rule: if someone saw a single screenshot, could they tell what the project does?
Try it on yours
living-canvas is open source: github.com/shouvik12/living-canvas
Drop your GitHub handle in the comments, and I'll run it on a few profiles and post the results.
Top comments (0)