Agent skill

Routines

by Yesterday-AI in Yesterday-AI/paperclip-plugin-company-wizard

Set up and manage Paperclip Routines — recurring scheduled tasks that replace expensive always-on heartbeats.

MITAuto-check passedProductivity & Automation

Install Routines

skills CLI

$ npx skills add Yesterday-AI/paperclip-plugin-company-wizard --skill routines -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Yesterday-AI/paperclip-plugin-company-wizard routines --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Yesterday-AI/paperclip-plugin-company-wizard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/routines .claude/skills/routines && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "routines" agent skill from https://github.com/Yesterday-AI/paperclip-plugin-company-wizard/tree/main/.claude/skills/routines into .claude/skills/routines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "routines", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Yesterday-AI/paperclip-plugin-company-wizard/tree/main/.claude/skills/routines

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Yesterday-AI/paperclip-plugin-company-wizard --skill routines -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Yesterday-AI/paperclip-plugin-company-wizard routines --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Yesterday-AI/paperclip-plugin-company-wizard.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/routines .agents/skills/routines && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "routines" agent skill from https://github.com/Yesterday-AI/paperclip-plugin-company-wizard/tree/main/.claude/skills/routines into .agents/skills/routines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "routines", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Yesterday-AI/paperclip-plugin-company-wizard --skill routines -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Yesterday-AI/paperclip-plugin-company-wizard routines --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Yesterday-AI/paperclip-plugin-company-wizard.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/routines .cursor/skills/routines && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "routines" agent skill from https://github.com/Yesterday-AI/paperclip-plugin-company-wizard/tree/main/.claude/skills/routines into .cursor/skills/routines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "routines", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Yesterday-AI/paperclip-plugin-company-wizard.git --path .claude/skills/routines

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Yesterday-AI/paperclip-plugin-company-wizard --skill routines -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Yesterday-AI/paperclip-plugin-company-wizard routines --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Yesterday-AI/paperclip-plugin-company-wizard.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/routines .gemini/skills/routines && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "routines" agent skill from https://github.com/Yesterday-AI/paperclip-plugin-company-wizard/tree/main/.claude/skills/routines into .gemini/skills/routines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "routines", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Yesterday-AI/paperclip-plugin-company-wizard routines

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Yesterday-AI/paperclip-plugin-company-wizard --skill routines -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Yesterday-AI/paperclip-plugin-company-wizard.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/routines .github/skills/routines && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "routines" agent skill from https://github.com/Yesterday-AI/paperclip-plugin-company-wizard/tree/main/.claude/skills/routines into .github/skills/routines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "routines", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Yesterday-AI/paperclip-plugin-company-wizard --skill routines -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Yesterday-AI/paperclip-plugin-company-wizard routines --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Yesterday-AI/paperclip-plugin-company-wizard.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/routines .opencode/skills/routines && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "routines" agent skill from https://github.com/Yesterday-AI/paperclip-plugin-company-wizard/tree/main/.claude/skills/routines into .opencode/skills/routines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "routines", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: routines
GitHub stars: 186
Token cost: ~2.1k tokens
SKILL.md length: 567 words
Files: 1
Skills in repo: 4
Repo updated: Apr 22, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Set up and manage Paperclip Routines — recurring scheduled tasks that replace expensive always-on heartbeats.

Works in 5 steps: Find your IDs → Create a routine → Add a cron trigger → …
Create cron-based
SKILL.md covers Why Routines > Always-On…, Quick Start, Suggested Routine Patterns and Concurrency Policies, plus 6 more sections
Calls curl and jq; needs PAPERCLIP_API_KEY

What it does

Routines is an agent skill from Yesterday-AI/paperclip-plugin-company-wizard. Set up and manage Paperclip Routines — recurring scheduled tasks that replace expensive always-on heartbeats. Use to create cron-based, webhook-triggered, or API-triggered routines for agents, reducing token spend while keeping agents responsive. Covers routine CRUD, triggers, concurrency policies, and suggested routine patterns for common agent roles.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Scheduled and recurring tasks, Webhooks and Multi-agent orchestration. The repository describes itself as: Bootstrap AI agent companies from modular templates. The licence is MIT.

When your agent uses it

Create cron-based
Webhook-triggered
API-triggered routines for agents
Reducing token spend while keeping agents responsive

Example prompts

“/routines”

Requirements

A credential in PAPERCLIP_API_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Find your IDs
Create a routine
Add a cron trigger
Or add a webhook trigger (for external events)
Manual run (testing)

What it can do on your machine

Read from SKILL.md and the folder at commit 3eeca7d. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- curl
- jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- PAPERCLIP_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Routines loads about 2.1k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 567 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~91
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Yesterday-AI/paperclip-plugin-company-wizard at commit 3eeca7d, republished under its MIT licence (© Yesterday-AI). 567 words, ~2,084 tokens.

