Skip to content
Back to skills

Quantify Toil

ASecurity

Quantify manual toil and the automation ROI in engineer-hours per year. Reach for this on an automate-or-not question.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agents

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add mcorbett51090/RavenClaude --skill quantify-toil --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Quantify Toil?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Quantify Toil
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-quantify-toil/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-quantify-toil)

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

Download with Pro
SKILL.md
---
name: quantify-toil
description: "Quantify manual toil and the automation ROI in engineer-hours per year. Reach for this on an automate-or-not question."
---

# Skill: Quantify toil

Every recurring ticket is platform debt with a measurable cost (§3 #4).

## Step 1 — Inventory the task
Manual minutes per occurrence, frequency, and engineers affected.

## Step 2 — Compute hours/yr
minutes × frequency × engineers ÷ 60 via `platform_engineering_idp_calc.py toil` (§3 #4).

## Step 3 — Compare to build cost
Hours/yr saved vs the build-and-maintain cost of the self-service action.

## Step 4 — Rank against adoption
Prioritize toil on high-adoption paths, not rare edge cases (§3 #7).

## Output
A toil ROI read in engineer-hours/yr with the build-vs-buy-vs-leave call.

Attribution

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

Loading comments…