Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Rote

ASecurity

Eliminate rote work: identify repetitive tasks, measure their cost, and automate or remove them systematically. Use when drowning in repetitive busywork or building a culture of leverage.

2 stars
0 votes
0 copies
1 views
Added 9/29/2026
ai-agentsgodocumentation

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill rote --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Rote?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Rote
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-rote/badge)](https://www.skillsdirectory.com/skills/aicodedecode-rote)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: rote
description: Eliminate rote work: identify repetitive tasks, measure their cost, and automate or remove them systematically. Use when drowning in repetitive busywork or building a culture of leverage.
category: workflow-automation
---

# Rote

## Overview

Rote work = repetitive, low-judgment tasks done the same way every time: data entry, reformatting, status copying, manual checks.

It's the highest-ROI automation target: frequent, well-defined, and currently eating human hours that could create value.

The rote method: inventory it, measure it, then eliminate (automate, delegate, or delete) — in that order of preference.

## When to use

- Days filled with repetitive manual tasks
- Teams doing the same data shuffling weekly
- Finding automation opportunities systematically
- Building a personal or team leverage habit
- Deciding what to automate first

## Core concepts

- **Rote inventory.**
  For two weeks, log every repetitive task: what, how often, how long, how error-prone. The inventory is the opportunity map.
- **Cost math.**
  Frequency x duration x (1 + error cost). A 10-min daily task = 40+ hrs/year. Rote work is expensive in aggregate — make the cost visible.
- **Eliminate first.**
  Before automating: can it be deleted? Can the process change so the task vanishes? The best automation is elimination.
- **Automate second.**
  If it must exist: script it, template it, or flow it. Match tool to complexity; timebox the build.
- **Delegate third.**
  If it needs a human but not you: delegate with a checklist/SOP. Delegation without documentation just moves the pain.
- **SOPs for the remainder.**
  Rote work that stays manual gets a checklist/SOP: consistent, delegable, improvable. Undocumented rote is fragile rote.
- **Leverage habit.**
  Weekly: 'what did I do repetitively this week?' Monthly automation hour. Leverage compounds like interest.
- **Error cost.**
  Rote work isn't just slow — it's error-prone. Factor mistake cost (wrong data sent, missed step) into the automation case.

## Practical workflow

1. **Run the inventory.**
   Two weeks logging repetitive tasks: task, frequency, minutes, errors. No judgment, just data.
2. **Do the cost math.**
   Annualize each: frequency x duration. Sort by cost. The top 5 are your automation backlog.
3. **Eliminate.**
   For each top item: can it die? Challenge the process — many rote tasks exist from inertia, not need.
4. **Automate the survivors.**
   Pick the top 2-3. Timebox builds. Ship the simple version; iterate only if it earns it.
5. **Document the rest.**
   Remaining manual rote gets SOPs/checklists. 10 minutes documenting saves hours of re-teaching.
6. **Build the habit.**
   Weekly 15-min review: new rote spotted? Monthly automation hour: kill one item from the backlog.
7. **Share wins.**
   Show the team what got eliminated and the hours saved. Leverage culture spreads by example.
8. **Re-inventory quarterly.**
   New rote creeps in constantly. Quarterly inventory keeps the backlog honest and the habit alive.

## Common pitfalls

- **Automating before eliminating.**
  Building elaborate automation for a task that could simply stop. Delete first, always.
- **No inventory.**
  'Automate things' without knowing what the rote work actually is. The inventory directs effort to real costs.
- **Gold-plating.**
  Spending 20 hours automating a 5-min monthly task. Cost math first; timebox the build.
- **Automating judgment work.**
  Rote = low judgment. Automating decisions that need human nuance creates confident, fast mistakes.
- **Undocumented delegation.**
  Handing rote to someone without SOPs. Delegation without documentation is just relocated suffering.
- **One-time automation theater.**
  Automating something done twice a year. The inventory's frequency column prevents this.
- **Ignoring error costs.**
  Counting only time saved, not mistakes prevented. Error reduction often exceeds time savings in value.
- **Leverage guilt.**
  Feeling bad about 'not doing real work' while automating. Eliminating rote IS real work — it's leverage.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →