knowledge-cat-ppt-skill
Story-first Agent Skill for creating, routing, and QA-checking PPT, HTML, and image-first presentation decks
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/gnipbao--knowledge-cat-ppt-skill)HTML
<a href="/listings/gnipbao--knowledge-cat-ppt-skill"><img src="/api/listings/gnipbao--knowledge-cat-ppt-skill/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Repository URL:
https://github.com/gnipbao/knowledge-cat-ppt-skill.git
Codex
git clone https://github.com/gnipbao/knowledge-cat-ppt-skill.git ~/.codex/skills/knowledge-cat-ppt-skill
Restart Codex or refresh local skills.
From a cloned repository:
python3 scripts/install_skill.py --agent codex --force
Claude Code
git clone https://github.com/gnipbao/knowledge-cat-ppt-skill.git ~/.claude/skills/knowledge-cat-ppt-skill
Restart Claude Code or refresh local skills.
From a cloned repository:
python3 scripts/install_skill.py --agent claude --force
Manual Install
Copy the whole folder into your agent's skills directory:
cp -R knowledge-cat-ppt-skill ~/.codex/skills/
or:
cp -R knowledge-cat-ppt-skill ~/.claude/skills/
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 · 383 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- ---
- name: knowledge-cat-ppt-skill
- description: "Create, critique, and repair high-quality presentation decks with a story-first, output-engine-aware workflow. Use when the user asks for PPT, PowerPoint, slides, deck, pitch deck, keynote, course deck, academic deck, consulting deck, HTML slides, web presentation, image-first slides, social carousel, speaker notes, deck outline, slide plan, template replication, deck review, deck polish, or conversion from documents, articles, Markdown, PDFs, URLs, or existing .pptx files. Also use when the user says Knowledge Cat PPT or asks for an industry-grade presentation skill."
- ---
- # Knowledge Cat PPT Skill
- ## Overview
- Knowledge Cat PPT is a presentation operating system for agents. Its job is to turn messy source material into a persuasive, teachable deck, choose the right production lane, and verify the result through content and visual QA.
- Do not treat "make slides" as a formatting task. First determine the audience, the decision or learning outcome, the story spine, and the output format. Then build the deck.
- ## Resource Guide
- Load only what the current task needs:
- - Read `references/benchmark-synthesis.md` when explaining the design philosophy, comparing PPT skill patterns, or improving this skill.
- - Read `references/benchmark-quality-gates.md` when the user asks for the best version, benchmark-grade output, open-source comparison, case-study evidence, or quality claims above normal client-ready delivery.
- - Read `references/engine-routing.md` before choosing native PPTX, HTML deck, image-first PPTX, or review-only mode.
- - Read `references/story-architecture.md` when turning source material into a deck brief, narrative spine, action titles, or slide plan.
- - Read `references/design-systems.md` when choosing style direction, layout family, visual tokens, imagery, or anti-generic design rules.
- - Read `references/template-replication.md` when the user provides an existing `.pptx`, screenshot, brand deck, style reference, or asks to clone a template.
- - Read `references/html-production-lock.md` before building production HTML decks, visual prototypes, browser-based talks, or HTML decks with local images/screenshots.
- - Read `references/html-visual-systems.md` after the HTML production lock when a browser deck needs benchmark-level visual rhythm, a reusable style package, or contact-sheet QA.
- - Read `references/style-template-library.md` when the user provides many PPT style prompts, asks for common PPT style websites, asks which style to choose, or wants Knowledge Cat to exceed Guizang-style HTML template depth.
- - Read `references/native-pptx-recipes.md` when building or repairing editable PowerPoint decks.
- - Read `references/html-deck-recipes.md` when building browser-based decks, fast visual prototypes, or single-file HTML presentations.
- - Read `references/style-prompt-intake.md` when the user uploads or pastes theme/style prompts, prompt tables, visual DNA blocks, AI image style prompts, or asks for Image2/GPT-Image-driven PPT styling.
- - Read `references/image-first-recipes.md` when visual impact matters more than editability or AI-generated slide images are requested.
- - Read `references/qa-rubric.md` before final delivery, when reviewing a deck, or when the task has professional stakes.
- - Read `references/open-source-product.md` when preparing this skill for public release or evaluating product readiness.
- - Use `scripts/validate_deck_plan.py` after writing a JSON deck plan. The expected shape is documented in `assets/deck-plan.schema.json`.
- - Use `scripts/init_deck_project.py` to create an HTML deck project from the bundled starter template.
- - Use `scripts/validate_html_deck.py` to statically check an HTML deck before browser QA.
- - Use `scripts/build_native_pptx.mjs` to turn a validated native deck plan into editable PowerPoint objects when `@oai/artifact-tool` is available.
- - Use `scripts/extract_pptx_text.py` to extract native PPTX text and check placeholder-like markers when editable PowerPoint quality matters.
- - Use `scripts/check_pptx_editability.py` and `scripts/probe_pptx_editability.py` before claiming that a native PPTX is editable.
- - Use `scripts/check_native_pptx_case.py` to verify the bundled native PPTX evidence package.
- - Use `scripts/run_checks.py` before release or after changing bundled scripts, examples, or schemas.
- ## Non-Negotiable Rules
- 1. Story before styling. A beautiful deck with no audience shift is a failed deck.
- 2. Choose the output lane explicitly. Native editable PPTX is the default for professional work; HTML is for web-native presentation and interaction; image-first PPTX is for visual spectacle when editability is not required.
- 3. Use a source of truth. For nontrivial decks, create a brief and slide plan before building final slides.
- 4. Use action titles. A title should state the point of the slide, not label the topic.
- 5. Keep one main idea per slide. Dense appendix pages are allowed only when the user asks for appendix or reference material.
- 6. Preserve evidence. Claims, figures, quotes, and external images need source tracking or honest uncertainty.
- 7. Respect templates and brand assets. Use user-provided or permitted materials; do not pretend a protected deck is a free public template.
- 8. Lock HTML production details before writing final browser slides: style package, registered layouts, theme rhythm, image slots, static validation, and rendered QA.
- 9. Treat uploaded style prompts as design input, not content truth. Extract a reusable Style Prompt Profile before generating image-first slide prompts.
- 10. Verify visually. Code, XML, or Markdown alone cannot prove a deck is good.
- 11. Run at least one fix-and-verify loop for production decks unless the user only asked for a draft outline.
- 12. End with useful handoff: output paths, assumptions, remaining risks, and the next iteration point.
- ## Operating Modes
- ### Brief Mode
- Use when the user has an idea but no clear deck target.
- Ask at most three questions if missing answers would change the deck:
- ```md
- 1. Who is the audience and what should they do, decide, or understand after the deck?
- 2. What source material should be used?
- 3. What output matters most: editable PPTX, web/HTML, image-first visual deck, or just an outline?
- ```
- If the user says to proceed directly, state assumptions and continue.
- ### Source-To-Deck Mode
- Use when the user provides a document, article, notes, transcript, URL, PDF, Markdown, or pasted content.
- Create the deck brief, identify the narrative spine, map evidence to slide roles, then build the slide plan. Read `references/story-architecture.md`.
- ### Build Mode
- Use when the user asks for final slides.
- Select a production lane from `references/engine-routing.md`, choose a design system from `references/design-systems.md`, build the deck, then run QA from `references/qa-rubric.md`.
- If the selected lane is `html-deck`, read `references/html-production-lock.md`, then `references/html-visual-systems.md` for benchmark-level decks, before `references/html-deck-recipes.md`.
- If the user uploaded or selected a theme/style prompt, read `references/style-template-library.md` when it is a large style table or known preset, then `references/style-prompt-intake.md` before `references/image-first-recipes.md`, and prefer `image-first-pptx` unless editability, exact text, charts, tables, citations, or stakeholder collaboration matter more.
- ### Template Mode
- Use when the user provides a `.pptx`, image, screenshot, or brand sample as a template.
- Read `references/template-replication.md`. Extract the template profile first, then map each planned slide to a compatible layout. Do not reuse a highly distinctive layout too many times.
- ### Review And Repair Mode
- Use when the user provides an existing deck or asks whether it is good.
- Review story, audience fit, slide clarity, visual system, evidence, editability, and technical defects. Lead with prioritized issues, then propose or perform repairs.
- ### Publishing Mode
- Use when the user needs speaker notes, handouts, PDF export, video narration, social cards, Xiaohongshu carousel, WeChat cover, or other downstream formats.
- Keep the original deck source of truth intact and derive outputs from it.
- ### Productization Mode
- Use when improving this skill itself, preparing a public repository, writing release docs, or evaluating open-source readiness.
- Read `references/open-source-product.md` and `references/benchmark-quality-gates.md`. Keep `SKILL.md` concise, move detailed production guidance into references, and run bundled checks before claiming release readiness.
- ## Core Workflow
- ### 1. Triage The Request
- Classify:
- - Deck type: investor, sales, strategy, teaching, academic, consulting, product, keynote, internal report, social carousel, courseware, or other.
- - Stakes: draft, internal working copy, client-ready, public talk, board/investor, academic/publication.
- - Output lane: native-pptx, html-deck, image-first-pptx, or review-only.
- - Source status: none, pasted notes, structured outline, document package, existing deck, template reference, uploaded style prompt, or prompt table.
- - Deadline and iteration budget.
- Open with:
- ```md
- Deck type:
- Audience:
- Outcome:
- Output lane:
- Source status:
- Primary risk:
- Next action:
- ```
- For small requests, this can be one short paragraph.
- ### 2. Build The Deck Brief
- For nontrivial decks, produce:
- ```md
- Title:
- Audience:
- Moment:
- Desired audience shift:
- Decision or learning outcome:
- Main promise:
- Scope:
- Output lane:
- Format:
- Page count:
- Source materials:
- Style prompt source:
- Design posture:
- Must include:
- Must avoid:
- QA level:
- ```
- Do not over-ask. Infer safe defaults where possible.
- ### 3. Synthesize The Story
- Choose a spine:
- - Situation -> tension -> insight -> proof -> action
- - Problem -> failed old approach -> new mechanism -> evidence -> next step
- - Context -> finding -> implication -> recommendation
- - Question -> method -> result -> limitation -> conclusion
- - Hook -> transformation -> steps -> proof -> call to action
- Then write the ghost deck: the action titles alone should tell the story.
- ### 4. Create The Slide Plan
- Each slide should have:
- ```md
- Slide:
- Layout:
- Action title:
- Role:
- Key message:
- Evidence:
- Visual:
- Speaker note:
- Source refs:
- Asset needs:
- ```
- For JSON plans, validate with:
- ```bash
- python3 scripts/validate_deck_plan.py path/to/deck-plan.json
- ```
- Fix validation failures before building final slides.
- ### 5. Choose The Production Lane
- Use the decision matrix in `references/engine-routing.md`.
- Default decisions:
- - Business, investor, consulting, academic, training, legal, finance, or collaborative decks -> native editable PPTX.
- - Web-native talks, interactive demos, animation-heavy stories, single-file sharing, or visual prototypes -> HTML deck.
- - Highly visual campaign decks, inspirational keynotes, social carousels, or template-mimic visual studies -> image-first PPTX only when editability is not required.
- - Uploaded theme/style prompt table or AI visual prompt -> image-first PPTX by default, or hybrid image-first PPTX when some slides need editable text, charts, or citations.
- - Existing deck feedback -> review-only first, then repair if asked.
- After choosing the lane, load the matching recipe:
- - Native editable PPTX -> `references/native-pptx-recipes.md`
- - Browser-based deck -> `references/html-production-lock.md`, then `references/html-deck-recipes.md`
- - Image-first PPTX -> `references/style-prompt-intake.md` when a user style prompt exists, then `references/image-first-recipes.md`
- ### 6. Build The Design System
- Select a design posture from `references/design-systems.md`. Define:
- - Layout rhythm
- - Typography scale
- - Color tokens
- - Evidence treatment
- - Image style and crop ratios
- - Chart style
- - Motion level, if any
- - Accessibility constraints
- Avoid generic AI aesthetics: random gradients, decorative orbs, over-rounded cards, low-contrast gray text, inconsistent spacing, and repeated title-plus-bullets.
- ### 7. Produce The Deck
- Use the best available local capability for the selected lane. If a specialized presentation, PPTX, browser, image, or document skill is available, compose with it rather than rewriting its job here.
- Maintain a source-of-truth file when possible:
- - `deck-brief.md` for strategy and constraints
- - `deck-plan.md` or `deck-plan.json` for slide structure
- - output files in a predictable project folder
- - `qa-report.md` for production decks
- For HTML decks, prefer the bundled starter:
- ```bash
- python3 scripts/init_deck_project.py path/to/project --title "Deck Title"
- python3 scripts/validate_html_deck.py path/to/project/index.html
- ```
- Each final HTML slide must declare `data-layout`, `data-title`, `data-role`, and `data-theme`. Local images must use `images/` paths plus `data-image-slot` and target ratio metadata. Treat static validation errors as blockers.
- For native PPTX, follow `references/native-pptx-recipes.md`. A validated plan can use the bundled builder when the current environment provides `@oai/artifact-tool`:
- ```bash
- node scripts/build_native_pptx.mjs \
- --plan path/to/deck-plan.json \
- --output path/to/output.pptx \
- --workspace path/to/prepared-artifact-workspace \
- --preview-dir path/to/screenshots \
- --inspection path/to/inspection.ndjson
- ```
- The builder reopens the exported PPTX before producing previews and inspection evidence. If the dependency is unavailable, compose with a verified native-PPTX skill or renderer and keep the same QA contract. For native PPTX, run:
- ```bash
- python3 scripts/extract_pptx_text.py path/to/output.pptx --fail-on-placeholders
- python3 scripts/check_pptx_editability.py path/to/output.pptx --fail-on-image-only-slides
- python3 scripts/probe_pptx_editability.py path/to/output.pptx
- ```
- For image-first PPTX, follow the lane-specific recipe and state the editability tradeoff.
- ### 8. QA And Iterate
- Use `references/qa-rubric.md`.
- Minimum production QA:
- 1. Content QA: title order, missing content, typos, unsupported claims, placeholder text.
- 2. Visual QA: render slides or open the HTML, inspect for overflow, contrast, alignment, collision, spacing, and image crop issues.
- 3. Story QA: ghost deck, audience shift, duplicated ideas, weak ending.
- 4. Format QA: file opens, assets resolve, fonts are reasonable, links work when promised.
- 5. Native editability QA: inspect object types, reject image-only impostors, and run a reversible edit probe when editability is promised.
- 6. Fix and recheck affected slides.
- For release or repository work, also run:
- ```bash
- python3 scripts/run_checks.py
- ```
- If the first pass finds no problems, inspect again more critically.
- When claiming benchmark-level quality, use `references/benchmark-quality-gates.md` and provide the evidence artifacts behind the score.
- ## Output Protocols
- ### Deck Brief
- ```md
- Deck type:
- Audience:
- Outcome:
- Main promise:
- Narrative spine:
- Output lane:
- Format:
- Page count:
- Source materials:
- Style prompt source:
- Design posture:
- Assumptions:
- Next action:
- ```
- ### Slide Plan
- ```md
- | # | Layout | Action title | Role | Key message | Evidence | Visual | Notes |
- |---|---|---|---|---|---|---|---|
- ```
- ### Review Report
- ```md
- Overall score:
- P0 issues:
- P1 issues:
- P2 improvements:
- Story diagnosis:
- Visual diagnosis:
- Evidence diagnosis:
- Technical diagnosis:
- Recommended repair sequence:
- ```
- ### Delivery Note
- ```md
- Created:
- Output lane:
- Files:
- QA performed:
- Key assumptions:
- Known limitations:
- Best next iteration:
- ```
- ## Boundaries
- - Do not fabricate facts, sources, market sizes, citations, or user metrics.
- - Do not flatten slides into images when the user needs editable PowerPoint.
- - Do not force native PPTX when the user clearly wants a web-native presentation.
- - Do not create a huge final deck before agreeing on the story unless the user explicitly asks for a first draft.
- - Do not overuse the same layout, theme, transition, or visual trick.
- - Do not treat a template as permission to copy copyrighted assets.
- - Do not hide tradeoffs. If the chosen lane sacrifices editability, animation, fidelity, accessibility, or portability, say so.
- - Do not claim final quality without a QA pass.
- ## Quality Standard
- Score production outputs out of 100:
- - Audience and outcome fit: 15
- - Narrative spine and ghost deck: 20
- - Slide clarity and action titles: 15
- - Evidence quality and source traceability: 15
- - Visual system and layout discipline: 15
- - Output-lane correctness and technical reliability: 10
- - QA loop and handoff: 10
- Below 70: do not deliver as final. 70-84: workable draft. 85-94: client-ready with minor risk. 95+: benchmark-level only when the gate evidence in `references/benchmark-quality-gates.md` is present.
- Before final response, confirm:
- - Did the deck have a clear audience shift?
- - Did the output lane match the user's real need?
- - Did each slide have one main job?
- - Did the visual system serve the argument?
- - Did evidence remain traceable?
- - Did at least one visual/content QA loop happen for final decks?
README.md · README · 432 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # Knowledge Cat PPT Skill
- Story-first presentation production for AI agents.
- [English](README.md) | [简体中文](README_CN.md) | [Bilingual](README_BILINGUAL.md)
- Knowledge Cat PPT is an open-source Agent Skill for creating, reviewing, and repairing presentation decks. It is designed for Codex, Claude Code, and other skill-aware coding agents. Instead of acting like a generic "make pretty slides" prompt, it gives the agent a production system: clarify the audience shift, choose the right output lane, build a slide plan, generate the deck, and verify the result.
- Current version: `0.10.0`
- ## Highlights
- - Story-first deck planning with audience, outcome, narrative spine, and action titles.
- - Output-lane routing for native editable PPTX, HTML decks, image-first PPTX, and review-only workflows.
- - Evidence tracking for claims, quotes, data, assumptions, screenshots, and source materials.
- - HTML deck starter template with keyboard navigation, print CSS, light/dark themes, and no external dependencies.
- - JSON deck-plan validator and HTML deck validator.
- - HTML production lock for registered layouts, theme rhythm, image slots, screenshots, and rendered QA.
- - Uploaded theme/style prompt intake for Image2/GPT-Image-first PPT workflows.
- - Curated 44-style template library with common PPT style-site radar and Guizang-surpass signature-pack targets.
- - Portfolio Minimal HTML signature pack with a 14-layout registry, 12-slide case study, QA artifacts, and a dedicated pack checker.
- - Native deck-plan-to-PPTX generator with editable text, shapes, charts, tables, and speaker notes.
- - Real native PPTX case study with re-imported slide renders, contact sheet, object inspection, editability report, and reversible text-object probe.
- - Open-source repository hygiene checks, GitHub Actions workflow, issue templates, and release checklist.
- - Compatible with both Codex local skills and Claude Code style skills.
- ## Three Production Modes
- | Native PPTX | HTML Deck | Image-First PPTX |
- |---|---|---|
- |  |  |  |
- | Editable PowerPoint work for real teams, client handoffs, charts, tables, and speaker notes. | Browser-native decks with keyboard navigation, print CSS, fast iteration, and visual QA. | High-impact visual decks for social carousels, campaigns, and keynote-style moments. |
- ## Compatibility
- | Agent environment | Status | Install path |
- |---|---|---|
- | Codex | Supported | `~/.codex/skills/knowledge-cat-ppt-skill` |
- | Claude Code | Supported | `~/.claude/skills/knowledge-cat-ppt-skill` |
- | Other skill-aware agents | Should work if they read `SKILL.md` plus bundled resources | Agent-specific |
- The skill itself is plain Markdown, Python, JavaScript, JSON, and HTML. Validators use only the Python standard library. The optional bundled native PPTX builder requires Node.js plus `@oai/artifact-tool` in a prepared workspace.
- ## What It Does
- Knowledge Cat PPT helps an agent:
- - Turn rough ideas, notes, documents, transcripts, URLs, PDFs, or research into a deck brief.
- - Build a slide plan with action titles, slide roles, evidence, visuals, notes, and source references.
- - Choose the correct output lane before production.
- - Parse uploaded theme/style prompts into an image-first Style Prompt Profile.
- - Generate or guide production of HTML decks, editable PowerPoint decks, or image-first visual decks.
- - Review existing decks for story, evidence, visual system, editability, and technical risks.
- - Run validation before claiming a deck is ready.
- ## Why It Exists
- Most AI slide workflows fail for three reasons:
- 1. They start with visual style before defining the audience outcome.
- 2. They choose the wrong output format, such as flattened images when the user needs editable PowerPoint.
- 3. They skip rendered QA and ship slides that only looked correct in code.
- Knowledge Cat PPT treats a deck as a production system. Story, engine, design, evidence, and QA must agree.
- ## Install
- Repository URL:
- ```txt
- https://github.com/gnipbao/knowledge-cat-ppt-skill.git
- ```
- ### Codex
- ```bash
- git clone https://github.com/gnipbao/knowledge-cat-ppt-skill.git ~/.codex/skills/knowledge-cat-ppt-skill
- ```
- Restart Codex or refresh local skills.
- From a cloned repository:
- ```bash
- python3 scripts/install_skill.py --agent codex --force
- ```
- ### Claude Code
- ```bash
- git clone https://github.com/gnipbao/knowledge-cat-ppt-skill.git ~/.claude/skills/knowledge-cat-ppt-skill
- ```
- Restart Claude Code or refresh local skills.
- From a cloned repository:
- ```bash
- python3 scripts/install_skill.py --agent claude --force
- ```
- ### Manual Install
- Copy the whole folder into your agent's skills directory:
- ```bash
- cp -R knowledge-cat-ppt-skill ~/.codex/skills/
- ```
- or:
- ```bash
- cp -R knowledge-cat-ppt-skill ~/.claude/skills/
- ```
- ## Quick Start
- Ask your agent:
- ```md
- Use $knowledge-cat-ppt-skill to turn my notes into an 8-slide client-ready deck. I need editable PPTX unless you think another output lane is better.
- ```
- For a deck review:
- ```md
- Use $knowledge-cat-ppt-skill to review this deck. Focus on story, evidence, visual clarity, and whether it is actually ready to send.
- ```
- For an HTML deck:
- ```md
- Use $knowledge-cat-ppt-skill to build a browser-based HTML deck from this outline. Make it keyboard navigable and run the bundled HTML validator.
- ```
- For the 44-style template library:
- ```md
- Use $knowledge-cat-ppt-skill. Choose the best style from the template library for my topic, explain the lane tradeoff, then create a deck brief and slide plan.
- ```
- For the Portfolio Minimal signature pack:
- ```md
- Use $knowledge-cat-ppt-skill. Build a browser-based HTML deck using the kc-24 Portfolio Minimal signature pack. Use the pack layout registry, include a local image slot, produce screenshots/contact sheet, and run the signature-pack checks.
- ```
- ## Output Lanes
- | Lane | Use when | Main tradeoff |
- |---|---|---|
- | `native-pptx` | PowerPoint editability, team collaboration, charts, tables, notes, client decks | Bundled builder requires a prepared `@oai/artifact-tool` workspace; imported-deck repairs still need a verified native editor |
- | `html-deck` | Web-native presentation, rapid visual iteration, browser preview, single-file sharing | Not a true editable PowerPoint file |
- | `image-first-pptx` | Social carousel, campaign deck, visual keynote, AI-generated slide surfaces | Lower editability |
- | `review-only` | Existing deck critique, repair planning, story/evidence diagnosis | Does not create a final deck until repair is requested |
- ## Native Editable PPTX Case
- The bundled native lane now includes an executable deck-plan builder and a real evidence package:
- ```txt
- examples/case-studies/native-editable/
- +-- deck-brief.md
- +-- deck-plan.json
- +-- knowledge-cat-native-editable.pptx
- +-- inspection.ndjson
- +-- editability-report.json
- +-- edit-probe.json
- +-- qa-report.md
- +-- screenshots/
- +-- slide-01.png ... slide-06.png
- +-- slide-01.layout.json ... slide-06.layout.json
- +-- contact-sheet.png
- ```
- The example contains native text, shapes, one chart, one table, and speaker notes on every slide. It contains no full-slide images.
- Validate the complete evidence package:
- ```bash
- python3 scripts/check_native_pptx_case.py
- ```
- Build another native deck from a validated plan after preparing an `@oai/artifact-tool` workspace:
- ```bash
- node scripts/build_native_pptx.mjs \
- --plan path/to/deck-plan.json \
- --output path/to/output.pptx \
- --workspace path/to/prepared-artifact-workspace \
- --preview-dir path/to/screenshots \
- --inspection path/to/inspection.ndjson
- ```
- Then run text, object, and reversible edit checks:
- ```bash
- python3 scripts/extract_pptx_text.py path/to/output.pptx --fail-on-placeholders
- python3 scripts/check_pptx_editability.py path/to/output.pptx --fail-on-image-only-slides
- python3 scripts/probe_pptx_editability.py path/to/output.pptx
- ```
- ## HTML Deck Starter
- Create a sample HTML deck:
- ```bash
- python3 scripts/init_deck_project.py /tmp/kc-demo-deck --title "Knowledge Cat Demo"
- python3 scripts/validate_html_deck.py /tmp/kc-demo-deck/index.html
- ```
- Open:
- ```txt
- /tmp/kc-demo-deck/index.html
- ```
- The starter includes:
- - 16:9 desktop slide canvas
- - Mobile stacked fallback
- - Keyboard navigation
- - Print CSS
- - Light/dark theme switching
- - Action-title aware slide structure
- - No external dependencies
- ## Style Template Library
- Knowledge Cat includes a curated 44-style template library in `references/style-template-library.md`. The library turns pasted PPT style prompts into a routing system:
- - style seeds such as `kc-24` Portfolio Minimal, `kc-25` Minimal Data Story, `kc-28` Bold Editorial Magazine, `kc-26` Dark SaaS Product, and `kc-11` Architectural Blueprint
- - default output lanes for each style
- - protected-style normalization rules
- - a priority path for building signature packs that can compete with Guizang-style HTML deck depth
- Copy-ready prompts live in:
- ```txt
- docs/TEMPLATE_LIBRARY_PROMPTS.md
- ```
- ## Portfolio Minimal Signature Pack
- The first implemented signature pack is `kc-24` Portfolio Minimal:
- ```txt
- assets/html-signature-packs/portfolio-minimal/
- +-- README.md
- +-- layout-registry.json
- +-- template.html
- ```
- It includes 14 registered `custom-pm-*` layouts and a 12-slide case study:
- ```txt
- examples/case-studies/portfolio-minimal/
- ```
- Run the pack gate:
- ```bash
- python3 scripts/check_signature_pack.py portfolio-minimal
- ```
- The Portfolio Minimal case study includes browser-captured PNG slide screenshots and a browser contact sheet, so quality claims are backed by visual artifacts rather than code inspection alone.
- ## Deck Plan Validation
- Validate a JSON deck plan:
- ```bash
- python3 scripts/validate_deck_plan.py examples/sample-deck-plan.json
- ```
- The expected structure is documented in:
- ```txt
- assets/deck-plan.schema.json
- ```
- ## Full Validation
- Run all bundled checks:
- ```bash
- python3 scripts/run_checks.py
- ```
- Run repository hygiene checks:
- ```bash
- python3 scripts/check_repo.py
- ```
- The checks validate:
- - sample deck plan
- - generated sample HTML deck
- - HTML structure
- - Portfolio Minimal signature pack and case study
- - native PPTX text extraction, object inspection, and reversible edit-probe self-tests
- - real native PPTX case, re-imported renders, contact sheet, and QA evidence
- - required repository files
- - changelog/version consistency
- - cache and generated-file hygiene
- ## Repository Layout
- ```txt
- knowledge-cat-ppt-skill/
- +-- SKILL.md
- +-- README.md
- +-- README_CN.md
- +-- README_BILINGUAL.md
- +-- VERSION
- +-- CHANGELOG.md
- +-- CONTRIBUTING.md
- +-- SECURITY.md
- +-- LICENSE
- +-- .github/
- | +-- workflows/validate.yml
- | +-- ISSUE_TEMPLATE/
- +-- agents/
- | +-- openai.yaml
- +-- assets/
- | +-- deck-plan.schema.json
- | +-- html-template/
- | +-- index.html
- | +-- html-signature-packs/
- | +-- portfolio-minimal/
- +-- examples/
- | +-- retest-prompts.md
- | +-- sample-deck-plan.json
- | +-- sample-html-deck/
- | +-- case-studies/
- | +-- portfolio-minimal/
- | +-- native-editable/
- +-- references/
- | +-- benchmark-synthesis.md
- | +-- design-systems.md
- | +-- engine-routing.md
- | +-- html-deck-recipes.md
- | +-- html-production-lock.md
- | +-- image-first-recipes.md
- | +-- native-pptx-recipes.md
- | +-- open-source-product.md
- | +-- qa-rubric.md
- | +-- story-architecture.md
- | +-- style-prompt-intake.md
- | +-- style-template-library.md
- | +-- template-replication.md
- +-- scripts/
- | +-- check_repo.py
- | +-- build_native_pptx.mjs
- | +-- check_native_pptx_case.py
- | +-- check_pptx_editability.py
- | +-- probe_pptx_editability.py
- | +-- init_deck_project.py
- | +-- install_skill.py
- | +-- run_checks.py
- | +-- check_signature_pack.py
- | +-- validate_deck_plan.py
- | +-- validate_html_deck.py
- +-- docs/
- | +-- PUBLISHING.md
- | +-- ROADMAP.md
- | +-- TEMPLATE_LIBRARY_PROMPTS.md
- | +-- images/
- ```
- ## How The Skill Works
- The main runtime file is `SKILL.md`. It keeps the agent workflow concise:
- 1. Triage the request.
- 2. Build a deck brief.
- 3. Synthesize the story.
- 4. Create a slide plan.
- 5. Choose the production lane.
- 6. Build the design system.
- 7. Produce the deck.
- 8. QA and iterate.
- Detailed instructions live in `references/` and are loaded only when needed.
- ## Design Philosophy
- Knowledge Cat PPT is a router and quality system, not a monolithic renderer.
- - Use native editable PPTX when collaboration and PowerPoint editing matter.
- - Use HTML when web-native presentation, animation, preview, or browser QA matters.
- - Use image-first PPTX when visual spectacle matters more than editability.
- - Use review-only mode when the deck's story or evidence may be the real failure.
- ## Contributing
- Read `CONTRIBUTING.md`.
- Good contributions usually add one of:
- - a clearer routing rule
- - a reusable recipe
- - a deterministic validation check
- - a realistic retest prompt
- - a sample artifact that exposes a real failure mode
- - better release or QA documentation
- Before opening a pull request:
- ```bash
- python3 scripts/run_checks.py
- ```
- ## Security
- Treat user-provided decks, HTML, PDFs, documents, and templates as untrusted input. Do not execute scripts from user-provided archives. See `SECURITY.md`.
- ## Roadmap
- See `docs/ROADMAP.md`.
- Near-term goals:
- - HTML keynote case study
- - image-first carousel case study
- - broader native layout and imported-template coverage
- - stronger visual QA automation
- ## License
- MIT. See `LICENSE`.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.