Skip to main content
agentsSource-backed

Claude Code Routine Designer Agent

Source-backed agent that designs safe recurring Claude Code routines, turning a repeated task into a well-scoped, idempotent skill-driven workflow with clear triggers, permissions, and reporting, grounded in the official Claude Code skills docs.

by JPette1783·added 2026-06-05·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://code.claude.com/docs/en/skills, https://github.com/JSONbored/awesome-claude/blob/main/content/agents/claude-code-routine-designer-agent.mdx
Safety notes
This agent designs the routine; running it on a schedule means it acts without a human present, so scope it tightly., Make routines idempotent and bounded so a repeated or retried run cannot cause cumulative damage., Keep destructive or far-reaching steps out of unattended routines, or gate them behind explicit confirmation and least-privilege permissions.
Privacy notes
A recurring routine repeatedly sends its context to the model provider; confirm that is acceptable for the data involved., Routine output and logs can accumulate; avoid writing secrets or sensitive data into them., Scope the routine's tools and file access to only what the task requires.
Author
JPette1783
Submitted by
JPette1783
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup.

0/3 ready
Permissions & scopes1General2

Safety & privacy surface

Safety & privacy surface

3 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes, third-party handling.

4 areas
  • SafetyPermissions & scopesThis agent designs the routine; running it on a schedule means it acts without a human present, so scope it tightly.
  • SafetyExecution & processesMake routines idempotent and bounded so a repeated or retried run cannot cause cumulative damage.
  • SafetyPermissions & scopesKeep destructive or far-reaching steps out of unattended routines, or gate them behind explicit confirmation and least-privilege permissions.
  • PrivacyThird-party handlingA recurring routine repeatedly sends its context to the model provider; confirm that is acceptable for the data involved.
  • PrivacyCredentials & tokensRoutine output and logs can accumulate; avoid writing secrets or sensitive data into them.
  • PrivacyPermissions & scopesScope the routine's tools and file access to only what the task requires.

Safety notes

  • This agent designs the routine; running it on a schedule means it acts without a human present, so scope it tightly.
  • Make routines idempotent and bounded so a repeated or retried run cannot cause cumulative damage.
  • Keep destructive or far-reaching steps out of unattended routines, or gate them behind explicit confirmation and least-privilege permissions.

Privacy notes

  • A recurring routine repeatedly sends its context to the model provider; confirm that is acceptable for the data involved.
  • Routine output and logs can accumulate; avoid writing secrets or sensitive data into them.
  • Scope the routine's tools and file access to only what the task requires.

Prerequisites

  • A repeated task you want to run on a schedule or trigger with Claude Code.
  • Knowledge of the inputs, outputs, and side effects of that task.
  • Ability to author a skill and set the permissions the routine needs.

Schema details

Install type
copy
Troubleshooting
No
Full copyable content
## Content

Claude Code Routine Designer Agent is a reusable agent prompt for turning a
repeated task into a safe recurring routine. It scopes the task, makes it
idempotent, defines triggers and least-privilege permissions, and decides what the
routine reports, so unattended runs stay predictable and safe.

Use it when you keep doing the same Claude Code task by hand and want to capture it
as a dependable routine instead of an ad-hoc prompt.

## Agent Prompt

You are a routine designer for Claude Code. Turn a repeated task into a safe,
bounded, recurring workflow. Use the official Claude Code skills documentation as
your reference, and design for unattended execution.

Design workflow:

1. Capture the task. State the goal, inputs, outputs, and side effects of the
   repeated task in plain terms.
2. Scope it. Define exactly which files, repos, and tools the routine may touch.
   Keep it narrow.
3. Make it idempotent. Ensure that running it twice, or retrying after a failure,
   does not cause cumulative or duplicate damage.
4. Encode it. Capture the steps as a skill so the procedure is reusable and loads
   on demand, rather than living in ad-hoc prompts.
5. Triggers and permissions. Define when it runs and the least-privilege
   permissions it needs. Keep destructive steps out or behind confirmation.
6. Reporting. Decide what a run reports (success, changes made, anomalies) so an
   absent human can review it later.
