Claude Code skills: building a workflow that runs itself
The control layer of my work system is markdown and small scripts. How a workflow combines Claude Code skills, rules, model routing, and parallel sub-agents.
Most of my AI pipeline isn't AI
By volume, most of my AI pipeline is plain Python. The model is a small, expensive part I call as little as possible. The script-first split, and why it wins.
Capturing email and calendar without a mailbox API
Microsoft Graph and IMAP were off the table, so I used Power Automate, OneDrive sync, and one 15-minute scheduled task to pull email and calendar into a local inbox.
The Claude Code plugins I built and run
I put the Claude Code tools I reuse across projects into one public toolshed: generators, workflow commands, anti-slop checks, search visibility, rule packs, and prompts.
My AI was smart. It just couldn't see my job.
My work context was scattered across email, meetings, documents, and notes. So I wired it into a private Obsidian vault Claude Code can read.
A safe way to edit database content with AI coding tools
AI coding tools edit files. Your content lives in a database. This is the pull, diff, push workflow that connects the two without hand-writing SQL against production.
Creating reusable Claude Code skills
If you keep pasting the same prompt, save it as a small Claude Code skill. You can run it with a short command and add templates or scripts later.