One Time Automation One Time Automation The Library →
Story · 4 August 2026

I Got Sick for Two Days and My Business Did Not Notice

I used to keep a folder of prompts. It was a Rolodex, and I was the index. Which meant nothing in it ran unless I was upright and remembering.

Leo Chen · 5 min read · AI Skills 101

Not the kind of sick where you still answer a few emails from bed. Flat on my back, phone face down, two full working days gone.

I used to keep a folder of prompts for exactly this reason. Good ones. Tested ones. The ones that actually worked, saved and labelled and ready.

It was a Rolodex. I kept it organized, and I was the index.

Which meant nothing in it ran unless I was upright and remembering. A folder of excellent prompts on a day you cannot sit up is worth the same as an empty folder.

What happened during those two days

My inbox still got sorted every morning, and the only messages left sitting there were the ones that actually needed a human.

New leads from my listings still landed in the CRM and still got their first follow up.

Summaries from every call on my calendar were waiting for me, so catching up took minutes instead of all morning.

The client status reports still went out without me.

I opened my laptop on day three braced for the pile. There was no pile.

None of that was a prompt I remembered to run

Every one of them was a skill. Written once, installed, and run by an agent. Many of them on a schedule, which is the part that matters, because a schedule does not care whether I am sick.

A prompt is something you copy and paste. A skill is something you write once and AI runs it forever.

I have 101 of those skill files today and I add more every week.

The actual difference

People hear "skill" and assume it means a better prompt. It does not. The prompt is the smallest part of it.

That last one is the compounding part. Improve a prompt and you have improved today. Improve a skill and you have improved every Tuesday from now on.

The one thing people get wrong. They try to write the perfect skill first. Write the ugly one. Run it. Fix the thing that actually broke. A skill you fixed twice beats a skill you planned for a month.

Start with the thing you keep retyping

Not the hardest thing. Not the most valuable thing. The thing you have typed into a chat window more than three times.

That repetition is the signal. You have already tested it, already know what good output looks like, already know where it goes wrong. All that is missing is writing it down somewhere your agent can find it without you.

You might be wondering what happened to the folder.

I turned all of it into skills.

Works in: Claude Code, Cowork, or Codex. Any agent with a skill builder and permission to write files. No connectors needed for the first one.

The tool from this piece

The Skills 101 Starter

It does not hand you a finished skill. It walks your own skill builder through making one, so what you end up with is installed and running instead of pasted into a chat. Five questions, then it writes the file, installs it, tells you the path, and tests it in front of you so you see the trigger fire.

Get the starter →
One Time Automation. Automate it once. Own it forever.
Leo Chen builds AI operating systems and runs them across his own brokerage and agency.

← Back to the library