[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVSGTS3BSHMHQ3TMDAXRC2":3,"skill-same:01M7EVSGTS3BSHMHQ3TMDAXRC2":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EVSGTS3BSHMHQ3TMDAXRC2","ams-rote",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-rote\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rote\ndescription: 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.\ncategory: workflow-automation\n---\n\n# Rote\n\n## Overview\n\nRote work = repetitive, low-judgment tasks done the same way every time: data entry, reformatting, status copying, manual checks.\n\nIt's the highest-ROI automation target: frequent, well-defined, and currently eating human hours that could create value.\n\nThe rote method: inventory it, measure it, then eliminate (automate, delegate, or delete) — in that order of preference.\n\n## When to use\n\n- Days filled with repetitive manual tasks\n- Teams doing the same data shuffling weekly\n- Finding automation opportunities systematically\n- Building a personal or team leverage habit\n- Deciding what to automate first\n\n## Core concepts\n\n- **Rote inventory.**\n  For two weeks, log every repetitive task: what, how often, how long, how error-prone. The inventory is the opportunity map.\n- **Cost math.**\n  Frequency x duration x (1 + error cost). A 10-min daily task = 40+ hrs\u002Fyear. Rote work is expensive in aggregate — make the cost visible.\n- **Eliminate first.**\n  Before automating: can it be deleted? Can the process change so the task vanishes? The best automation is elimination.\n- **Automate second.**\n  If it must exist: script it, template it, or flow it. Match tool to complexity; timebox the build.\n- **Delegate third.**\n  If it needs a human but not you: delegate with a checklist\u002FSOP. Delegation without documentation just moves the pain.\n- **SOPs for the remainder.**\n  Rote work that stays manual gets a checklist\u002FSOP: consistent, delegable, improvable. Undocumented rote is fragile rote.\n- **Leverage habit.**\n  Weekly: 'what did I do repetitively this week?' Monthly automation hour. Leverage compounds like interest.\n- **Error cost.**\n  Rote work isn't just slow — it's error-prone. Factor mistake cost (wrong data sent, missed step) into the automation case.\n\n## Practical workflow\n\n1. **Run the inventory.**\n   Two weeks logging repetitive tasks: task, frequency, minutes, errors. No judgment, just data.\n2. **Do the cost math.**\n   Annualize each: frequency x duration. Sort by cost. The top 5 are your automation backlog.\n3. **Eliminate.**\n   For each top item: can it die? Challenge the process — many rote tasks exist from inertia, not need.\n4. **Automate the survivors.**\n   Pick the top 2-3. Timebox builds. Ship the simple version; iterate only if it earns it.\n5. **Document the rest.**\n   Remaining manual rote gets SOPs\u002Fchecklists. 10 minutes documenting saves hours of re-teaching.\n6. **Build the habit.**\n   Weekly 15-min review: new rote spotted? Monthly automation hour: kill one item from the backlog.\n7. **Share wins.**\n   Show the team what got eliminated and the hours saved. Leverage culture spreads by example.\n8. **Re-inventory quarterly.**\n   New rote creeps in constantly. Quarterly inventory keeps the backlog honest and the habit alive.\n\n## Common pitfalls\n\n- **Automating before eliminating.**\n  Building elaborate automation for a task that could simply stop. Delete first, always.\n- **No inventory.**\n  'Automate things' without knowing what the rote work actually is. The inventory directs effort to real costs.\n- **Gold-plating.**\n  Spending 20 hours automating a 5-min monthly task. Cost math first; timebox the build.\n- **Automating judgment work.**\n  Rote = low judgment. Automating decisions that need human nuance creates confident, fast mistakes.\n- **Undocumented delegation.**\n  Handing rote to someone without SOPs. Delegation without documentation is just relocated suffering.\n- **One-time automation theater.**\n  Automating something done twice a year. The inventory's frequency column prevents this.\n- **Ignoring error costs.**\n  Counting only time saved, not mistakes prevented. Error reduction often exceeds time savings in value.\n- **Leverage guilt.**\n  Feeling bad about 'not doing real work' while automating. Eliminating rote IS real work — it's leverage.\n","# Rote\n\n## Overview\n\nRote work = repetitive, low-judgment tasks done the same way every time: data entry, reformatting, status copying, manual checks.\n\nIt's the highest-ROI automation target: frequent, well-defined, and currently eating human hours that could create value.\n\nThe rote method: inventory it, measure it, then eliminate (automate, delegate, or delete) — in that order of preference.\n\n## When to use\n\n- Days filled with repetitive manual tasks\n- Teams doing the same data shuffling weekly\n- Finding automation opportunities systematically\n- Building a personal or team leverage habit\n- Deciding what to automate first\n\n## Core concepts\n\n- **Rote inventory.**\n  For two weeks, log every repetitive task: what, how often, how long, how error-prone. The inventory is the opportunity map.\n- **Cost math.**\n  Frequency x duration x (1 + error cost). A 10-min daily task = 40+ hrs\u002Fyear. Rote work is expensive in aggregate — make the cost visible.\n- **Eliminate first.**\n  Before automating: can it be deleted? Can the process change so the task vanishes? The best automation is elimination.\n- **Automate second.**\n  If it must exist: script it, template it, or flow it. Match tool to complexity; timebox the build.\n- **Delegate third.**\n  If it needs a human but not you: delegate with a checklist\u002FSOP. Delegation without documentation just moves the pain.\n- **SOPs for the remainder.**\n  Rote work that stays manual gets a checklist\u002FSOP: consistent, delegable, improvable. Undocumented rote is fragile rote.\n- **Leverage habit.**\n  Weekly: 'what did I do repetitively this week?' Monthly automation hour. Leverage compounds like interest.\n- **Error cost.**\n  Rote work isn't just slow — it's error-prone. Factor mistake cost (wrong data sent, missed step) into the automation case.\n\n## Practical workflow\n\n1. **Run the inventory.**\n   Two weeks logging repetitive tasks: task, frequency, minutes, errors. No judgment, just data.\n2. **Do the cost math.**\n   Annualize each: frequency x duration. Sort by cost. The top 5 are your automation backlog.\n3. **Eliminate.**\n   For each top item: can it die? Challenge the process — many rote tasks exist from inertia, not need.\n4. **Automate the survivors.**\n   Pick the top 2-3. Timebox builds. Ship the simple version; iterate only if it earns it.\n5. **Document the rest.**\n   Remaining manual rote gets SOPs\u002Fchecklists. 10 minutes documenting saves hours of re-teaching.\n6. **Build the habit.**\n   Weekly 15-min review: new rote spotted? Monthly automation hour: kill one item from the backlog.\n7. **Share wins.**\n   Show the team what got eliminated and the hours saved. Leverage culture spreads by example.\n8. **Re-inventory quarterly.**\n   New rote creeps in constantly. Quarterly inventory keeps the backlog honest and the habit alive.\n\n## Common pitfalls\n\n- **Automating before eliminating.**\n  Building elaborate automation for a task that could simply stop. Delete first, always.\n- **No inventory.**\n  'Automate things' without knowing what the rote work actually is. The inventory directs effort to real costs.\n- **Gold-plating.**\n  Spending 20 hours automating a 5-min monthly task. Cost math first; timebox the build.\n- **Automating judgment work.**\n  Rote = low judgment. Automating decisions that need human nuance creates confident, fast mistakes.\n- **Undocumented delegation.**\n  Handing rote to someone without SOPs. Delegation without documentation is just relocated suffering.\n- **One-time automation theater.**\n  Automating something done twice a year. The inventory's frequency column prevents this.\n- **Ignoring error costs.**\n  Counting only time saved, not mistakes prevented. Error reduction often exceeds time savings in value.\n- **Leverage guilt.**\n  Feeling bad about 'not doing real work' while automating. Eliminating rote IS real work — it's leverage.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-rote",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-rote",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-rote",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-rote","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-rote\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]