Download SKILL.mdSave it as .claude/skills/routines/SKILL.md (or your agent's skills folder).

name: routines
description: Set up and manage Paperclip Routines — recurring scheduled tasks that replace expensive always-on heartbeats. Use to create cron-based, webhook-triggered, or API-triggered routines for agents, reducing token spend while keeping agents responsive. Covers routine CRUD, triggers, concurrency policies, and suggested routine patterns for common agent roles.

Routines — Recurring Agent Tasks

Routines are Paperclip's scheduling primitive. Instead of agents burning tokens on timer heartbeats polling for work, routines fire only when needed — on a cron schedule, webhook, or explicit API call — and create a targeted heartbeat run for the assigned agent.

Why Routines > Always-On Heartbeats

Approach	Token cost	Responsiveness
Heartbeat every 5 min	~288 runs/day, most idle	High but wasteful
Routines (cron + webhook)	Only fires when scheduled or triggered	Same responsiveness, fraction of the cost

The key insight: clean up heartbeats = token reducing = cheaper.

Quick Start

1. Find your IDs

bash

# Company ID
curl -s "$PAPERCLIP_API_URL/api/agents/me" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" | jq '.companyId, .id'

# Agents in company
curl -s "$PAPERCLIP_API_URL/api/companies/{companyId}/agents" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" | jq '.[] | {id, name, role}'

# Projects
curl -s "$PAPERCLIP_API_URL/api/companies/{companyId}/projects" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" | jq '.[] | {id, name}'

2. Create a routine

bash

curl -s -X POST "$PAPERCLIP_API_URL/api/companies/{companyId}/routines" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Daily standup check",
    "description": "CEO reviews all in_progress issues and nudges stalled agents",
    "assigneeAgentId": "{ceo-agent-id}",
    "projectId": "{project-id}",
    "priority": "medium",
    "status": "active",
    "concurrencyPolicy": "skip_if_active",
    "catchUpPolicy": "skip_missed"
  }'

3. Add a cron trigger

bash

curl -s -X POST "$PAPERCLIP_API_URL/api/routines/{routineId}/triggers" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "schedule",
    "cronExpression": "0 9 * * 1-5",
    "timezone": "Europe/Amsterdam"
  }'

4. Or add a webhook trigger (for external events)

bash

curl -s -X POST "$PAPERCLIP_API_URL/api/routines/{routineId}/triggers" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "webhook",
    "signingMode": "bearer"
  }'

The response includes a publicId and signing secret. External systems POST to: POST /api/routine-triggers/public/{publicId}/fire

5. Manual run (testing)

bash

curl -s -X POST "$PAPERCLIP_API_URL/api/routines/{routineId}/run" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"source": "manual"}'

Suggested Routine Patterns

CEO Agent

Routine	Schedule	Why
Morning standup	`0 9 * * 1-5`	Review stalled issues, nudge idle agents, check backlog health
End-of-day wrap	`0 17 * * 1-5`	Summarize progress, update roadmap, plan tomorrow
Weekly retro	`0 10 * * 1`	Run retrospective, check velocity trends
Backlog grooming	`0 14 * * 3`	Ensure 3+ unassigned issues exist, create from roadmap if needed

Engineer Agent

Routine	Schedule	Why
PR check	`0 /4 * 1-5`	Check for review comments, merge approved PRs
CI/deploy monitor	webhook	Trigger on GitHub Actions / Railway deploy events
Dependency audit	`0 10 * * 1`	Weekly check for outdated/vulnerable deps

PM Agent

Routine	Schedule	Why
Triage new issues	`0 9,14 * * 1-5`	Prioritize and assign incoming issues
Sprint review	`0 16 * * 5`	Friday sprint summary
Stakeholder update	`0 11 * * 3`	Mid-week status digest

Cross-cutting

Routine	Schedule	Why
GitHub webhook relay	webhook	On push/PR events, wake the engineer
Sentry/error alert relay	webhook	On new error, wake the engineer
Daily backup verification	`0 3 * * *`	Verify latest DB backup is fresh

Concurrency Policies

Choose based on routine behavior:

Policy	Use when
`coalesce_if_active` (default)	Idempotent checks — if agent is already running, the new trigger adds nothing
`skip_if_active`	Same as coalesce but cleaner — just drop it
`always_enqueue`	Every trigger matters (e.g., each webhook payload is unique work)

Show full SKILL.md (232 more words)Show less

Catch-Up Policies

Policy	Use when
`skip_missed` (default)	Agent was down; the missed check isn't worth running late
`enqueue_missed_with_cap`	Missed runs should still execute (e.g., missed deploy checks)

