# Templates Source: https://routineos.org/templates > Ten Claude Code templates as one-file packs: jobs watch, inbox triage, meeting brief, invoice exceptions and more. Each starts report-only. 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. [Get started](https://routineos.org/#start)[Install a template](#install) 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 [ ### Jobs watch Tracks public job postings for commerce and automation roles, links each role to its company, and puts the few that need a person in the Inbox. Needs: Web search, Web fetch pilotedwatch Open ](https://routineos.org/templates/jobs-watch) [ ### Meeting brief Before each outside meeting, researches the other company and writes a short, cited brief to the Desk. Needs: Calendar, Web search, Web fetch unpilotedwatch Open ](https://routineos.org/templates/meeting-brief) Support [ ### Inbox triage Labels new mail threads, drafts replies in your style, and sends a reply only after a person approves it. Needs: Mail (read) unpilotedapproval-gated Open ](https://routineos.org/templates/inbox-triage) [ ### Support gap digest Each week, groups repeated support questions and flags the ones your help pages do not answer yet. Needs: Help desk, Web fetch unpilotedwatch Read in the docs ](https://routineos.org/templates/support-gap-digest) Finance [ ### Invoice exceptions Reads incoming invoices and flags duplicates, large amounts and new vendors for a person to check. The prompt forbids paying. Needs: Invoice mailbox or folder unpilotedwatch Open ](https://routineos.org/templates/invoice-exceptions) Recruiting [ ### Candidate shortlist Scores new applicants against your rubric with evidence per criterion and suggests a shortlist. The prompt forbids rejecting anyone. Needs: Applicant tracking system unpilotedwatch Open ](https://routineos.org/templates/candidate-shortlist) Content [ ### Content calendar Drafts cited posts from your topics and sources in your house style, and holds each draft for a person to approve. Needs: Web search, Web fetch unpilotedapproval-gated Open ](https://routineos.org/templates/content-calendar) Dev [ ### Engineering digest A daily digest of open pull requests, issues and failing builds, with the stale ones flagged. Needs: Code host unpilotedwatch Read in the docs ](https://routineos.org/templates/engineering-digest) Marketing [ ### Weekly marketing report Each week, compares marketing metrics with the week before, audits a few key pages, and flags big moves. Needs: Analytics and ad platforms unpilotedwatch Read in the docs ](https://routineos.org/templates/weekly-marketing-report) General [ ### Watch (generic) Watches a list of sources for new and changed items and writes one report per run, even in a quiet week. Needs: Web fetch pilotedwatch Open ](https://routineos.org/templates/watch) Install ## Install a template 1. **Install the plugin**In 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 list**From a clone of the repository root. `python3 skills/routineos/scripts/routineos.py pack list catalog/index.json` 3. **Install one**Swap 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](https://docs.routineos.org/reference/pack-schema) for every key, or [Templates and packs](https://docs.routineos.org/templates) 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](https://docs.routineos.org/guides/migrate). 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](https://docs.routineos.org/templates/authoring) and [Writing a pack](https://docs.routineos.org/templates/writing-a-pack) show how. ## Start with one, report-only. Install RoutineOS, pick a template, and read one run before you let it act. [Get started](https://routineos.org/#start)[Read the docs](https://docs.routineos.org)