ai-roi-audit

Featured

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.

AI & Automation 1,228 stars 220 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 Method 1. **Reconstruct the promise.** Per tool: what outcome justified the purchase — time saved, quality improved, headcount avoided, revenue created? A tool without a stated outcome gets audited against the best-fit guess, *flagged as retrofitted*. 2. **Score with the strongest method the ev...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
5 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

ai-content-audit

Audit a content library, docs site, or blog for AI-generated filler that's eroding trust and search performance — and triage what to fix, rewrite, or delete. Use when asked to find slop in a content library, audit AI-written content quality, explain why content engagement or rankings dropped after scaling with AI, or set a quality bar for AI-assisted publishing. Produces an audited inventory with per-piece verdicts, the detection signals used, a triage plan, and a publishing quality gate that prevents recurrence. For a single article's AI-citability use aeo-optimizer; for the strategy itself use content-calendar or seo-content-brief.

1,228 Updated today
mohitagw15856
AI & Automation Listed

run-ai-audit

Audit how a business actually operates, build a digital twin of its workflows, classify every task as Agent, Copilot, or Human, and return a scored, phased AI implementation roadmap. Use when a founder, operator, or team asks "where should we use AI", "what should we automate", wants an AI audit, AI strategy, automation roadmap, or workflow mapping, says their team is drowning in manual work, or wants to know what should stay human. Not for building one specific automation — this maps the whole operation first.

0 Updated 1 weeks ago
navinramharak-rgb
AI & Automation Featured

ai-assisted-performance-review

Evaluate performance fairly when output is AI-assisted — what still measures the human, what now measures the tooling, and how to run the review conversation. Use when reviewing someone whose work is heavily AI-assisted, when output volume stopped meaning anything, when calibrating a team with uneven AI adoption, or when writing review criteria for the AI era. Produces review guidance: a what-measures-whom analysis, rewritten criteria, calibration rules for mixed-adoption teams, and conversation scripts. For the general review document use performance-review; for redesigning the role itself use role-redesign-for-ai.

1,228 Updated today
mohitagw15856