Menu

1 / 2

Skills Were Dead Prompts. Routines Made Them Alive.

DEV Community·Alfredo Izquierdo·6 months ago
#rokzWRhz
#ai#automation#skill#routines#cron
Reading 0:00
15s threshold

A few weeks ago I shipped Skills — a way to save AI prompts as reusable templates inside ContextForge , so my best prompts wouldn't keep dying in a Notion page nobody opens.

It worked. I stopped losing them.

Then I noticed something worse.

I had a Skill that drafts marketing copy every time we ship a feature. Another that summarizes my weekly progress. Another that generates LinkedIn posts. They were all sitting there, clean and named, in a tab I'd open every Monday morning and slowly click "Run" on like a factory line.

That's when it hit me: I built a library, not an assistant. Skills were just dead prompts with a database row.

So I built Routines.

What a Routine actually is

A Routine is a Skill on a cron expression. That's it.

You pick a Skill (the prompt template). You pick a schedule — daily , weekly , monthly , or any 5-field cron you write yourself. You pass the input variables. You hit Create.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.