Skip to content
Skill

strategy-consulting-visualization

by kgraph57

AI Summary

Use this skill to turn any content into professional visualization specs with strategy-consulting clarity: insight-led headlines, disciplined layout, accurate data, restrained design, and explicit implications. It covers board slides first, and generalizes to reports, proposals, training materials,

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "strategy-consulting-visualization" skill in my project.

Please run this command in my terminal:
# Install skill into your project
mkdir -p .claude/skills/mckinsey-style-visualization-skill && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/mckinsey-style-visualization-skill/SKILL.md "https://raw.githubusercontent.com/kgraph57/mckinsey-style-visualization-skill/main/SKILL.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

Use when turning any content into clear, professional visualizations - board slides, reports, proposals, research summaries, training materials, technical diagrams, infographics, process flows, timelines, benchmarks, waterfall charts, or data-backed visual specs for any audience.

Purpose

Use this skill to turn any content into professional visualization specs with strategy-consulting clarity: insight-led headlines, disciplined layout, accurate data, restrained design, and explicit implications. It covers board slides first, and generalizes to reports, proposals, training materials, technical diagrams, infographics, and any input that benefits from visual structure.

Use When

• The user needs a board slide, executive memo visual, market map, competitor benchmark, investment view, performance bridge, or strategic timeline. • The user needs visuals for any other document: internal reports, research summaries, sales proposals, project status updates, training or education materials, technical documentation, one-pagers, infographics, or study notes. • The user has raw data, prose, notes, a process description, or a question and needs a visual direction — even if they only say "visualize this". • The user asks for McKinsey-style, BCG-style, Bain-style, consulting-style, boardroom-ready, executive-ready, or strategy-deck visuals. • The output should feel like a top-tier professional deliverable without implying affiliation with any consulting firm.

Do Not Use When

• The user wants decorative art with no informational content, brand campaigns, or low-density inspirational visuals. • The user needs regulated financial, medical, or legal conclusions without source verification. • The user asks for a final rendered chart but has not provided enough data to check labels, scales, and claims.

Workflow

• Identify the decision, question, or job the visual should support for its reader. • If the input is not an obvious chart request, triage it with references/input-triage.md to map any input type to a pattern family. • Pick the document profile from references/document-type-profiles.md to set canvas, density, and tone. • Convert the request into an insight-led headline that answers the reader's question. • Select the visualization pattern from references/visualization-patterns.md. • Apply the visual system in references/style-system.md, using the canvas from the document profile. • Produce a structured spec, diagram-as-code source, or image-generation prompt using references/prompt-templates.md. When the environment allows running scripts, optionally render supported patterns (waterfall, gap, before_after, time_series, benchmark_table, summary_strip, process_flow, funnel, heatmap, gantt, kpi_scorecard, two_by_two) to SVG with python3 scripts/render_slide_spec.py <spec.json>; spec examples are in examples/render-specs/. • Score the output against references/quality-rubric.md. • Flag missing data, unverifiable claims, source-sensitive assumptions, or trademark-sensitive wording. • For public, high-stakes, cross-functional, or broad-audience work, run references/expert-review-loop.md to remove blind spots, overclaims, jargon, accessibility issues, and cultural assumptions. • For polished executive work, run the draft through references/iterative-review-loop.md until the output reaches the stopping criteria.

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 3d ago
Active
AdoptionUnder 100 stars
36 ★ · Niche
DocsREADME + description
Well-documented

GitHub Signals

Stars36
Forks10
Issues5
Updated3d ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code