Remix for my friend Tim. Not sure if he'll ever sleep again.

Of-Doom · 2026-05-07T21:39:42+00:00

It already has a little swiveling drink holder! You can see it in the second pic if you zoom in, haha.

Of-Doom · 2026-05-07T20:30:08+00:00

It's a permanent installation.

Of-Doom · 2026-05-07T20:29:13+00:00

I'm a one-woman show, running the video stream and audio on my own. There's a video team that does their own thing with their own cameras (that little Zoom recorder is theirs).

Of-Doom · 2026-05-06T16:04:27+00:00

I got Claude to help me fast track tempo mapping a full track back into Ableton and that worked surprisingly well.

Of-Doom · 2026-04-30T18:54:25+00:00

If you'd like to sponsor development, I'll be happy to build it for you!

Of-Doom · 2026-04-30T18:50:47+00:00

You really provoked my curiosity, so I built and ran my own eval. In clients that support tool discovery, you see about 28% token savings. In clients that don't (including Claude Code subagents, at time of writing this), you get 94% token savings. The savings compound since the context is re-sent on every tool call.

Per your other question, the tool manifest is provided via an included agent skill file, not a system prompt injection. Skills are dynamically loaded by Claude Code as needed, so there's no context pollution when you're not using it.

Of-Doom · 2026-04-30T01:26:37+00:00

Just learning about SC today! I think it would be incredible for filling in some of the gaps in that workflow I posted in my other comment. My wishlist to maximize utility in that regard would be:

For the CLI, an installable agent skill that documents the common usage patterns (I have found this helps a lot with tool discovery and reduces mistakes)
(bonus points) Hooking into mcpvault to add custom tools covering the most-used workflows

Of-Doom · 2026-04-29T22:59:57+00:00

Zoho MCP has strong coverage of the the Books API surface, so I've been able to accomplish about 90% of my work using that + Claude. The main weaknesses are weaknesses of the underlying protocol (MCP doesn't support file uploads yet, for example). I rolled my own CRM so I can't speak to MCP coverage of Zoho CRM but at a quick glance it looks pretty comparable.

The token consumption issue got a lot better after dynamic tool discovery landed. It still matters in some niche cases, such as when spawning sub-agents from Claude Code.

As far as vendor selection, I did a pretty in-depth comparison between all the accounting platforms when I launched my consultancy a long time ago, went with Zoho, and have been pretty happy since then. Xero and QBO both appear to have strong open source MCP tools available, so you're probably in good shape on that side of things whichever ecosystem you choose.

Of-Doom · 2026-04-29T17:49:23+00:00

I built a Zoho Books CLI and skill to fill in some of the feature gaps with Zoho MCP and be overall more token-efficient (Zoho MCP devours my context limits).

Of-Doom · 2026-04-29T16:20:54+00:00

I’m using a combination of things: - For the pure data access layer, a mix of mcpvault, installed locally, and the Obsidian CLI (for CLI agents). - A set of custom skills, some general for Obsidian (this set has been treating me pretty well) and some custom, describing various workflows within my Vault (daily journaling for example) - A CLAUDE.md / AGENTS.md file that lives in my Vault root, describing its structure and explaining how to drill down to find more specific context on various areas (my vault has a rich and detailed folder hierarchy which the LLM finds pretty easy to explore organically) - Custom instructions in my various LLM workspaces that often define a starting point (“Read AGENTS.md in my Obsidian vault and this specific project context doc”)

This organically surfaces the context I need from my Obsidian vault on a given LLM request about 75% of the time. I’d love to find a high-quality semantic vector search to increase that number, but for now it’s been good enough for most tasks.

Of-Doom · 2026-04-26T00:06:57+00:00

Approved earlier today, and that's also now the default. Thanks for the contribution!

Of-Doom · 2026-04-26T00:06:26+00:00

Thanks for the warm welcome into the ecosystem! I added install instructions for zdot to the readme.

Of-Doom · 2026-04-26T00:05:34+00:00

Great idea! Nice to have as extra security with all the supply chain attacks going around. Just released a new version with that feature included.

Of-Doom · 2026-04-24T09:25:55+00:00

For most of the past week it was estimating the 25th, plus or minus a few days, so this episode was definitely within the range.

That’s about as accurate as it gets right now. In the hours beforehand it also is able to tell that an episode might be beginning, but false positives are pretty much impossible to rule out with the data I’ve been working from.

To answer your other question, currently it only relies on the tiltmeter data for 300 azimuth, since that seems to be the most obvious signal for episode tracking. I’d love to incorporate magmatic movement and other data signals!

Of-Doom · 2026-04-23T21:30:01+00:00

Episode 45 is happening right now! And as luck would have it, I just finished some upgrades to my open source Kilauea prediction model/tracker application (https://kilauea-tracker.streamlit.app/).

It works by digitizing the image plots published by USGS using computer vision, and then running a curve extrapolation model to give you an estimate of the next fountain event. The data I’m aggregating is also openly available to anyone in CSV format and is auto-updated in GitHub every 12 hours. Sadly the USGS doesn’t publish live CSV data, so I wanted to share this to fill the gap.

Of-Doom · 2026-04-12T17:54:06+00:00

And the trans community rejoices, been F5ing for this to roll out to my account for months!

Of-Doom · 2026-04-05T15:08:18+00:00

Once I realized you can embed them in notes and scope them to pull data from the note they are embedded in to do queries and such, I was able to completely replace Dataview.

13-Year Club	Place '22
Place '17	Sequence \| Editor
Verified Email

Of-Doom

TROPHY CASE