Skip to content
Back to search

strategy-consulting-visualization

Use when turning content into clear strategy-consulting visualizations, including board slides, reports, diagrams, quiet animated decks, or explicit dynamic and interactive decks with clickable evidence, scenario controls, what-if sliders, and deterministic presenter demos.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/kgraph57/mckinsey-style-visualization-skill with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/kgraph57/mckinsey-style-visualization-skill'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/kgraph57--mckinsey-style-visualization-skill/badge.svg)](/listings/kgraph57--mckinsey-style-visualization-skill)

HTML

<a href="/listings/kgraph57--mckinsey-style-visualization-skill"><img src="/api/listings/kgraph57--mckinsey-style-visualization-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

# Skills CLI (skills.sh) — works with Claude Code, Cursor, Codex, and 70+ agents
npx skills add kgraph57/mckinsey-style-visualization-skill

Alternative — Claude Code clone install:

# Personal skill (Claude Code)
git clone https://github.com/kgraph57/mckinsey-style-visualization-skill.git ~/.claude/skills/strategy-consulting-visualization

# Project skill
git clone https://github.com/kgraph57/mckinsey-style-visualization-skill.git .claude/skills/strategy-consulting-visualization

Verify the package (same checks CI runs):

python3 -m unittest discover -s tests
python3 scripts/validate_skill.py   # → OK: skill package passed validation