Managing Routines

bash

# List all routines
curl -s "$PAPERCLIP_API_URL/api/companies/{companyId}/routines" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" | jq '.[] | {id, title, status, assigneeAgentId}'

# Pause a routine
curl -s -X PATCH "$PAPERCLIP_API_URL/api/routines/{routineId}" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status": "paused"}'

# Resume
curl -s -X PATCH "$PAPERCLIP_API_URL/api/routines/{routineId}" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status": "active"}'

# Archive (permanent)
curl -s -X PATCH "$PAPERCLIP_API_URL/api/routines/{routineId}" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status": "archived"}'

# Check run history
curl -s "$PAPERCLIP_API_URL/api/routines/{routineId}/runs?limit=10" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" | jq '.[] | {id, status, createdAt}'

# Update trigger schedule
curl -s -X PATCH "$PAPERCLIP_API_URL/api/routine-triggers/{triggerId}" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"cronExpression": "0 10 * * 1-5"}'

# Disable a trigger without deleting
curl -s -X PATCH "$PAPERCLIP_API_URL/api/routine-triggers/{triggerId}" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"enabled": false}'

# Delete a trigger
curl -s -X DELETE "$PAPERCLIP_API_URL/api/routine-triggers/{triggerId}" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY"

Webhook Integration Examples

GitHub → Engineer wake on push

Create routine with webhook trigger
In GitHub repo settings → Webhooks, add:
- URL: {PAPERCLIP_PUBLIC_URL}/api/routine-triggers/public/{publicId}/fire
- Content type: application/json
- Events: Push, Pull request
- Secret: the signing secret from trigger creation

Railway → Engineer wake on deploy

Same pattern — Railway supports deploy webhooks that POST to your routine trigger URL.

Agent Access Rules

Operation	Agent (own)	Agent (other)	Board
List / Get	yes	yes (read-only)	yes
Create	yes (self-assign only)	no	yes
Update	yes	no	yes
Triggers CRUD	yes	no	yes
Manual run	yes	no	yes
Reassign	no	no	yes

Migration: Heartbeat → Routines

To convert an always-on heartbeat agent to routine-based:

Identify the agent's recurring tasks from their HEARTBEAT.md
Create a routine for each distinct recurring concern (standup, triage, deploy check, etc.)
Add appropriate triggers — cron for time-based, webhook for event-based
Reduce or stop the heartbeat interval — routines handle the scheduling now
Keep one low-frequency fallback heartbeat (e.g., every 2 hours) as a safety net for anything routines don't cover
Monitor run history to verify routines fire correctly before fully removing heartbeats

Full API Reference

See skills/paperclip/references/api-reference.md for the complete endpoint list and the Routines API doc at docs/api/routines.md in the Paperclip source.

Files

Just SKILL.md in .claude/skills/routines of Yesterday-AI/paperclip-plugin-company-wizard.

Open the folder on GitHubat commit 3eeca7d

Compare with similar skills

Routines next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Routines compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Routines this skillYesterday-AI/paperclip-plugin-company-wizard	186	—	~2.1k	Automated safety check: Pass	MIT	5 mo ago
Kandev Routineskdlbs/kandev	917	—	~493	Automated safety check: Pass	AGPL-3.0	today
N8n Workflowsvibeeval/vibecosystem	532	—	~3.3k	Automated safety check: Pass	MIT	2 mo ago
N8n Workflow Patternsdavila7/claude-code-templates	33k	1 repos	~2.8k	Automated safety check: Pass	MIT	yesterday
Team BuilderLeoYeAI/openclaw-master-skills	2.2k	—	~5.7k	Automated safety check: Pass	MIT	2 mo ago
Openhands AutomationOpenHands/extensions	163	—	~12k	Automated safety check: Pass	MIT	yesterday

Similar skills

Kandev Routines
kdlbs/kandev
Create, inspect, pause, resume, or delete recurring Office routines when work should run on a cron schedule or webhook trigger.
917 GitHub stars~493 tokensUpdated today
Productivity & AutomationAuto-check passed
N8n Workflows
vibeeval/vibecosystem
n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.
532 GitHub stars~3.3k tokensUpdated 2 mo ago
Productivity & AutomationAuto-check passed
N8n Workflow Patterns
davila7/claude-code-templates
Proven workflow architectural patterns from real n8n workflows.
33k GitHub starsUsed in 1 repo~2.8k tokens
Productivity & AutomationAuto-check passed
Team Builder
LeoYeAI/openclaw-master-skills
Deploy a multi-agent SaaS growth team on OpenClaw with shared workspace, async inbox communication, cron-scheduled tasks, deep project code scanning (Deep Dive), and optional Telegram integration.
2.2k GitHub stars~5.7k tokensUpdated 2 mo ago
Productivity & AutomationAuto-check passed
Openhands Automation
OpenHands/extensions
This skill should be used when the user asks to "create an automation", "schedule a task", "set up a cron job", "webhook integration", "event-triggered automation", or mentions automations…
163 GitHub stars~12k tokensUpdated yesterday
Productivity & AutomationAuto-check passed
n8n Workflow Patterns
czlonkowski/n8n-skills
Architecture patterns for n8n workflows covering webhooks, HTTP APIs, databases, AI agents, scheduled jobs and batch processing, with advice on choosing between them.
6.4k GitHub stars~5.1k tokensUpdated 2 days ago
Productivity & AutomationAuto-check passed

