Skiff update: drag and drop images onto a session. Skiff inserts them in the terminal and keeps them in a library so you can reuse them in other sessions. Skiff is a lightweight desktop app built around your terminal, and terminals handle dropped files a bit differently. Now it works the same way everywhere.

The Main Skipper's name now defaults to Admiral. It deserves the rank. You can also now set /SKIPPER.md files for your Skipper crew, so they get specific Fleet and Project instructions. Once we hit v2 with remote hosts and then v2.5 with scheduled tasks, will Skiff turn into the simplest and most lightweight autonomous agent orchestrator we've ever seen?

Dosirak's Mac App Store review came back. The reviewer is asking for a sample file, so I put together this beautiful page for them with a download of the Recipes database. dosirakdb.app/sample-databas…

Skiff is cooking too hard. Should I stop or keep going?

I don't see anyone in my feed building products for the @MicrosoftStore But why? Look at this: submitted a new version at 10:29 and it was approved at 10:43. 14 minutes. Yea, don't build for the Microsoft Store, I don't want y'all clogging the review pipeline.

I have my promo video skill and scripts dialed in. I can ask my Claude Skiff agent to build a promo video on any feature and it just makes it, using real screens with mock data, horizontal and vertical orientations. Here I asked it to explain how agent delegation works.

Here's the new gallery feature in Skiff. Every image you drop into a Skiff terminal gets saved in the agent-skiff cache. The library is accessible from any Skiff session. Pin your favorites so they're always on top. Super handy if you find yourself looking for the same images over and over.

Skiff is built with Tauri, so the UI is a web frontend. That means I can ask my agents to take screenshots through headless Chrome. It works great, and I don't have to spend time setting up sessions to show off a feature. Here's one they just took of the new Fleet Skipper. Fake data, real app.

While building Skiff v2 with Skiff, I realized I needed Project Skippers. Orchestrating different projects through one agent started to get nuts. Now every project can have its own Skipper, so the main Skipper can drop anchor and keep watch while I relax. Live in Skiff 1.7.

parallel agents building Rust 💀

Don't you love going to the support portal and searching for something like > how to make a payment and they send you to the ancient library of payment scrolls instead of answering with <a href="/payments">Make Payment</a> 💀

The more I use Skiff, the more I want it to connect to other computers. So I'm working on v2: remote hosts. I already had a good client/daemon split. Now I'm refactoring it so the daemon owns the projects, fleets and ledgers. The goal: 1. Launch Skiff on your computer 2. Add an SSH host 3. Skiff installs the daemon and sets up the server for you I might turn into a VPS AI dev 😭

We pushed a new version of migrate-filemaker. If you're a FileMaker developer, the part to look at first is the explode step. FileMaker exports a DDR as one XML file per database file. Our test DDR was 174 MB across two files. Grepping raw DDR XML is miserable. So the skill takes it apart. Every script, table, layout, relationship, value list, custom function, menu, account and privilege set becomes its own text file. Scripts come out as numbered steps. Layouts come out as an object tree with their hide rules, triggers, buttons and portal filters. Every calculation shows its text plus a refs line listing the fields and custom functions it uses, so finding everything that touches Invoices::total is one grep. On the test DDR that took 20 seconds and produced 4,542 object files covering 36,051 calculations. With the DDR in pieces, the work splits across agents. In the test, 22 subagents read all 4,542 objects in about 12 minutes, and the migration plan cites object files as its evidence.