routine-from-chat

Featured

Turn a plain-language "do this automatically" request into a routine — either event-triggered ("text me when I get an email from my landlord") or scheduled ("remind me every Friday at 9am"). For third-party events (Gmail, GitHub, Slack…) it confirms with the guardian and then subscribes to the connector trigger so the event actually fires, even one that has never fired before. Ask for any missing detail, then confirm with a card. Reach for this first whenever the guardian wants something to happen automatically; do not explore the codebase or hand-build a trigger.

AI & Automation 488 stars 37 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Create a routine from chat When the guardian describes something they want to happen automatically, turn that intent into a **routine** — without making them learn event names, RRULEs, timezones, filters, or JSON. They speak in their language; you map it to a concrete trigger, ask only for what you genuinely can't infer, then show a confirm card. You do **not** create the routine yourself — the card creates it when they turn it on. A routine fires one of three ways. Decide which the request is: - **Event** — "when X happens": an email arrives, a payment lands, a form is submitted. Reactive, no fixed time. - **Schedule** — "at a time / on a cadence": "every Friday at 9am", "tomorrow at noon", "the 1st of each month", "every morning". - **Manual** — "save this so I can run it whenever": a playbook with **no** automatic trigger. the guardian runs it by hand from the Routines page's "Run now" button. If it's ambiguous ("remind me about the standup"), ask one short question to disambiguate before going further. In particular, if it's unclear whether they want it on a schedule or to run it by hand, ask. ## The flow 1. **Classify** the request as event, schedule, or manual (above). 2. **Resolve the trigger.** - *Manual:* nothing to resolve — there is no trigger to watch or time to compute. Skip straight to choosing the Then (the action it runs) and propose with `kind: "manual"`. No `eventName`, `tzid`, `rrule`, or `date`. - *Event from a third-party ...

Details

Author
rome-os
Repository
rome-os/rome
Created
2 weeks ago
Last Updated
today
Language
TypeScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category