7. Failure handling. Define what happens on error: stop, retry safely, or
   escalate.

Output contract:

- Task definition: goal, inputs, outputs, side effects.
- Scope and least-privilege permissions.
- Idempotent step sequence captured as a skill.
- Trigger, reporting, and failure-handling plan.

## Features

- Converts a repeated task into a scoped, idempotent routine.
- Captures the procedure as a reusable skill.
- Defines triggers, least-privilege permissions, and reporting.
- Designs failure handling for unattended execution.

## Use Cases

- Turn a recurring maintenance task into a dependable routine.
- Make an automated job idempotent so retries are safe.
- Scope and permission a routine for unattended runs.
- Define what a routine reports for later human review.

## Source Notes

- Claude Code skills capture repeatable procedures in SKILL.md that load on demand
  and can be invoked or run automatically, which is the natural home for a routine.
- Permission modes and allow/deny rules define least-privilege execution, which is
  essential for routines that run without a human present.

## Duplicate Check

The content tree and open PRs were checked for routine, recurring task, and
scheduled workflow agents. No routine designer agent exists. This entry is
distinct: it is an `agents` prompt focused on designing safe recurring Claude Code
routines.

## Editorial Disclosure

Submitted as an independent community agent entry by `JPette1783`, based on
public Claude Code documentation. No paid placement, referral, or affiliate
relationship.

## Sources

- Claude Code skills documentation: https://code.claude.com/docs/en/skills
- Claude Code features overview: https://code.claude.com/docs/en/features-overview
- Claude Code MCP documentation: https://code.claude.com/docs/en/mcp

About this resource

Content

Claude Code Routine Designer Agent is a reusable agent prompt for turning a repeated task into a safe recurring routine. It scopes the task, makes it idempotent, defines triggers and least-privilege permissions, and decides what the routine reports, so unattended runs stay predictable and safe.

Use it when you keep doing the same Claude Code task by hand and want to capture it as a dependable routine instead of an ad-hoc prompt.

Agent Prompt

You are a routine designer for Claude Code. Turn a repeated task into a safe, bounded, recurring workflow. Use the official Claude Code skills documentation as your reference, and design for unattended execution.

Design workflow:

  1. Capture the task. State the goal, inputs, outputs, and side effects of the repeated task in plain terms.
  2. Scope it. Define exactly which files, repos, and tools the routine may touch. Keep it narrow.
  3. Make it idempotent. Ensure that running it twice, or retrying after a failure, does not cause cumulative or duplicate damage.
  4. Encode it. Capture the steps as a skill so the procedure is reusable and loads on demand, rather than living in ad-hoc prompts.
  5. Triggers and permissions. Define when it runs and the least-privilege permissions it needs. Keep destructive steps out or behind confirmation.
  6. Reporting. Decide what a run reports (success, changes made, anomalies) so an absent human can review it later.
  7. Failure handling. Define what happens on error: stop, retry safely, or escalate.

Output contract:

  • Task definition: goal, inputs, outputs, side effects.
  • Scope and least-privilege permissions.
  • Idempotent step sequence captured as a skill.
  • Trigger, reporting, and failure-handling plan.

Features

  • Converts a repeated task into a scoped, idempotent routine.
  • Captures the procedure as a reusable skill.
  • Defines triggers, least-privilege permissions, and reporting.
  • Designs failure handling for unattended execution.

Use Cases

  • Turn a recurring maintenance task into a dependable routine.
  • Make an automated job idempotent so retries are safe.
  • Scope and permission a routine for unattended runs.
  • Define what a routine reports for later human review.

Source Notes

  • Claude Code skills capture repeatable procedures in SKILL.md that load on demand and can be invoked or run automatically, which is the natural home for a routine.
  • Permission modes and allow/deny rules define least-privilege execution, which is essential for routines that run without a human present.

Duplicate Check

The content tree and open PRs were checked for routine, recurring task, and scheduled workflow agents. No routine designer agent exists. This entry is distinct: it is an agents prompt focused on designing safe recurring Claude Code routines.

Editorial Disclosure

Submitted as an independent community agent entry by JPette1783, based on public Claude Code documentation. No paid placement, referral, or affiliate relationship.

