Creating Consultant-Quality Slides with AI Using consulting-pptx-skill
機械翻訳 / Machine-translated
Original article: Creating Consultant-Quality Slides with AI Using consulting-pptx-skill (cccskills)
Skill page: consulting-pptx-skill
What you'll learn from this article
When you have AI create meeting slides, the appearance tends to vary from page to page, making them hard to use as-is.
consulting-pptx-skill is a skill that builds decks based on the design spec slide-rules.md and a collection of 62 HTML component types, then finishes them with automated checks using check_deck.py.
This article introduces what it can do and how to install it.
It also covers how to use it to add pages in the same format to an existing PowerPoint file.
consulting-pptx-skill is a skill for creating slides of a quality suitable for executive meetings.
At its core is the design spec references/slide-rules.md, which the agent reads in full before starting any creation work.
It then assembles a draft from the HTML component library and refines it within the bounds of the spec.
The output is a 16:9 HTML file and a PDF printed via Chrome.
In the HTML, each section corresponds to one slide.
If you want a PowerPoint file, simply make that explicit in your request and it will convert the file at the end.
The spec consolidates rules for both the content and appearance of documents.
Here are a few highlights from what is listed in SKILL.md:
The component library is split into two HTML files.
The additional file is used when the basics are not enough.
| Component Library | Number of Types | Main Contents |
|---|---|---|
| Basic freeform_parts_16x9.html | 27 | Cover, overview map, chevron arrows, premise→conclusion, axis-based tables, evaluation tables, distribution charts, etc. |
| Additional freeform_parts_more_16x9.html | 35 | Executive summary, stacked bar charts, bridge charts, scatter plots, matrices, roadmaps, Gantt charts, etc. |
Drafts are generated as a single HTML file by listing component numbers in scripts/new_deck.py.
The script handles CSS consolidation and page number resequencing.
There is also assets/SlideCatalog_16x9.pdf, a printed catalog of all 62 types, so you can browse them visually.
This skill positions the component catalog as an idea book for layouts.
The philosophy is: rather than forcing slides to fit a type, choose the type that fits your story — and if none fits, discard it and compose freely.
Questioning on a per-slide basis whether each type is appropriate is also part of the process.
During finishing, scripts/check_deck.py mechanically checks the spec, and issues are corrected until there are zero FAILs.
Remaining placeholders and titles that still show the component type name are also counted as FAILs.
The subsequent scripts/check_layout.mjs actually renders the slides and detects overlaps, overflows, and pages where more than 40% of the printable area is empty.
After the automated checks, the process moves on to a "fresh-eyes review."
This involves having a separate agent — one that has not been involved in the creation — read through the deck.
Finally, the deck is exported to PDF and every page is reviewed visually.
SKILL.md explicitly states that issues such as collapsed bars or a blank lower half of a page can only be caught by visual inspection.
This skill is suited for people who want to use AI to draft internal meeting or proposal slides to a consistent quality standard.
If you struggle with AI-generated slides looking different every time, this approach — fixing the standard through a spec and automated checks — may be a good fit.
On the other hand, this may feel heavy if you just need to create a single slide quickly.
There are many steps, from reading the spec in full to visually reviewing every page.
The design rules are also strict — for example, no rounded corners — so it may not be a good fit for documents where you want creative freedom in design.
To install from the terminal, run the following command:
npx skills add https://github.com/carnot-tech/jinba-consulting-pptx-skill --skill consulting-pptx-skill
To install by asking Claude Code, send the following message exactly as written:
次の Agent Skill をインストールしてください。
https://github.com/carnot-tech/jinba-consulting-pptx-skill
まず SKILL.md と付属ファイルの中身を確認し、不審な処理（外部への送信、認証情報の読み取りなど）がないことを確かめてから、~/.claude/skills/consulting-pptx-skill/ に配置してください。
If you want to use it across all projects, place it in ~/.claude/skills/.
If you only want to use it for a specific project, place it in that project's .claude/skills/ directory.
The distribution source is the GitHub repository carnot-tech/jinba-consulting-pptx-skill.
SKILL.md includes trigger phrase examples such as "create consultant-quality slides," "build a deck following the spec," "choose from the component catalog," and "add a page to this .pptx in the same format."
Adding your objective and content to these phrases makes it easier for the skill to proceed according to its steps.
I need to present the status of next fiscal year's new business initiatives at an executive meeting.
Please create consultant-quality slides, around 10 pages.
For this kind of request, the process follows the steps in SKILL.md in this order:
What you receive back is an HTML file and PDF that have passed the automated checks.
Please create a proposal document for external use as a deck following the spec.
The list of client names is at ~/.config/deck-forbidden-terms.txt.
For decks going outside the organization, the --forbid option is used to check for any accidentally included client names or project codes.
It also detects terms left in HTML comments or attributes, but the terms themselves do not appear in the output.
Please create one page to add to this .pptx in the same format, showing the trend in market size.
Please provide it as a PPTX file.
In this case, rather than using a conversion step, pages are built directly on top of the master of the provided document (slide-rules §8.7).
The process involves measuring the formatting with measure_deck.py and writing it to skin.json, then assembling the page with deck_pptx.py and checking it with check_deck.py --house.
What you receive is a file containing only the pages to be inserted; the user is responsible for inserting them into the document.
The output format varies depending on how you phrase your request.
Building directly on top of an existing document's master only happens when an existing PowerPoint is provided and PPTX output is explicitly requested.
Conversion to PPTX is also limited to cases where you explicitly specify "as a PPTX" or "convert to PowerPoint."
| How You Ask | Output | Main Scripts Used |
|---|---|---|
| No format specified | HTML and PDF | new_deck.py, check_deck.py, check_layout.mjs |
| Explicitly specify "as a PPTX" | Editable PPTX | html_to_pptx.py |
| Provide an existing .pptx and request PPTX output | PPTX file containing only the pages to insert | measure_deck.py, deck_pptx.py |
Python 3 is required to run the skill.
check_layout.mjs uses Playwright, so install it in advance with npm run setup.
PDF generation is done via Chrome headless printing; the examples in SKILL.md use macOS paths.
PPTX conversion requires Node 22 or later, Chrome, and python-pptx.
SVG charts and diagrams are converted to images, and the numerical values inside them cannot be edited.
Fonts are replaced with Yu Gothic and Yu Mincho, and line endings may shift by one character.
For this reason, visual inspection cannot be skipped.
Always run check_deck.py on a PPTX built on an existing document before opening it in PowerPoint.
If a malformed file is opened, PowerPoint will leave a repair dialog behind.
Regarding security: it is worth knowing that the skill may suggest pulling in updates or creating a pull request.
At the start of each session, it checks for updates with git fetch, and any broadly applicable suggestions are proposed once as a PR to the main repository.
It will only proceed to gh pr create if you give consent.
Even so, to ensure nothing like client names gets mixed in, review the diff yourself before pushing.
The license is MIT.
If you want to make corrections to the finished PDF, nano-pdf is an option.
It is a skill that lets you give instructions in natural language — such as changing a title or fixing a typo — for specific pages of a PDF.
If you want to compile your explanation in document form rather than as slides, technical-documentation is available.
It is a skill that supports the creation and review of technical documents and instruction files for agents.
Yes, you can.
If you explicitly say "as a PPTX" or "convert to PowerPoint," the finished HTML will be converted using html_to_pptx.py.
The policy is to make edits on the HTML side and run the conversion only once at the very end.
If you place a slide-rules.local.md or forbid.txt in the local/ folder, they will be read after the main spec.
Since the main files are not modified, there will be no conflicts when pulling in skill updates.
The default is a warm color scheme with an off-white background and dark brown text.
You can change this using the :root tokens at the top of the <style> section in each component library file.
Navy-based values are also included as comments.
No, it is not finished.
The automated checks only look for overlaps, overflows, and spec violations.
Visually reviewing every page after exporting to PDF is also part of the process.
consulting-pptx-skill is a skill that standardizes slide quality through a design spec and automated checks.
The 62-type component library is used as an idea book, with components assembled and rearranged to fit the story.
It can be used to draft new decks as well as to add pages to existing PowerPoint files.
The process has many steps, making it best suited for situations where you want to produce meeting or proposal materials at a consistent level of quality.
For more details, see the cccskills page.
This article is a reprint of the cccskills article "Creating Consultant-Quality Slides with AI Using consulting-pptx-skill."
Details about the skill and installation instructions can be found on the cccskills consulting-pptx-skill page.