mckinsey-critic

mckinsey-critic is a skill for Claude Code, Codex from sruthir28/enterprise-ai-skills. It costs 60 tokens per session (915 once invoked), scanned A, original, MIT.

A review method for presentations, strategy documents, memos, and recommendations. It checks the structure, evidence, logic, and clarity, then gives an overall rating and three highest-priority fixes.

In plain words
What is it for?
Use it after writing a deck, document, strategy, or recommendation and before presenting or sending it to others.
Why use it?
It helps find weak arguments, unsupported claims, missing information, and confusing structure before work is shared with stakeholders.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after writing a deck, document, strategy, or recommendation and before presenting or sending it to others.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sruthir28/enterprise-ai-skills/mckinsey-critic
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add sruthir28/enterprise-ai-skills --skill mckinsey-critic
Clone the repo
git clone --depth 1 https://github.com/sruthir28/enterprise-ai-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mckinsey-critic

README.md
[![agentmods](https://agentmods.dev/badge/skills/sruthir28/enterprise-ai-skills/mckinsey-critic/github.svg)](https://agentmods.dev/skills/sruthir28/enterprise-ai-skills/mckinsey-critic)
Your own site
<a href="https://agentmods.dev/skills/sruthir28/enterprise-ai-skills/mckinsey-critic"><img src="https://agentmods.dev/badge/skills/sruthir28/enterprise-ai-skills/mckinsey-critic/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mckinsey-critic

Your own site · 80×15
<a href="https://agentmods.dev/skills/sruthir28/enterprise-ai-skills/mckinsey-critic"><img src="https://agentmods.dev/badge/skills/sruthir28/enterprise-ai-skills/mckinsey-critic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 915 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00060 $0.00915
Opus 5 $0.00030 $0.00458
Sonnet 5 $0.00012 $0.00183
Haiku 4.5 $0.00006 $0.00092

Measured 12d ago against content hash 0c58957ccf10, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

mckinsey-critic scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

mckinsey-critic/SKILL.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

McKinsey Critic

Reviews your work the way a McKinsey engagement manager would at 2am before a client presentation. Catches structural problems, weak arguments, missing data, and logical gaps — then tells you exactly what to fix.

How It Works

Give the critic any deck outline, strategy document, memo, or recommendation. It will:

  1. Grade the overall work (Green / Yellow / Red)
  2. Review each section or slide with a status and specific issue
  3. Identify the top 3 fixes — ranked by impact, with clear instructions
  4. Call out one thing that works — so you know what to protect

Grading Scale

Grade Meaning
Green Ready for stakeholders. Minor polish only.
Yellow Fixable overnight, but do not send as-is. Structural issues that undermine credibility.
Red Needs rework. Core argument or structure is broken.

What the Critic Checks

Structure

  • Does the narrative flow logically? (Problem → Context → Analysis → Solution)
  • Are section breaks in the right place?
  • Is there a clear beginning, middle, and end?

Rigor

  • Is every claim backed by data or a source?
  • Are numbers specific, not vague ("grew significantly" → "grew 25% YoY")?
  • Are comparisons fair and complete?
  • Is there a financial frame where one is needed?

So-What

  • Does each section have a clear takeaway?
  • Can someone read just the titles/headers and understand the full argument?
  • Is the recommendation actionable and time-bound?

Completeness

  • Are there comparison frameworks where options are presented? (not just a list)
  • Are competitors named, not described generically?
  • Are next steps specific with owners and timelines?

Output Format

# Critic Review: [Title]

**Grade: [GREEN/YELLOW/RED] — [one-line verdict]**

## Section-by-Section Review

| Section/Slide | Status | Issue |
|---|---|---|
| [Name] | Green/Yellow/Red | [Specific issue or "Strong"] |

## Top 3 Fixes

### Fix 1: [Title]
[What's wrong and exactly how to fix it]

### Fix 2: [Title]
[What's wrong and exactly how to fix it]

### Fix 3: [Title]
[What's wrong and exactly how to fix it]

## One Thing That Works
[Specific section/line that's strong and why — protect this]

Read the full file on GitHub · 102 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 102 lines · 60 tokens per session scan A 0c58957ccf10

Subscribe to this mod's changes

mckinsey-critic is a skill published in the GitHub repository sruthir28/enterprise-ai-skills (139 stars, last pushed 11d ago), licensed MIT. It adds 60 tokens to every session and 915 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.