Sources

Source citations

Add this badge to your README

Show that Claude Code Routine Designer Agent is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/agents/claude-code-routine-designer-agent.svg)](https://heyclau.de/entry/agents/claude-code-routine-designer-agent)

How it compares

Claude Code Routine Designer Agent side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field

Source-backed agent that designs safe recurring Claude Code routines, turning a repeated task into a well-scoped, idempotent skill-driven workflow with clear triggers, permissions, and reporting, grounded in the official Claude Code skills docs.

Open dossier

Source-backed Claude Code subagent prompt for reviewing Agent Skills before adoption or publication, checking SKILL.md scope, descriptions, invocation control, supporting files, tool permissions, helpfulness, safety, and privacy risks against official Claude Code skills guidance.

Open dossier

An agent prompt for curating an organization's Agent Skills: reviewing each SKILL.md name and description, scope (personal, project, or plugin) and precedence, per-skill allowed-tools, and whether Claude or the user invokes it.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backed
SubmitterDiffersJPette1783Desel72JPette1783
Install riskReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand
Categoryagentsagentsagents
SourceSource-backedSource-backedSource-backed
AuthorJPette1783Desel72JPette1783
Added2026-06-052026-06-082026-06-05
Platforms
Harness
Source repo
Safety notesThis agent designs the routine; running it on a schedule means it acts without a human present, so scope it tightly. Make routines idempotent and bounded so a repeated or retried run cannot cause cumulative damage. Keep destructive or far-reaching steps out of unattended routines, or gate them behind explicit confirmation and least-privilege permissions.This agent reviews skill quality and adoption readiness; it does not execute the skill, install plugins, run scripts, or approve production rollout by itself. Flag skills that can perform writes, deployments, destructive actions, account changes, network calls, credential handling, or background automation without explicit user control. Recommend `disable-model-invocation: true`, least-privilege `allowed-tools`, or additional human review when a skill has side effects or could trigger too broadly. Treat supporting files, shell injection blocks, and bundled scripts as executable or instruction-bearing review surfaces, not harmless documentation.This agent curates and reviews skills; it does not execute them. Recommend tool restrictions (allowed-tools) for skills that touch sensitive actions, and invocation control for skills with side effects. Flag skills whose descriptions could cause the model to auto-invoke them in inappropriate contexts.
Privacy notesA recurring routine repeatedly sends its context to the model provider; confirm that is acceptable for the data involved. Routine output and logs can accumulate; avoid writing secrets or sensitive data into them. Scope the routine's tools and file access to only what the task requires.Reads local skill instructions and supporting files, which may expose internal workflow names, repository paths, policies, examples, customer data, or credentials accidentally written into prompts. Review output can mention sensitive skill names, tool permissions, file paths, dynamic commands, and risk findings; keep it out of public PR comments unless sanitized. Skills loaded by Claude can place their descriptions or full instructions into model context, so the review should flag secrets and unnecessary confidential details before adoption.Skill descriptions load each session; keep sensitive workflow detail and secrets out of them. Skills sourced from outside the org should be reviewed before adoption, since their instructions run in your sessions. Use settings-level overrides to hide or disable model-invocation of skills you did not author without editing their files.
Prerequisites
  • A repeated task you want to run on a schedule or trigger with Claude Code.
  • Knowledge of the inputs, outputs, and side effects of that task.
  • Ability to author a skill and set the permissions the routine needs.
  • One or more Agent Skill directories with a `SKILL.md` file and any referenced supporting files.
  • Access to the skill's intended user, task boundary, invocation path, and expected output.
  • A clear policy for whether the skill may be model-invoked automatically or must be user-invoked.
  • Permission to inspect tool restrictions, dynamic context commands, scripts, examples, templates, and bundled plugin metadata if present.
  • A set of Agent Skills (personal, project, or plugin) with their SKILL.md files.
  • Knowledge of which skills should be org-wide versus project-specific.
  • Ability to edit skill frontmatter and settings such as skill overrides.
Install
Config
Citations
ClaimUnclaimedUnclaimedUnclaimed
Open 3 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.