RoutineOSBeta
Templates

Ten Claude Code templates, ten with their own page.

These are Claude Code templates for routines: ready one-file packs for jobs, mail, meetings, invoices and more. Each one is built to start report-only (by design, checked by the installer and validator), so you read a first report before it is allowed to send, post or delete anything.

2 piloted8 unpilotedMIT licence
Pick by role

All ten templates, by role

Jump to a role, or scroll. Piloted means a real run checked it. Unpiloted means it passed validation but has not run for real, and each page says so. The three that point to the docs have no page here yet.

Sales

Support

Finance

Recruiting

Content

Dev

Marketing

General

Install

Install a template

  1. Install the pluginIn Claude Code 2.1.275 or later. The command line tool needs Python 3.11 or later.
    /plugin install routineos --marketplace devkindhq/routineos
  2. See the listFrom a clone of the repository root.
    python3 skills/routineos/scripts/routineos.py pack list catalog/index.json
  3. Install oneSwap the file name for any template in the list. It writes a routine folder and prints what you must connect.
    python3 skills/routineos/scripts/routineos.py pack install catalog/jobs-watch.json --dir my-jobs-watch
What a pack is

One file holds the whole routine

A pack is one JSON file. It holds the routine's settings, its prompt, its README, the definition of what it records, the stages it runs, the connectors it needs and, where the routine has them, helper scripts and skills. You can check it before you install it.

Read the pack schema for every key, or Templates and packs in the docs.

What a pack never does

Safe to try

  • Never runs code when you install it.
  • Never holds a secret or an email address.
  • Never ships with a live first run. A person switches a routine live.
  • Never overwrites an existing folder.
Already in n8n?

Convert an n8n template instead

If you already use n8n templates or have your own n8n workflow, you can turn it into a routine pack. Windmill flows convert too. Zapier is guided from a description of the Zap, not converted. The result is a pack plus a migration report.

Read the migrate guide.

Write your own

Make a template for your team

Any routine folder can be exported as a pack, and any pack can be installed by someone else. Authoring a template and Writing a pack show how.

Start with one, report-only.

Install RoutineOS, pick a template, and read one run before you let it act.