A portfolio shows what you shipped.

This shows the machine.

Rigsby version-controls your Claude Code harness — the skills, hooks, rules and tools you work through — and turns it into a record you can point at. Install it once; it keeps the log itself.

Install

npx rigsby

One command, from anywhere. It finds your harness, reconstructs your history from git if it is there, and records where you are today. Nothing is sent anywhere — the scanner has no network capability at all, which is checked in CI rather than promised in a README.

Publishing a profile is a separate, optional step. Get a token →

What it reads today

Claude Code only — ~/.claude and ~/.claude.json: your context files, memory, skills, commands, agents, hooks, permissions and MCP servers. Codex and Gemini are not supported yet; the manifest carries a tool field so they can be, but nothing reads them today and this page will say so when that changes.

What it measures

Composition — what is on the bench. Practice — whether rules are enforced by machinery or by prose. Trajectory — whether the harness is getting better, which is the part nothing else can see, because nothing else keeps a history.

Badges come in two kinds. Honor badges are claimed. Shame badges name their own fix and disappear when you fix them — the sharpest one, Pruner, can only be earned by removing more than you added.

What travels

Shape, never content. Counts, word totals, categories and a connections graph whose nodes are one-way hashes. Never file contents, never paths, never an environment variable value. You approve the payload once by reading a worked example, and re-approve it if the shape ever changes.