The email skill is an executable note

The photo was the gesture that saved the company — snap the schedule, every date lands on the calendar. But a photo is a thing you do once. You point the camera at the mess on the fridge, and you're done. The firehose that never stops isn't the fridge. It's your inbox.

The mess that keeps arriving

The dates on a party invite are a one-time pile. The receipts aren't. The order confirmations aren't. The class sign-ups, the shipping notices, the monthly invoices — those arrive forever, in the same shape every time, and every one of them is a little act of data entry that some human keeps doing by hand. Read the email, find the four numbers that matter, type them into a spreadsheet, delete the email. Again tomorrow.

That's the same transcription tax as the photo, except it doesn't end. And because it doesn't end, it's the one worth automating properly.

Tell it once

So the question became: what if you could tell the agent, one time, what the email is and what to keep — and never do it again?

You can. You describe it the way you'd describe it to a new assistant: "I get a receipt from this vendor every so often. Save the date, the receipt number, what it was for, and the total." Dustav writes the rule — which emails it matches, which typed fields to pull — reads you back a real row so you can check it, and then it's live. From that point on, every matching email that arrives becomes a row in a table you can search and export. You stop being the parser.

A rule is a note that runs

Here's the framing that made it click for me. Back when this was pal.fun, a note was a thing the agent wrote down and kept for you — a recipe, a plan, a list — so it didn't vanish into a transcript. Useful, but inert. It just sat there.

An email rule is a note that runs. It's the same gesture — you and the agent author something durable together, by talking — except the thing you author has a job. It watches for its email and does the entry. It's the difference between a recipe card and a cook.

The marketplace I killed, done right

I once built a per-skill app store for pal.fun and then deleted it, because a generic skill couldn't earn its cost. Email rules are what that idea should have been all along: not a catalog of abstract capabilities you shop for, but one concrete, useful skill you author for your inbox, in a sentence, for free. No store, no ceremony, nothing to browse. The capability is specific to your household or your shop because you described your own email to make it.

And it reads the mail — it doesn't match a rigid template against it. That matters, because real email is messy: the vendor changes their receipt layout, the subject line drifts, the total moves. A template breaks on that; a reader shrugs and keeps going. The rule is a description of intent, not a brittle pattern, so it survives the long tail of email that no fixed integration ever covers.

The one-sentence version

The photo taught me the product was never the calendar — it was not having to fill it in. Email rules are the same lesson pointed at the inbox: the product isn't a place to keep your receipts. It's a note you write once, in plain words, that does the filing forever.