The validator re-renders every committed SVG and the demo deck from source specs and fails on any drift — the gallery cannot silently rot.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 194 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: strategy-consulting-visualization
  3. description: Use when turning content into clear strategy-consulting visualizations, including board slides, reports, diagrams, quiet animated decks, or explicit dynamic and interactive decks with clickable evidence, scenario controls, what-if sliders, and deterministic presenter demos.
  4. ---
  5. # Strategy Consulting Visualization
  6. ## Purpose
  7. 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.
  8. ## Fast Path
  9. Skip the pattern-by-pattern build when the user just wants a complete, real deck or document immediately.
  10. **Full deck** — scaffold a ready-made archetype from `templates/decks/`, then fill in the illustrative placeholders with real data:
  11. ```bash
  12. python3 scripts/scaffold_deck.py --list # 6 archetypes with slide counts
  13. python3 scripts/scaffold_deck.py board-update -o my-deck # copies deck.json + specs/
  14. # edit my-deck/specs/*.json with real data, keeping the pattern shapes intact
  15. python3 scripts/build_html_deck.py --manifest my-deck/deck.json -o my-deck/deck.html
  16. ```
  17. **Click-through motion presentation** — when the reader should enter a page
  18. from an overview, press the exhibit or its main number for supporting detail,
  19. and verify the claim through an operation, use the story-led presentation
  20. route. This is the preferred route for a reference-led request for うちた-style
  21. 動く資料 or クリックで深掘り. Read `references/motion-story.md` and author a
  22. small `motion.json`; the six-page Japanese example demonstrates the components:
  23. ```bash
  24. python3 scripts/build_motion_deck.py --manifest examples/interactive-deck/motion.json -o deck.motion.html
  25. python3 scripts/build_motion_deck.py --manifest examples/interactive-deck/motion.json --static -o deck.motion.static.html
  26. ```
  27. The opening is a navigable argument, followed by evidence-led pages with one
  28. primary operation each. Exhibits and prominent numbers open a source-bearing
  29. drawer; classification sorts, comparison retains the prior shape, a slider
  30. recalculates the displayed formula, actions fill a gap, and a timeline advances
  31. through real decisions. Review the entire flow and run the visible cursor demo
  32. through its ending in the page overview. A single redesigned comparison page
  33. does not satisfy a request for this whole-deck experience.
  34. **Contract-backed interactive companion** — “animated” alone keeps the classic quiet-
  35. reveal path above. An explicit request for an interactive/dynamic deck, 動く・
  36. 動的スライド, clickable evidence, what-if recalculation, a slider, drill-down,
  37. or auto-demo builds the classic artifact first and then a companion from the
  38. same manifest:
  39. ```bash
  40. python3 scripts/build_html_deck.py --manifest my-deck/deck.json -o my-deck/deck.html
  41. python3 scripts/build_interactive_deck.py --manifest my-deck/deck.json -o my-deck/deck.interactive.html
  42. ```
  43. Before adding a scene, use `references/interaction-selection.md`. Author the
  44. closed scene contract with `references/interactive-scene-schema.md`, review
  45. `references/interactive-accessibility.md`, and hand off with
  46. `references/presenter-operation.md`. Always report both paths. The interactive
  47. artifact never replaces the static/print baseline.
  48. **Document** — write Markdown (with `spec:`/`svg:` exhibit references where a chart belongs) and build it straight to a browser-ready, print-to-A4 HTML report:
  49. ```bash
  50. python3 scripts/build_html_report.py my-report.md -o my-report.html --lang en
  51. ```
  52. `templates/reports/` has three starting points (board pre-read, one-pager, proposal memo).
  53. **Speaker script** — the podium version of any deck: add a top-level `"notes"` field (a string, or a list of paragraph strings) to the slides that need narration, then build a print-first, one-slide-per-page HTML script with the narration set below each slide. The renderer ignores `notes` entirely, so adding it never changes the rendered slide, and a slide with no notes still gets its own page with a muted "no script" marker.
  54. ```bash
  55. python3 scripts/build_speaker_script.py --manifest my-deck/deck.json -o my-deck/script.html --lang en
  56. ```
  57. **Deck as an article** — the same deck read top-to-bottom on a single 680px reading column instead of click-through slides or a side-nav document: a paper-first hero (kicker/lead from the manifest's optional `series`/`lead` keys), then each slide's SVG followed by its `notes` as reading prose, with optional per-slide `label`/`refs` fields adding a section tag and a "Links" aside that rolls up into an end-of-article links section.
  58. ```bash
  59. python3 scripts/build_html_article.py --manifest my-deck/deck.json -o my-deck/article.html --lang en
  60. ```
  61. All classic fast paths and the optional interactive companion still obey the style system and quality rubric below — they only skip writing specs from a blank page. Fall back to the full workflow for anything the templates don't already cover.
  62. ## Use When
  63. - The user needs a board slide, executive memo visual, market map, competitor benchmark, investment view, performance bridge, or strategic timeline.
  64. - 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.
  65. - 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".
  66. - The user asks for McKinsey-style, BCG-style, Bain-style, consulting-style, boardroom-ready, executive-ready, or strategy-deck visuals.
  67. - The output should feel like a top-tier professional deliverable without implying affiliation with any consulting firm.
  68. ## Do Not Use When
  69. - The user wants decorative art with no informational content, brand campaigns, or low-density inspirational visuals.
  70. - The user needs regulated financial, medical, or legal conclusions without source verification.
  71. - The user asks for a final rendered chart but has not provided enough data to check labels, scales, and claims.
  72. ## Workflow
  73. 1. Identify the decision, question, or job the visual should support for its reader.
  74. 2. 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.
  75. 3. Pick the document profile from `references/document-type-profiles.md` to set canvas, density, and tone.
  76. 4. Convert the request into an insight-led headline that answers the reader's question. The headline must be a single proposition — one answer or one tension, never several claims joined by "and".
  77. For an explicit interactive request, write the title-only storyboard first and add `Evidence`, `Main interaction`, `May change`, and `Must not change`. Reject any interaction that does not improve verification, insight, action, a decision, or evidence retrieval. See `references/interaction-selection.md`.
  78. 5. Select the visualization pattern from `references/visualization-patterns.md`, starting from the comparison-type gate at the top of that file. Structural patterns (`section_divider`, `agenda`, `bullet_list`, `closing`, `quote`, `end_cover`, `cover`) are deck furniture, not the argument — use them for connective tissue between slides (opening, orienting, transitioning, closing) and spend the insight-headline discipline on the content slides they connect.
  79. 6. Apply the visual system in `references/style-system.md`, using the canvas from the document profile. Write copy to its Word Budget: when text does not fit, cut words or split the slide — never shrink type.
  80. 7. Produce a structured spec, diagram-as-code source, or image-generation prompt using `references/prompt-templates.md`.
  81. When the environment allows running scripts, render supported patterns to SVG with `python3 scripts/render_slide_spec.py <spec.json>`. Twenty-two patterns render (cover, section_divider, end_cover, agenda, bullet_list, closing, quote, waterfall, gap, before_after, time_series, benchmark_table, summary_strip, process_flow, funnel, heatmap, gantt, kpi_scorecard, two_by_two, scatter, distribution, small_multiples), on a 16:9 canvas only; every other pattern and canvas is spec-only. `cover`, `section_divider`, and `end_cover` are full-bleed navy and skip the header/footer chrome; every other renderable pattern uses the standard white content chrome. Tell the user which they are getting — never imply a spec-only pattern will render. Spec examples are in `examples/render-specs/`.
  82. 8. Score the output against `references/quality-rubric.md`. For decks, also run its deck-level headline check.
  83. Inspect every rendered page at intended viewing size. A test pass or contact sheet alone is not completion. Numerical assertions need proportional visual evidence: bars for magnitude, a full model line and gate for a threshold, and contributions or a counterfactual for an additive score. Do not substitute a list of numbers, equal-width bands, or an isolated dot for that proof.
  84. For an interactive companion, validate the scene, inspect live and declared static states, run the author audit, and keep every unperformed manual/physical check explicit. See `references/interactive-accessibility.md` and `references/presenter-operation.md`.
  85. 9. Flag missing data, unverifiable claims, source-sensitive assumptions, or trademark-sensitive wording.
  86. 10. 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.
  87. 11. For polished executive work, run the draft through `references/iterative-review-loop.md` until the output reaches the stopping criteria.
  88. ## Output Contract
  89. Return a concise deliverable with:
  90. - `Strategic question` (or the reader's key question for non-strategy documents)
  91. - `Insight headline`
  92. - `Recommended visualization`
  93. - `Slide spec` (or figure, page, or diagram spec matching the document profile)
  94. - `Data and assumptions`
  95. - `Quality check`
  96. - `Expert review notes` when the output is public, high-stakes, cross-functional, or broad-audience
  97. When the user requests a batch, deck, or multi-figure document, repeat the contract per visual and add a brief flow summary explaining how the visuals build the argument.
  98. ## Reference-led reproduction
  99. When the user requests a particular firm's style or supplies a reference, read `references/reference-reproduction.md` before selecting a theme. Consult `references/consulting-reference-evidence.json` and inspect the specific source page. Record geometry, hierarchy, chart encoding, notes and deviations. Choose presentation, analytical pre-read, or reading document explicitly. Do not claim exact fidelity from a colour preset alone. The worked examples are in `templates/reference-layouts/`.
  100. ## Default Visual Standards
  101. - For business presentation requests, prefer `"theme": "executive"` consistently across the deck: sans-serif headlines, neutral comparison marks, and navy for the main outcome. In a metric-led summary, use `focus_block` only for the single decision-critical column. For diagrams, keep executive process flows to five steps with optional owner/duration fields and priority matrices to six numbered options; split denser content across slides. See `references/style-system.md` for the supported options; retain `classic` when the user requests serif styling.
  102. - Slides render to 16:9. Supported chart/diagram patterns also render compact document exhibits with `--exhibit`; arbitrary canvases remain spec-only. HTML reports support A4 briefing/editorial layouts with editable captions and sources. Optional `scripts/build_briefing_docx.cjs` creates editable A4 Word briefs and requires Node packages `docx` and `sharp`.
  103. - White content slides with black text, a single navy accent (`#15296B`), and grey hierarchy.
  104. - Navy full-bleed slides only when opening a deck (`cover`), opening a section (`section_divider`), or closing a deck (`end_cover`) — never for a content slide.
  105. - Classic uses serif headlines; executive and analytical content use sans-serif headlines. A reference-led request takes precedence over these defaults.
  106. - High information density with clear hierarchy; no decorative clutter.
  107. - All numbers must be visible, consistently formatted, and tied to the user's data or cited assumptions.
  108. - Keep action titles self-contained; omit subtitles that merely restate the title. Preserve the fixed title baseline and a clear gap before the exhibit.
  109. - Presentation body copy uses 26px and primary exhibit labels 22px on the 1280 × 720 canvas. Reduce content or split the page before reducing these sizes.
  110. - Interactive desktop slides are one composition: exhibit, inputs and decision visible together at 1280 × 720 and 1440 × 900. Hide redundant semantic copies visually while retaining accessible equivalents. Narrow screens reflow; never shrink the entire interface into unreadable text.
  111. - Choose control placement for the argument, not a fixed dashboard template. For a small scenario comparison, retain the reference state beside the changing state and place the selector near the comparison. A rank bridge encodes ordinal position; label the scores directly rather than implying its slope measures score change. Emphasize the decision-changing item and keep supporting actions visually secondary.
  112. - Check the decision sequence across the deck. A gated action cannot precede its review, and “approve today” must not conflict with a later conditional decision.
  113. ## Marketplace Safety
  114. This skill is not affiliated with, endorsed by, or sponsored by McKinsey & Company, Boston Consulting Group, Bain & Company, or any other consulting firm. Use category language such as "strategy consulting visualization" in user-facing outputs unless the user specifically asks for comparative style references.
  115. Do not invent client names, confidential labels, benchmark data, or source citations. If a visual depends on uncertain or missing data, mark the assumption explicitly in `Data and assumptions`.
  116. ## Reference Files
  117. - `references/motion-story.md` for the story-led motion presentation builder,
  118. six component contracts, whole-deck navigation and direct evidence access.
  119. - `references/consulting-design-study.md` for the six-firm page-level design study.
  120. - `references/reference-reproduction.md` for measured reproduction, supported routes and fidelity review.
  121. - `references/persona-playbook.md` for role-based entry points (sales, marketing, product, PMO, HR, engineering, research, finance, executive) with prompts and example specs.
  122. - `references/input-triage.md` for mapping any input — numbers, prose, processes, ideas — to a pattern family.
  123. - `references/document-type-profiles.md` for adapting format, density, and tone to slides, reports, proposals, training materials, technical docs, and infographics.
  124. - `references/visualization-patterns.md` for pattern selection and use cases.
  125. - `references/style-system.md` for palette, typography, spacing, and layout rules.
  126. - `references/prompt-templates.md` for slide specs and image-generation prompts.
  127. - `references/quality-rubric.md` for final scoring and marketplace-quality checks.
  128. - `references/expert-review-loop.md` for challenging assumptions, overclaims, accessibility, localization, and audience-fit risks.
  129. - `references/public-reference-corpus.md` for public executive-report sources to study without copying.
  130. - `references/iterative-review-loop.md` for draft, review, revise, and score cycles.
  131. - `references/interaction-selection.md` for the classic/animated/interactive routing boundary and the static-first deletion gate.
  132. - `references/interactive-scene-schema.md` for the six scenes, model/control/view matrix, exact values, lineage, and build commands.
  133. - `references/interactive-accessibility.md` for semantic, focus, compact, print, automated, and manual review obligations.
  134. - `references/presenter-operation.md` for live controls, demo, safe links, offline use, printing, and the physical-device checklist.
  135. - `templates/decks/` and `scripts/scaffold_deck.py` for ready-made deck archetypes (`--list` to see all six).
  136. - `templates/reports/` and `scripts/build_html_report.py` for Markdown-to-report documents with numbered exhibits.
  137. - `scripts/build_speaker_script.py` for a print-first, one-slide-per-page podium script built from a deck's `notes` field.
  138. - `scripts/build_html_article.py` for reading the same deck top-to-bottom as a single web-page article, slide by slide with its `notes` as prose.
  139. ## HTML to PDF
  140. Use JSON for charts and Markdown for the narrative. Generate HTML, review it in the browser, and export that same HTML to PDF. HTML is the primary layout artifact; Word is an optional separate export. Reports use A4 print styles; decks use one 16:9 slide per page.
  141. ```bash
  142. python3 -m pip install playwright
  143. python3 scripts/build_html_report.py templates/reference-layouts/decision-brief.md -o brief.html
  144. python3 scripts/export_pdf.py brief.html -o brief.pdf
  145. python3 scripts/export_pdf.py examples/demo-deck.html -o deck.pdf
  146. ```
  147. PDF export requires installed Google Chrome or Chromium (`--browser /path/to/browser` for a custom executable). SVG and HTML generation remain Python-standard-library only. Alternatively, open the generated HTML, choose **Save as PDF**, and select the browser’s PDF destination. Inspect every page after changing content; longer reports may need deliberate page breaks.
README.md · README · 454 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <div align="center">
  2. # Strategy Consulting Visualization Skill
  3. **Messy notes in. Board-ready slides out.**
  4. One skill for your AI agent: turn notes, metrics, and prose into consulting-grade visuals — as real SVG slides, as an **animated HTML deck**, or as a spec any designer or tool can execute.
  5. Rendering existing JSON specs into SVG/HTML uses the Python 3 standard library only, with no API key or network access required. **Generating slides from notes in the browser requires your own Anthropic API key.** The sample trial needs no key. Automated PDF export has optional browser dependencies.
  6. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
  7. [![CI](https://github.com/kgraph57/mckinsey-style-visualization-skill/actions/workflows/ci.yml/badge.svg)](https://github.com/kgraph57/mckinsey-style-visualization-skill/actions/workflows/ci.yml)
  8. [![Skill Format](https://img.shields.io/badge/SKILL.md-ready-blue.svg)](SKILL.md)
  9. [![Preview Release](https://img.shields.io/badge/Preview-v3.0.0--rc.1-005eb8.svg)](https://github.com/kgraph57/mckinsey-style-visualization-skill/releases/tag/v3.0.0-rc.1)
  10. English | [日本語](README.ja.md)
  11. [![Watch the English interactive decision story demo](assets/readme/decision-story-demo-frameless.gif)](https://kgraph57.github.io/mckinsey-style-visualization-skill/demo/)
  12. **[Watch the full demo with playback controls →](https://kgraph57.github.io/mckinsey-style-visualization-skill/demo/)**
  13. _Actual browser recording. Preview at 2.5× speed; full video at normal speed, without audio._
  14. _Actual v3 output: `motion manifest (JSON) → interactive story + static reading edition`._
  15. </div>
  16. ## v3.0.0-rc.1 — Interactive decision stories
  17. [**Open the English live demo →**](https://kgraph57.github.io/mckinsey-style-visualization-skill/site/artifacts/project-relay.motion.en.html) · [Static reading version](https://kgraph57.github.io/mckinsey-style-visualization-skill/site/artifacts/project-relay.motion.en.static.html) · [Japanese demo](https://kgraph57.github.io/mckinsey-style-visualization-skill/site/artifacts/project-relay.motion.html)
  18. **Change an assumption. See the decision change.** Six connected pages take readers
  19. from the priority to investigate, through route comparisons and a live value model,
  20. to readiness and a conditional rollout. The English decision design uses large
  21. body text, assertion-led headlines and whitespace instead of decorative dividers.
  22. Press **D** for the guided demo, or explore the charts and controls yourself.
  23. All example data is illustrative, not a client result.
  24. This is a **prerelease**, not a fully device-certified stable release.
  25. [v2.4.0](https://github.com/kgraph57/mckinsey-style-visualization-skill/releases/tag/v2.4.0)
  26. remains the latest stable release. Download the self-contained HTML files from
  27. the [release assets](https://github.com/kgraph57/mckinsey-style-visualization-skill/releases/tag/v3.0.0-rc.1).
  28. **A click-through motion presentation is now available.** The
  29. [six-page English story](examples/interactive-deck/deck.motion.en.html) starts with
  30. an overview you can enter, lets readers press exhibits and prominent numbers
  31. for evidence, and connects changed assumptions to the conditional rollout.
  32. Sorting, retained differences, live equations, gap-filling actions and timeline
  33. steps are included in a cursor-led demo. A
  34. [static reading version](examples/interactive-deck/deck.motion.en.static.html)
  35. comes from the same source. See the [motion story guide](references/motion-story.md).
  36. The [Japanese version](examples/interactive-deck/deck.motion.html) is also retained.
  37. ```bash
  38. python3 scripts/build_motion_deck.py --manifest examples/interactive-deck/motion.en.json -o deck.motion.en.html
  39. python3 scripts/build_motion_deck.py --manifest examples/interactive-deck/motion.en.json --static -o deck.motion.en.static.html
  40. ```
  41. The separately supported contract-backed runtime is described below.
  42. The skill now has an optional **stateful interactive companion** for decision
  43. work: clickable evidence, bounded scenario switches, exact what-if sliders,
  44. readiness scoring, drill-downs, accordions, and a deterministic presenter demo.
  45. It keeps the restrained, assertion-led slide system and always preserves a
  46. static/print conclusion.
  47. “Animated deck” still means the existing quiet reveal. Ask explicitly for an
  48. `interactive deck`, `dynamic deck`, `what-if`, `clickable evidence`, `scenario
  49. slider`, `drill-down`, or `auto-demo` to build both audience artifacts:
  50. ```bash
  51. python3 scripts/build_html_deck.py --manifest examples/interactive-deck/deck.json -o deck.html
  52. python3 scripts/build_interactive_deck.py --manifest examples/interactive-deck/deck.json -o deck.interactive.html
  53. ```
  54. Try the original, entirely illustrative eight-page example: [Project Relay —
  55. classic HTML](examples/interactive-deck/deck.html), [interactive
  56. HTML](examples/interactive-deck/deck.interactive.html), and [static
  57. PDF](examples/interactive-deck/deck.pdf). The public `/try/` route remains the
  58. classic builder. Core HTML generation uses the Python standard library and
  59. writes only the explicit output path; browser/PDF/audit checks use the pinned
  60. optional test tools. See [interaction selection](references/interaction-selection.md),
  61. [scene authoring](references/interactive-scene-schema.md), [accessibility](references/interactive-accessibility.md),
  62. and [presenter operation](references/presenter-operation.md).
  63. Known verification limits: Safari, physical iPhone/touch,
  64. real browser-toolbar 200% zoom, AirPlay/HDMI/projector, VoiceOver/NVDA, real
  65. high contrast, and hosted response headers remain manual gates. See the
  66. [verification record](tests/manual/interactive-release.md). The English decision
  67. layer is tailored to Project Relay, not a universal business-model generator.
  68. Public inspiration and independent design choices are recorded in
  69. [design provenance](references/decision-design.md); this package is not affiliated
  70. with or endorsed by McKinsey or any other consulting firm.
  71. ## What’s new — September 9, 2026
  72. **Try a presentation on your phone before setting up an API key.** Open the [browser trial](https://kgraph57.github.io/mckinsey-style-visualization-skill/try/), choose **Explore a sample deck**, then **Start presentation**.
  73. - **Present directly in the browser.** Swipe or use Previous / Next to move through slides; rotate your phone for a larger landscape view. Desktop keyboard navigation is also supported.
  74. - **Share or save HTML.** Use the device share sheet where supported, with a download fallback. Present from the browser; reopening interactive HTML from iOS Files is not yet verified.
  75. - **Save a PDF.** Choose **PDF / Print**, select landscape in the native print dialog, then use its share/save options. iOS may initially select A4 portrait.
  76. - **See the outcome before trying it.** The homepage pairs a clearly labeled AI-generated hero concept with actual renderer output and a path from examples to the trial or installation.
  77. - **iOS fixes verified in Simulator.** Japanese text and controls use an explicit Hiragino fallback; HTML sharing no longer creates an extra text file.
  78. Tested with **iPhone 17 / iOS 26.3 Simulator Safari**: sample loading, presentation, swipe navigation, rotation, nine-page print preview, and PDF/HTML saving to Files. Existing 335 tests pass. Physical iPhone hardware, live API generation and AirPlay/projector output remain unverified. See the [test record](tests/manual/ios-safari.md).
  79. ## What’s new — September 8, 2026
  80. - **Refined business slides and diagrams.** Updated the executive summary, growth waterfall, priority matrix, process flow and roadmap layouts, with clearer hierarchy, labels and decision cues. Regenerated the English and Japanese landing decks and site previews from the current renderer.
  81. - **Real deliverables on the site.** The homepage now shows actual slide previews alongside a complete A4 brief, with links to the finished PDFs. Examples use illustrative business data.
  82. - **HTML first, PDF for sharing.** Keep chart data in JSON and report prose in Markdown, refine the generated HTML, then export it directly to PDF. Decks and reports include a **Save as PDF** button; `scripts/export_pdf.py` also supports command-line export.
  83. - **Reference-based layouts.** A [design study of nine public documents from six consulting firms](references/consulting-design-study.md) informs the analytical slide and compact report templates.
  84. Explore the updated [nine-slide board deck (PDF)](examples/demo-deck.pdf), [one-page decision brief (PDF)](templates/reference-layouts/decision-brief.pdf), and [source HTML](templates/reference-layouts/decision-brief.html). See [HTML to PDF](#html-to-pdf) for export commands. Automated PDF export requires Python Playwright and installed Chrome or Chromium; core SVG/HTML generation has no third-party Python dependencies.
  85. ## Why This Gets Starred
  86. - **Install it and get a complete deck immediately.** `scripts/scaffold_deck.py <archetype>` copies a full, coherent 9-12 slide deck — cover through closing — into a working directory. Swap the illustrative data for yours and build. Six archetypes ship, one in Japanese.
  87. - **It actually renders.** 22 patterns produce real SVG slides — waterfall, executive summary, 2×2, scatter, heatmap, Gantt, small multiples, cover, section dividers, agendas, closings, and more. Every gallery image below is committed renderer output, verified fresh by CI on every push.
  88. - **Animated HTML decks from one command.** Combine slides into a single self-contained HTML file: quiet staggered reveals, keyboard navigation, progress bar, zero external requests. Press `p` → your browser prints it → **you have a PDF**.
  89. - **A browser-native report mode.** `scripts/build_html_report.py` turns Markdown into a self-contained, print-to-A4 HTML document with numbered exhibits — the same visual system, for documents instead of decks.
  90. - **Works with your slide tools.** The SVGs drop straight into **PowerPoint, Keynote, and Word** (Insert → Picture). For Google Slides, export PNG from any browser first.
  91. - **Japanese business documents are first-class.** CJK text wraps correctly (measured per fullwidth character, not by spaces), fonts fall back to Noto Sans JP / Hiragino, and there are dedicated profiles for 稟議書, 役員会資料, 週報, 学会抄録.
  92. - **Charts that survive an audit.** Bar proportions match the data (Lie Factor ≈ 1.0), zero baselines are marked, cell text passes WCAG AA contrast across the whole color ramp, and the accent navy stays readable in greyscale print — all of it **asserted in the test suite**, not promised in prose.
  93. - **Roasted by five design legends, then fixed.** We ran the whole system through a five-perspective design panel — Tufte's data-ink discipline, an ex-McKinsey chart master, Swiss grid typography, FT-style data journalism, and modern design engineering. They scored it 5.8/10 and listed every flaw. A previous release shipped every fix. [Read the receipts.](#roasted-by-five-design-legends)
  94. ## 60-Second Start
  95. ```bash
  96. # 1. Install it as an agent skill (Claude Code, Cursor, Codex, and 70+ agents)
  97. npx skills add kgraph57/mckinsey-style-visualization-skill
  98. ```
  99. Or clone it directly (also gets you the runnable scripts below):
  100. ```bash
  101. # 1. Get it (Claude Code clone install)
  102. git clone https://github.com/kgraph57/mckinsey-style-visualization-skill.git ~/.claude/skills/strategy-consulting-visualization
  103. cd ~/.claude/skills/strategy-consulting-visualization
  104. # 2. Render one slide → SVG
  105. python3 scripts/render_slide_spec.py examples/render-specs/arr-waterfall.json -o slide.svg
  106. # 3. Build the full animated deck → one HTML file
  107. python3 scripts/build_html_deck.py --manifest examples/demo-deck.json -o deck.html
  108. open deck.html # ← arrows to navigate, "p" to print → PDF
  109. ```
  110. Or skip the terminal and just ask your agent:
  111. ```text
  112. Use the strategy consulting visualization skill to turn these notes into a board slide:
  113. ARR grew from $10M to $15M. Enterprise added $3M, expansion $2.5M, churn -$0.5M.
  114. The board must decide on implementation capacity investment.
  115. ```
  116. ## The Pipeline
  117. ```mermaid
  118. flowchart LR
  119. A["Messy notes,<br/>metrics, prose"] --> B["Slide spec<br/>(JSON)"]
  120. B --> C["SVG slides"]
  121. C --> D["Animated HTML deck"]
  122. C --> E["PowerPoint / Keynote / Word<br/>(insert SVG)"]
  123. D --> F["PDF<br/>(browser print)"]
  124. ```
  125. Specs are plain JSON, so they diff, review, and version like code. The renderer and deck builder are single-file Python scripts with no installs.
  126. ## Gallery
  127. Every image is committed output of `scripts/render_slide_spec.py` — CI fails if any of them drifts from what the renderer actually produces. Specs live in [examples/render-specs/](examples/render-specs).
  128. | ARR Waterfall | Executive Summary Strip |
  129. | ------------------------------------------------------------ | -------------------------------------------------------------------- |
  130. | ![Rendered ARR waterfall](assets/rendered/arr-waterfall.svg) | ![Rendered executive summary](assets/rendered/executive-summary.svg) |
  131. | Small Multiples | Scatter / Correlation |
  132. | --------------------------------------------------------------------------- | ------------------------------------------------------------------ |
  133. | ![Rendered small multiples](assets/rendered/segment-adoption-multiples.svg) | ![Rendered scatter](assets/rendered/pricing-retention-scatter.svg) |
  134. | Japanese Board Summary(役員会サマリー) | Cover Slide |
  135. | ------------------------------------------------------------------------ | ------------------------------------------------------------- |
  136. | ![Rendered Japanese board summary](assets/rendered/jp-board-summary.svg) | ![Rendered cover slide](assets/rendered/board-deck-cover.svg) |
  137. | Benchmark Table | Distribution |
  138. | ----------------------------------------------------------------- | -------------------------------------------------------------------- |
  139. | ![Rendered benchmark table](assets/rendered/vendor-benchmark.svg) | ![Rendered distribution](assets/rendered/deal-size-distribution.svg) |
  140. | Capacity Gap | Process Flow |
  141. | ---------------------------------------------------------- | ------------------------------------------------------------- |
  142. | ![Rendered capacity gap](assets/rendered/capacity-gap.svg) | ![Rendered process flow](assets/rendered/onboarding-flow.svg) |
  143. **22 patterns render to SVG**: `cover`, `section_divider`, `end_cover`, `agenda`, `bullet_list`, `closing`, `quote`, `waterfall`, `gap`, `before_after`, `time_series`, `benchmark_table`, `summary_strip`, `process_flow`, `funnel`, `heatmap`, `gantt`, `kpi_scorecard`, `two_by_two`, `scatter`, `distribution`, `small_multiples`. Thirteen more patterns (Sankey, pyramid, maps, decision trees, …) ship as structured specs and image-generation prompts — [the catalog says exactly which is which](references/visualization-patterns.md). We don't pretend.
  144. ## Animated HTML Decks
  145. ```bash
  146. python3 scripts/build_html_deck.py cover.json bridge.json summary.json -o deck.html --title "Q4 Review"
  147. ```
  148. One command, one file, and you get:
  149. - **Quiet, staggered element reveals** on every slide — the restrained kind, not slide-carnival transitions (`prefers-reduced-motion` respected)
  150. - **Keyboard + click navigation**, progress bar, slide counter, deep links (`deck.html#3`)
  151. - **Print stylesheet**: `p` or Cmd+P gives you one slide per page → save as **PDF**
  152. - **Zero external requests** — fonts, styles, scripts, and SVGs are all inline. Email it, host it, present offline.
  153. Try the committed demo: [examples/demo-deck.html](examples/demo-deck.html) (open locally after cloning).
  154. ## Instant Deck: Scaffold → Build
  155. Skip writing specs from a blank page. Pick an archetype, copy it, swap in real data:
  156. ```bash
  157. python3 scripts/scaffold_deck.py --list # see all 6 archetypes + slide counts
  158. python3 scripts/scaffold_deck.py board-update -o my-deck --title "FY27 Board Update"
  159. # edit my-deck/specs/*.json with real numbers — the pattern shapes are already right
  160. python3 scripts/build_html_deck.py --manifest my-deck/deck.json -o my-deck/deck.html
  161. ```
  162. `scaffold_deck.py` refuses to overwrite a non-empty directory unless you pass `--force`, and prints the next two commands when it's done.
  163. ## Template Gallery
  164. Six deck archetypes ship pre-filled with a coherent illustrative storyline — every slide renders, nothing is a stub.
  165. | Archetype | Use For | Storyline |
  166. | ------------------------- | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
  167. | `board-update` | Recurring board / steering updates | Cover → agenda → executive summary → KPI scorecard → ARR waterfall → trend → risk view → closing → end cover |
  168. | `strategy-recommendation` | "Where to play, how to win" strategy decks | Cover → agenda → context → two section dividers (Where to play / How to win) → 2×2 → benchmark table → gap or bridge → roadmap → closing → end cover |
  169. | `project-status` | PMO / steering-committee status reviews | Cover → summary → roadmap → KPI scorecard → blockers → path-to-green flow → closing → end cover |
  170. | `market-entry` | Entry or expansion investment cases | Cover → agenda → market trend → competitor benchmark → segment 2×2 → entry-path flow → distribution or scatter → closing → end cover |
  171. | `sales-proposal` | Customer-facing proposals | Cover → client situation → before/after → approach flow → plan → why-us benchmark → customer quote → closing → end cover |
  172. | `board-update-ja` | 役員会向け月次アップデート(日本語) | `board-update` と同じ構成を、翻訳調ではなく自然な日本語の見出しで |
  173. ## Report Mode: Markdown → Browser Document
  174. For a document instead of a deck, write Markdown and build it straight to a single self-contained, print-to-A4 HTML report:
  175. ```bash
  176. python3 scripts/build_html_report.py my-report.md -o my-report.html --lang en
  177. ```
  178. - Front matter (`title`, `subtitle`, `author`, `date`, `classification`, `lang`) drives a navy title band — the only navy surface in the document.
  179. - `##`/`###` headings auto-number and build a "Contents" TOC with anchor links; standard Markdown (bullets, ordered lists, tables, bold/italic, code, blockquotes, links) renders as clean editorial typography — everything HTML-escaped first, so nothing in the source can inject markup.
  180. - Drop in a rendered chart with `![Caption](spec:path/to/spec.json)` — it becomes an auto-numbered `Exhibit N — Caption` with the full slide SVG embedded inline, no header/footer chrome needed. `![Caption](svg:path.svg)` embeds an existing SVG file the same way.
  181. - `p` / Cmd+P exports an A4-portrait PDF with the title band as the first page.
  182. - Zero external requests — same self-contained guarantee as the HTML deck.
  183. Three starting points ship in `templates/reports/`: `board-pre-read.md`, `one-pager.md`, `proposal-memo.md`. See the committed demo: [examples/demo-report.html](examples/demo-report.html) (built from [examples/demo-report.md](examples/demo-report.md)).
  184. ## Speaker Script: What You Read at the Podium
  185. Any slide spec can carry a top-level `"notes"` field — a string, or a list of paragraph strings — holding the spoken narration for that slide. The SVG renderer ignores it completely, so adding notes never changes a rendered slide. Build the same deck manifest into a print-first, one-slide-per-page script:
  186. ```bash
  187. python3 scripts/build_speaker_script.py --manifest my-deck/deck.json -o my-deck/script.html --lang en
  188. ```
  189. - One printed A4 page per slide: the slide rendered inline above, the narration in podium-readable type below (screen 20px, print ~13.5pt; `--lang ja` loosens line-height to 1.9 with `palt` for CJK).
  190. - A slide with no notes still gets its own page, with a muted "(no script)" / "(原稿なし)" marker — never silently skipped.
  191. - A cover page carries the deck title and the date from the deck's own cover slide, if present.
  192. - Zero external requests, no required JavaScript.
  193. See the committed demo: [examples/demo-script.html](examples/demo-script.html) (built with `--lang ja` from [templates/decks/board-update-ja/deck.json](templates/decks/board-update-ja/deck.json)).
  194. ## Deck as an Article: Read It Top to Bottom Like a Web Page
  195. The same `notes` field also drives a reading-mode build: the whole deck laid out vertically on a single 680px column, each slide's SVG followed by its narration as prose — a paper-first article, like a published M3-series piece, not a side-nav document.
  196. ```bash
  197. python3 scripts/build_html_article.py --manifest my-deck/deck.json -o my-deck/article.html --lang en
  198. ```
  199. - A hero opens the page: an optional uppercase kicker from the manifest's `series` key, the title, an optional lead paragraph from `lead` (falling back to `description` for older manifests), and meta chips for slide count, presenter, and date (from the deck's cover slide).
  200. - Every slide appears, in manifest order, as its own `<article>` on the full 680px column — meta line (number + optional per-spec `label`), heading, SVG, then its notes as prose. There is no "Contents" jump list in this mode; it is a single linear scroll.
  201. - A slide with no notes renders frame-only — the article still shows every slide, like flipping through the deck.
  202. - Optional per-slide `refs` (`[{"label": ..., "url": ...}]`) render as a "Links" aside below the notes and roll up, deduped by URL, into an "All links" section after the last slide; only http(s)/mailto URLs render as links.
  203. - `--title` overrides the manifest title; zero external requests except the `href` of a ref link itself.
  204. See the committed demo: [examples/demo-article.html](examples/demo-article.html) (built from [templates/decks/board-update/deck.json](templates/decks/board-update/deck.json)).
  205. ## Export Anywhere
  206. | Target | How | Fidelity |
  207. | --------------------------------- | -------------------------------------------- | --------------------------- |
  208. | PDF | Open the HTML deck → print → save as PDF | Vector, one slide per page |
  209. | PowerPoint / Keynote / Word | Insert the SVG files as pictures | Vector, scales losslessly |
  210. | Google Slides / Docs | Render SVG → PNG in any browser, then insert | Raster at any resolution |
  211. | Design tools (Figma, Illustrator) | Open the SVG directly | Fully editable vectors |
  212. | Docs / wikis / GitHub | Embed the SVG — GitHub renders it inline | What you see in this README |
  213. ## Roasted by Five Design Legends
  214. Most chart generators say "beautiful". We wanted **defensible**, so we convened a five-perspective design review panel (as rigorous AI personas) and told them to be merciless:
  215. | Reviewer lens | Verdict | Sharpest cut |
  216. | ------------------------------------------------ | ------- | ------------------------------------------------------------------- |
  217. | Edward Tufte — data-ink, honest scales | 5.5/10 | "Meaningless decorated rectangles baked into the renderer" |
  218. | Gene Zelazny — ex-McKinsey, _Say It With Charts_ | 6.5/10 | "The flagship example violates its own headline rule" |
  219. | Vignelli × Müller-Brockmann — Swiss grid | 6/10 | "A corporate template, not a design system" |
  220. | Alan Smith — FT data journalism | 5.5/10 | "The waterfall draws off-canvas on negative bridges" (he proved it) |
  221. | Modern design engineering | 5.5/10 | "2016 visuals wearing a 2020s spec sheet" |
  222. Then we shipped **every fix** in [a prior release](CHANGELOG.md): zero-floor waterfalls, CJK-correct wrapping, no silent truncation, a single re-derived navy that survives greyscale printing, diverging heatmaps for signed data, WCAG-AA cell text asserted across the entire ramp, decoration stripped, a comparison-type gate before every chart choice, and a rubric that now measures data-ink integrity and deck-level storyline logic.
  223. The result is a visual system you can defend in front of a board, an auditor, or a design critic — because it already survived one.
  224. ## The Discipline Under the Hood
  225. The renderer is the visible part. The skill underneath is a full operating system for executive visualization:
  226. - **Message first**: every visual starts from the reader's decision, gets a single-proposition insight headline, and only then picks a chart — gated by the five comparison types (component / item / time series / distribution / correlation).
  227. - **A real style system**: [design tokens on an 8px grid, a fixed type scale, one navy, an emphasis ladder (fill > line > text) with hard caps](references/style-system.md) — the same constants the renderer executes.
  228. - **A quality rubric with teeth**: [24-point scoring](references/quality-rubric.md) across strategy, data integrity, data-ink honesty, hierarchy, portability, and safety, plus blocking gates (no color-only meaning, no invented data, no implied rendering that doesn't exist).
  229. - **An adversarial review loop**: [expert lenses](references/expert-review-loop.md) that hunt overclaims, insider jargon, accessibility failures, and cultural assumptions before anything is called publishable.
  230. ## By Role
  231. The [persona playbook](references/persona-playbook.md) gives every role a copy-paste prompt and a rendered example:
  232. | Role | Ask For | Rendered Example |
  233. | ---------------------- | -------------------------------- | ---------------------------------------------------------------------------- |
  234. | Sales | Pipeline QBR, proposal visuals | ![Sales funnel](assets/rendered/sales-pipeline-funnel.svg) |
  235. | Project manager / PMO | Roadmap with critical path | ![PMO gantt](assets/rendered/pmo-rollout-gantt.svg) |
  236. | Marketing | Channel × segment performance | ![Marketing heatmap](assets/rendered/marketing-channel-heatmap.svg) |
  237. | HR / People ops | Talent scorecard | ![HR scorecard](assets/rendered/hr-talent-scorecard.svg) |
  238. | Product manager | Effort vs. impact prioritization | ![Product 2x2](assets/rendered/product-priority-two-by-two.svg) |
  239. | Engineer / Tech lead | Incident postmortem flow | ![Incident flow](assets/rendered/eng-incident-flow.svg) |
  240. | Researcher / Clinician | Study outcome summary | ![Research before-after](assets/rendered/research-outcomes-before-after.svg) |
  241. Japanese business formats (稟議書, 週報・月報, 役員会資料, 学会抄録, 提案書) have dedicated profiles in [document-type-profiles.md](references/document-type-profiles.md).
  242. ## One-Minute Example
  243. Give the skill this:
  244. ```text
  245. ARR grew from $10M to $15M.
  246. Enterprise expansion contributed $3M. Existing customers added $2.5M. Churn cost $0.5M.
  247. AI workflow adoption grew from 18% to 64%.
  248. The board needs to decide whether to invest in implementation capacity.
  249. ```
  250. It returns a decision-framed spec — strategic question, single-proposition headline, pattern choice with reasoning, exact values and labels, assumptions, and a rubric score — that renders to the waterfall you saw in the gallery. See the full worked proof: [input](examples/board-update-input.md) → [slide specs](examples/board-update-slide-spec.md) → [evaluation](examples/evaluation-report.md).
  251. ### Case Study: the full loop in two minutes
  252. **[SaaS Board Update — Raw Notes to a Board-Ready Slide](examples/case-studies/saas-board-update.md)** walks one real pass end to end: anonymized founder notes → weak first draft → the packaged reviewer rejects it (14/20) → decision-first revision passes (20/20) → the committed rendered slides. Every artifact is in this repo and reproducible with two commands.
  253. ## What You Can Point It At
  254. | Starting Point | You Get |
  255. | ---------------------------- | ----------------------------------------------------------- |
  256. | Board update metrics | 5-slide story: cover, waterfall, trend, gap, recommendation |
  257. | Revenue bridge data | Waterfall with drivers, honest baselines, assumptions |
  258. | Competitor / vendor data | Benchmark table + 2×2 positioning with leader highlights |
  259. | KPI before/after data | Impact slide with deltas and an implication headline |
  260. | Process description / SOP | Process flow with owners and the bottleneck highlighted |
  261. | Segment metrics over time | Small-multiples grid on one honest shared scale |
  262. | Research notes / whitepaper | Numbered report figures with sources and distributions |
  263. | Any prose — "visualize this" | Input triage → right pattern → document profile → spec |
  264. ## Install
  265. ```bash
  266. # Skills CLI (skills.sh) — works with Claude Code, Cursor, Codex, and 70+ agents
  267. npx skills add kgraph57/mckinsey-style-visualization-skill
  268. ```
  269. Alternative — Claude Code clone install:
  270. ```bash
  271. # Personal skill (Claude Code)
  272. git clone https://github.com/kgraph57/mckinsey-style-visualization-skill.git ~/.claude/skills/strategy-consulting-visualization
  273. # Project skill
  274. git clone https://github.com/kgraph57/mckinsey-style-visualization-skill.git .claude/skills/strategy-consulting-visualization
  275. ```
  276. Verify the package (same checks CI runs):
  277. ```bash
  278. python3 -m unittest discover -s tests
  279. python3 scripts/validate_skill.py # → OK: skill package passed validation
  280. ```
  281. The validator re-renders every committed SVG and the demo deck from source specs and fails on any drift — the gallery cannot silently rot.
  282. ## Star It, Break It, Share It
  283. If this turned your rough notes into a usable slide, **star the repo** — stars are how other people find tools that actually render instead of hallucinate.
  284. Even better contributions:
  285. - A messy input and the slide it produced ([Discussions](https://github.com/kgraph57/mckinsey-style-visualization-skill/discussions))
  286. - A business scenario that needs a pattern we don't have ([request template](https://github.com/kgraph57/mckinsey-style-visualization-skill/issues/new?template=example_request.md))
  287. - An output that's broken, confusing, or overconfident — it becomes a regression test
  288. [![Star History Chart](https://api.star-history.com/svg?repos=kgraph57/mckinsey-style-visualization-skill&type=Date)](https://star-history.com/#kgraph57/mckinsey-style-visualization-skill&Date)
  289. <details>
  290. <summary><strong>Repository map & package internals</strong></summary>
  291. | Layer | What It Does | File |
  292. | ---------------------- | ----------------------------------------------------------------------- | ----------------------------------------------------------------- |
  293. | Skill entrypoint | Tells agents when and how to use the skill | [SKILL.md](SKILL.md) |
  294. | Input triage | Maps any input to a pattern family | [input-triage.md](references/input-triage.md) |
  295. | Document profiles | Adapts format and tone per deliverable | [document-type-profiles.md](references/document-type-profiles.md) |
  296. | Pattern library | Comparison-type gate + 35-pattern catalog | [visualization-patterns.md](references/visualization-patterns.md) |
  297. | Style system | Tokens, palette, typography, chart rules | [style-system.md](references/style-system.md) |
  298. | Prompt templates | Reproducible spec formats | [prompt-templates.md](references/prompt-templates.md) |
  299. | Quality rubric | 24-point scoring + blocking gates + deck check | [quality-rubric.md](references/quality-rubric.md) |
  300. | Expert review loop | Adversarial pre-publication review | [expert-review-loop.md](references/expert-review-loop.md) |
  301. | SVG renderer | Spec JSON → styled SVG slide (22 patterns) | [render_slide_spec.py](scripts/render_slide_spec.py) |
  302. | Deck builder | SVG slides → animated single-file HTML deck | [build_html_deck.py](scripts/build_html_deck.py) |
  303. | Deck scaffolder | Copies a ready-made deck archetype into a working directory | [scaffold_deck.py](scripts/scaffold_deck.py) |
  304. | Report builder | Markdown → self-contained, print-to-A4 HTML report | [build_html_report.py](scripts/build_html_report.py) |
  305. | Speaker script builder | Deck manifest + `notes` → print-first, one-slide-per-page podium script | [build_speaker_script.py](scripts/build_speaker_script.py) |
  306. | Slide article builder | Deck manifest + `notes` → self-contained, top-to-bottom reading article | [build_html_article.py](scripts/build_html_article.py) |
  307. | Structural review | Lint a drafted spec document | [review_slide_spec.py](scripts/review_slide_spec.py) |
  308. | Validation | Package integrity + render parity | [validate_skill.py](scripts/validate_skill.py) |
  309. Iterative review-loop examples (draft → review → revision, four scenarios) live in [examples/review-loop/](examples/review-loop). Distribution and commercial docs: [MARKETPLACE.md](MARKETPLACE.md), [BUYER_BRIEF.md](BUYER_BRIEF.md), [ROADMAP.md](ROADMAP.md), [SECURITY.md](SECURITY.md), [CHANGELOG.md](CHANGELOG.md).
  310. </details>
  311. ## Disclaimer
  312. This is an independent skill package. It is not affiliated with, endorsed by, or sponsored by McKinsey & Company, Boston Consulting Group, Bain & Company, or any other consulting firm. Named firms may appear only as common style references or search terms.
  313. ## License
  314. MIT. See [LICENSE](LICENSE).
  315. ### Reference-led slides and editable Word briefs
  316. The [six-firm design study](references/consulting-design-study.md) records actual pages and exhibits, with an explicit evidence trail. Use the [reproduction workflow](references/reference-reproduction.md) to choose a reference and compare hierarchy, geometry, chart encoding and pagination.
  317. [Working templates](templates/reference-layouts/) include an analytical chart with a commentary rail, compact HTML report, and editable A4 Word brief. Word export is optional and requires Node.js packages `docx` and `sharp`; core SVG/HTML rendering remains Python-standard-library only. Chart figures in Word are SVGs with PNG fallbacks, while text and tables remain editable.
  318. ## HTML to PDF
  319. Use JSON for charts and Markdown for the narrative. Generate HTML, review it in the browser, and export that same HTML to PDF. HTML is the primary layout artifact; Word is an optional separate export. Reports use A4 print styles; decks use one 16:9 slide per page.
  320. ```bash
  321. python3 -m pip install playwright
  322. python3 scripts/build_html_report.py templates/reference-layouts/decision-brief.md -o brief.html
  323. python3 scripts/export_pdf.py brief.html -o brief.pdf
  324. python3 scripts/export_pdf.py examples/demo-deck.html -o deck.pdf
  325. ```
  326. PDF export requires installed Google Chrome or Chromium (`--browser /path/to/browser` for a custom executable). SVG and HTML generation remain Python-standard-library only. Alternatively, open the generated HTML, choose **Save as PDF**, and select the browser’s PDF destination. Inspect every page after changing content; longer reports may need deliberate page breaks.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.