Agent skill · Security

ai-roi-audit

Audit whether the organisation's AI spend actually paid — measured against baselines, not vendor math or vibes. Use when a CFO asks what the AI tools returned, when renewing AI contracts, when consolidating overlapping AI subscriptions, or to build the measurement plan before the next spend. Produces an ROI audit with per-tool verdicts (keep/consolidate/cut), the honest-measurement method behind each number, and a baseline plan for whatever can't be scored yet. To forecast ROI before an investment use roi-estimator; this skill measures what already happened.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill ai-roi-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/ai-roi-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# AI ROI Audit Skill Every org now spends real money on AI tools, and most justify it with adoption counts ("80% weekly active!") — which measure enthusiasm, not return. This skill audits what the spend *returned*, using methods that survive a sceptical CFO: baselines, counterfactuals, and quality deltas, with "we can't know yet" said out loud where it's true. ## What This Skill Produces - A **per-tool verdict table**: keep / consolidate / renegotiate / cut, each with its evidence - The **measurement behind each number** — method, baseline, confidence — so the audit is checkable - A **hidden-cost ledger** (the part vendor ROI decks omit) - A **baseline plan** for every "unknown", so next year's audit has data ## Required Inputs Ask for (if not already provided): - **The AI tool inventory with costs**: subscriptions, API spend, seats — and utilisation if known - **What each tool was bought to do** (the promised outcome, from the original business case if it exists) - **Available evidence**: usage data, before/after metrics, time studies, quality data, anecdotes (labelled as anecdotes) - **The decision at stake**: renewal? consolidation? budget defence? (calibrates depth) ## Audit Me

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Audit Method
  4. Output Format
  5. AI ROI Audit: [org/team] — [period]
  6. Quality Checks
  7. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the ai-roi-audit skill do?

Audit whether the organisation's AI spend actually paid — measured against baselines, not vendor math or vibes. Use when a CFO asks what the AI tools returned, when renewing AI contracts, when consolidating overlapping AI subscriptions, or to build the measurement plan before the next spend. Produces an ROI audit with per-tool verdicts (keep/consolidate/cut), the honest-measurement method behind each number, and a baseline plan for whatever can't be scored yet. To forecast ROI before an investment use roi-estimator; this skill measures what already happened.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill ai-roi-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going