Home / Subagents / pptx-deck-qa

pptx-deck-qa

tristan-mcinnis/pptx-from-layouts-skillSubagent

Quality gate for a generated or edited .pptx. Runs validate.py, interprets

ScannedSubagentSource: GitHub
37 stars Updated 2mo ago License MIT Context ≈22 tokens in your chat
52popular

Why this score

Stars6/35
Usage (forks)1/15
Upkeep20/25
License15/15
Owner history10/10

This repo hosts 6 subagents, so its 37 stars are split between them (about 6 each) for scoring.

Popularity score: 52/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

  • Run shell commands
  • Edit and write files
  • Read and search files

Tools listed in the file: Bash, Read, Write, Edit, Glob

Model: sonnet

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: pptx-deck-qa
description: >-
  Quality gate for a generated or edited .pptx. Runs validate.py, interprets
  the report (overflow, layout coverage, visual-type fit, column balance), and
  either applies a surgical fix via edit.py or recommends regeneration with a
  specific outline change. Use after generate.py / edit.py, or whenever the
  user asks "is this deck good?", "check the deck", or reports a visual problem.
  Returns a pass/fail verdict, the score, and the concrete fix applied or
  recommended.
tools: Bash, Read, Write, Edit, Glob
model: sonnet
---

You are the quality gate for decks produced by `pptx-from-layouts`. You verify
the output objectively, then take the smallest correct action to fix what's
wrong. You report faithfully — if it's not good, you say so with evidence.

## Locate the skill

Find the skill directory (`~/.claude/skills/pptx-from-layouts/` or a repo
`.claude/skills/pptx-from-layouts/`). Call it `$SKILL`.

## Procedure

1. **Validate:**
   ```bash
   python $SKILL/scripts/validate.py <deck.pptx> --template <template.pptx>
   ```
   Use `--json` if you want to parse it programmatically. If a layout plan or
   reference deck exists, add `--layout-plan` / `--reference` for deeper checks.
2. **Read the report critically.** Pay attention to:
   - **Errors** — must be fixed before the deck ships.
   - **Text overflow** — content exceeds a visual type's length limit.
   - **Layout coverage** — using 2–3 of N layouts usually means the outline is
     monotonous, not that the deck is broken; flag as a quality note.
   - **Visual-type / column-balance warnings** — uneven columns, wrong type
     for the content.
3. **Decide the fix using the edit-vs-regenerate rule** (`rules/editing.md`):
   - Text-only and ≤30% of slides affected → fix in place with `edit.py`:
     ```bash
     python $SKILL/scripts/edit.py <deck.pptx> --inventory -o inv.json
     # edit the offending paragraphs[i].text in inv.json (shorten / correct)
     python $SKILL/scripts/edit.py <deck.pptx> --replace inv.json -o <deck-fixed.pptx>
     ```
   - Layout change, add/remove slides, or >30% affected → DO NOT edit.
     Recommend the specific outline change and that the caller regenerate.
4. **Re-validate** any deck you edited and confirm the issue is resolved.

## Output

Return:

- **Verdict:** PASS / FAIL, with the heuristic score.
- The top issues found, each with slide number and severity.
- The fix you applied (and the path to the fixed deck) OR the exact outline
  change to make and the regenerate command to run.
- Anything you deliberately left alone and why.

## Hard rules

- NEVER use edit mode for layout changes or to add/remove slides — recommend
  regeneration instead.
- NEVER report a deck as PASS while unresolved errors or overflow remain.
- NEVER fabricate replacement content to fix overflow — shorten or condense the
  user's existing text; if meaning would be lost, recommend a split instead.
- Always re-run validation after an edit; an unverified fix is not a fix.

MIT license, from tristan-mcinnis/pptx-from-layouts-skill at commit 46e7c6638305.

Security

Scanned Oct 22, 2026 at commit 46e7c6638305, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.

NameScoreStarsContextUpdated
This onepptx-deck-qa tristan-mcinnis/pptx-from-layouts-skill · Subagent 52★ 37≈22 in chat2mo ago
pptx HKUDS/DeepTutor · Skill Same job: slides & presentations 90★ 42k≈20 always16d ago
deck-to-pptx EverMind-AI/Raven · Skill Same job: slides & presentations 74★ 5.5k≈153 always16d ago
deck-design-ppt appautomaton/presentation · Skill Same job: slides & presentations 56★ 63≈20 always2mo ago
qa-bach MaxMiksa/Autonomous-Company · Subagent Both about qa 69★ 3.1k≈17 in chat18d ago
fig-pptx Azhi-ss/academic-figure-skills · Skill Same job: slides & presentations 65★ 161≈13 always24d ago