Skip to content
Back to skills

Read Unit Economics

ASecurity

Compute cost per customer/transaction/feature and read the trend, not the gross bill. Reach for this on a scaling-health 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 read-unit-economics --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Read Unit Economics?

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

Security grade badge for Read Unit Economics
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-read-unit-economics/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-read-unit-economics)

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: read-unit-economics
description: "Compute cost per customer/transaction/feature and read the trend, not the gross bill. Reach for this on a scaling-health question."
---

# Skill: Read unit economics

A rising total bill can be healthy or decay — only the unit cost says which (§3 #2).

## Step 1 — Pick the unit
Customers, transactions, or features — the denominator that matters to the business.

## Step 2 — Compute cost-per-unit
Allocated cost ÷ units via `finops_cloud_cost_calc.py unit-cost` (§3 #2).

## Step 3 — Read the trend
Rising bill + falling unit cost = healthy; flat bill + rising unit cost = decay (§3 #2).

## Step 4 — Attribute the driver
Which service moves the unit cost, on allocated (not gross) spend (§3 #1).

## Output
A cost-per-unit read with the trend and the driving service named. Traverse Tree 2 in the decision-trees file.

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…