More from Yesterday-AI/paperclip-plugin-company-wizard

Paperclip AI
Yesterday-AI/paperclip-plugin-company-wizard
Manage Paperclip AI companies, agents, issues, projects, goals, routines, costs, and secrets via REST API.
186 GitHub stars~2.5k tokensUpdated 5 mo ago
Auto-check passed
Release
Yesterday-AI/paperclip-plugin-company-wizard
Prepare a new release by updating CHANGELOG.md, verifying documentation (README.md, CLAUDE.md, AGENTS.md, ROADMAP.md, docs/), bumping patch version in package.json, building, and suggesting publish…
186 GitHub stars~1.6k tokensUpdated 5 mo ago
Auto-check passed
Setup Routines
Yesterday-AI/paperclip-plugin-company-wizard
Analyze a Paperclip company's issue history, agent health, recurring failure patterns, and project architecture to design and provision tailored routines with cron/webhook triggers.
186 GitHub stars~3.1k tokensUpdated 5 mo ago
Auto-check passed

Questions about Routines

What does Routines do?

Set up and manage Paperclip Routines — recurring scheduled tasks that replace expensive always-on heartbeats. Routines is an agent skill from Yesterday-AI/paperclip-plugin-company-wizard. Set up and manage Paperclip Routines — recurring scheduled tasks that replace expensive always-on heartbeats.

When should I use Routines?

Routines fits situations like: create cron-based; webhook-triggered; API-triggered routines for agents; reducing token spend while keeping agents responsive.

How do I install Routines in Claude Code?

Run `npx skills add Yesterday-AI/paperclip-plugin-company-wizard --skill routines -a claude-code`. Or copy the skill folder (.claude/skills/routines in Yesterday-AI/paperclip-plugin-company-wizard) into .claude/skills/routines in your project. Claude Code loads it when a task matches its description.

How do I install Routines in Codex?

Run `npx skills add Yesterday-AI/paperclip-plugin-company-wizard --skill routines -a codex`. Or copy the skill folder (.claude/skills/routines in Yesterday-AI/paperclip-plugin-company-wizard) into .agents/skills/routines in your project. Codex loads it when a task matches its description.

Can I use Routines in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Yesterday-AI/paperclip-plugin-company-wizard --skill routines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/routines, .gemini/skills/routines, .github/skills/routines and .opencode/skills/routines in your project.

What does Routines need to run?

Going by SKILL.md and its folder, Routines needs the command-line tools its instructions call (curl and jq) and credentials named PAPERCLIP_API_KEY. Our summary lists: A credential in PAPERCLIP_API_KEY.

Does Routines access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Routines safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Routines use?

Routines is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Routines use?

About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Routines?

Skills that share tags, products or a category with Routines: Kandev Routines (kdlbs/kandev, 917 stars), N8n Workflows (vibeeval/vibecosystem, 532 stars), N8n Workflow Patterns (davila7/claude-code-templates, 33k stars) and Team Builder (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Routines?

Yesterday-AI (a GitHub organization) maintains it in Yesterday-AI/paperclip-plugin-company-wizard, which has 186 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on April 22, 2026.

Source: Yesterday-AI/paperclip-plugin-company-wizard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Routines

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Routines — Recurring Agent Tasks

Why Routines > Always-On Heartbeats

Quick Start

1. Find your IDs

2. Create a routine

3. Add a cron trigger

4. Or add a webhook trigger (for external events)

5. Manual run (testing)

Suggested Routine Patterns

CEO Agent

Engineer Agent

PM Agent

Cross-cutting

Concurrency Policies

Catch-Up Policies

Managing Routines

Webhook Integration Examples

GitHub → Engineer wake on push

Railway → Engineer wake on deploy

Agent Access Rules

Migration: Heartbeat → Routines

Full API Reference

Files

Compare with similar skills

Similar skills

More from Yesterday-AI/paperclip-plugin-company-wizard

Related

Questions about Routines