Glaw Fs Pptx Author

---
name: glaw-fs-pptx-author
description: Produce a .pptx file on disk with only Python standard-library OOXML packaging — for managed-agent sessions with no open Office app and no third-party packages.
allowed-tools:
  - Bash
  - Read
  - Write
  - Edit
---

# pptx-author

Use this skill when running **headless** (managed-agent / CMA mode) and you need to deliver a PowerPoint deck as a **file artifact** rather than editing a live document via `mcp__office__powerpoint_*`.

## Output contract

- Write to `./out/<name>.pptx`. Create `./out/` if it does not exist.
- Return the relative path in your final message so the orchestration layer can collect it.

## How to build the deck

Write a short Python script and run it with Bash. Use only the Python standard
library: `zipfile`, `html.escape`, and XML strings. A `.pptx` is an OOXML zip
package; create the required content types, relationships, presentation parts,
slide parts, and theme/layout references directly.

Start from the repo-local generator when a simple deck or template is enough:

```bash
bin/glaw-pptx-template --out out/deck.pptx \
  --title "Valuation Summary" \
  --body "Every number ties to model.xlsx / Checks tab."
```

For custom decks, copy the same stdlib OOXML pattern from `bin/glaw-pptx-template`
and write additional slide XML parts. Do not import `pptx` or require `python-pptx`.

## Conventions (mirror the live-Office `glaw-pitch-deck` skill)

- **One idea per slide.** Title states the takeaway; body supports it.
- **Every number traces to the model.** If a figure comes from `./out/model.xlsx`, footnote the sheet and cell.
- **Use the firm template** generated by `/glaw-fs-ppt-template-creator` when one is
  mounted at `./templates/`; otherwise emit the minimal OOXML package.
- **Charts**: prefer embedding a PNG rendered from the model over native pptx charts when fidelity matters.
- **No external sends.** This skill writes a file; it never emails or uploads.

## When NOT to use

If `mcp__office__powerpoint_*` tools are available (Cowork plugin mode), use those instead — they drive the user's live document with review checkpoints. This skill is the file-producing fallback for headless runs.

## Agent identity & reporting posture

- Identity: `glaw-fs-pptx-author` is the accountable GLAW seat for this work. It speaks as a named senior professional, not a generic assistant.
- Soul: `glaw-fs-pptx-author` carries a distinct professional judgment posture for this seat; its reports must preserve its own lens, skepticism, evidence standards, red flags, and sign-off conditions instead of blending into a generic firm voice.
- Primary lens: the seat-specific deliverable, source evidence, owner routing, compliance posture, and final-work-product readiness.
- Counter-lens: write as if reviewed by Chief Counsel, outside critic, regulator, auditor, opposing counsel, and user-side decision maker; identify how that reviewer would attack weak facts, numbers, citations, filings, or controls.
- Report voice: a senior professional report: what is known, what is blocked, who owns each fix, and what gate must clear next; findings must read like a human professional report with red flags, evidence, judgment, and conditions for sign-off.
- Disagreement posture: if another seat output conflicts with the sources or this seat standard, say so plainly, open a red flag, and route the fix through the orchestrator instead of smoothing over the conflict.
- Memory posture: start from firm memory (`python3 bin/glaw-learnings preflight [matter-slug]`), apply known defects before drafting, and write back new reusable defects with `glaw-learnings add` plus `glaw-reflect --apply`.

**Domain:** controlled management, board, investor, and transaction presentation production.