Case files from the workbench
Everything on this page started as a fix for a problem I hit in my own daily agent workflow: an agent that quietly summarized the wrong source, the fear of a key leaking in a public push, overnight builds dying at the usage limit. Each tool ran in real use before it had a README. The write-ups below say plainly what is tested, what is a limit, and what stays your job. None of it was built to be a demo.
What are you trying to do?
Skills that make an agent read the source it was actually asked to read, and read third-party code before anything gets installed.
belschak / web-research-cascade
Claude Code skill
Four fetch stages, from plain WebFetch to your own logged-in browser. The rule sits above the ladder: when a source blocks, escalate the fetch. Never swap the source for a weaker one just because that one loads.
$ git clone --depth=1 https://github.com/belschak/web-research-cascade.git ~/.claude/skills/web-research-cascadebelschak / repo-audit
Claude Code skill
$ git clone --depth=1 https://github.com/belschak/repo-audit.git ~/.claude/skills/repo-auditThe checks that stand between a working private repo and a public one.
belschak / publish-gate
Claude Code skill
This gate is built so that a dirty commit never leaves your machine.
$ git clone https://github.com/belschak/publish-gate ~/.claude/skills/publish-gatebelschak / showpiece
Claude Code skill
$ git clone --depth=1 https://github.com/belschak/showpiece.git ~/.claude/skills/showpiecebelschak / claude-design-handoff
Claude Code skill
$ git clone --depth=1 https://github.com/belschak/claude-design-handoff.git ~/.claude/skills/claude-design-handoffThe conventions and runners that keep an agent team and parallel sessions useful past a single context window.
belschak / claude-agent-team
Claude Code setup
Most public Claude Code setups are built for writing software. This one is built for everything else: an orchestrator that routes to specialist personas (finance, travel, training, research), each with a backlog file that survives context clears, plus a hiring workflow for domains that have no owner yet. The personas are starting points. The durable part is the conventions, documented with the failure each one prevents.
$ git clone --depth=1 https://github.com/belschak/claude-agent-team.git
$ mkdir -p ~/.claude
$ cp -rn claude-agent-team/template/* ~/.claude/belschak / parallel-streams
Claude Code skill
Your build keeps going.
$ git clone https://github.com/belschak/parallel-streams.gitSmall skills that each take over one recurring chore end to end.
belschak / video-watch
Claude Code skills
$ git clone --depth=1 https://github.com/belschak/video-watch.git video-watch-repo
$ mkdir -p ~/.claude/skills
$ cp -r video-watch-repo/video-watch video-watch-repo/audio-transcribe ~/.claude/skills/belschak / google-maps-skills
Claude Code skills
$ git clone --depth=1 https://github.com/belschak/google-maps-skills.git
$ mkdir -p ~/.claude/skills
$ cp -r google-maps-skills/google-maps google-maps-skills/map-scout ~/.claude/skills/belschak / strava-withings-sync
Python CLI
Standard library Python only, no dependencies.
$ git clone https://github.com/belschak/strava-withings-sync.git