Msft deck

Portable Agent Skills for non-RAPP systems and launchpads for single-file RAPP agents

Install

npx -y skills add kody-w/rapp-skills --skill msft-deck

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Build, restyle, or revise a PowerPoint deck in Kody's Microsoft styling, self-review every slide visually, and only hand it over verified and popped open. Use whenever the user asks for a deck, slides, a pptx, a one-pager deck, to "restyle" a deck, to make slides "look like the STYLED one" / "not look vibe coded", or to turn notes/a transcript/an md into a presentation.

SKILL.md

15.1 KB, ~8.8k tokens by cl100k_base, as published. Nobody here has run it

msft-deck

Produce a .pptx that survives Kody's review on the first pass. The historical failure modes this skill exists to kill, in order of how often they burned turns: handing over a deck with a broken/ugly slide he had to screenshot back, overwriting slides he authored, walls of text, delivering HTML when he wanted pptx, and asking him to open/check things you can check yourself.

Mode detection (do this first)

REVISE — he gave you a deck he (or a customer) touched: make ONLY the changes he asked for, in place, with python-pptx. Never regenerate, reorder, or "improve" other slides. His words: "keep the slides I had... THATS IT". When in doubt whether a slide is his, it's his.
RESTYLE — he gave a deck and wants it in the house style: keep content and slide order exactly; change fonts, colors, spacing, layout polish only.
NEW — build from notes/transcript/md/conversation. Distill the BUSINESS USE CASE, not the conversation that produced it. A transcript is raw ore, never an outline.

Style contract (extracted from the canonical STYLED reference deck)

16:9 (13.33in x 7.5in). Build with python-pptx (installed, v1.0.2).
Fonts: Segoe UI body, Segoe UI Semibold headings/emphasis, Consolas for code. Never Calibri, never the template default.
Palette: text #1B1A19 (near-black) and #3B3A39; secondary text #605E5C; accent/link #0078D4 (Microsoft blue); positive #107C10; warning/highlight #D83B01; white #FFFFFF on dark fills. Nothing outside this palette without being asked.
Type scale: titles ~40pt, section heads ~19pt, body 13–14pt, captions 10.5–12pt.
Layout: generous whitespace, left-aligned text, consistent margins across ALL slides (misaligned elements = "looks vibe coded"). One visual anchor per slide max.

Content rules (KISS — he has said this five times in a row)

Default ≤ 10 slides. One idea per slide. ≤ 5 bullets per slide, ≤ 12 words per bullet. If a slide needs a paragraph, it's two slides or a talk track.
Customer-facing decks: strip PII — no customer employee names, emails, or internal identifiers unless he explicitly says otherwise. Generalize ("a national retailer") if the customer name itself is sensitive.
Output is a real .pptx on disk. HTML decks only when he asks for HTML. Never emojis.

Self-review gate (non-negotiable — this is the whole point)

Before telling him anything is done:

Render: soffice --headless --convert-to pdf --outdir <dir> <deck>.pptx
Read the PDF and look at every page. Check each slide for: text overflowing or clipped by shapes, overlapping elements, off-palette colors, wrong/default fonts, ragged alignment vs neighboring slides, orphaned placeholder text ("Click to add..."), unreadable contrast.
Fix everything you find, re-render, re-inspect. Loop until a full pass is clean. Do not ask him to be the QA loop — no screenshots from him, ever.
In REVISE mode, additionally diff-check: confirm untouched slides are byte-identical in content (same text runs) to what he gave you.

Handoff

Save next to the source (or ~/Desktop for ad-hoc asks), versioned Name_v2.pptx style if a prior version exists — never overwrite the file he gave you.
Pop it open: open -a "Microsoft PowerPoint" <deck>.pptx
Report: file path, slide count, one line per change made (REVISE/RESTYLE) or the slide-by-slide outline (NEW), and confirmation the visual pass was clean.

Parameters

The typed contract this capability answers to (JSON Schema — the deterministic layer):

{
  "properties": {
    "deck": {
      "description": "Derived from `<deck>` used in the documented command at line 29.",
      "type": "string"
    }
  },
  "required": [],
  "type": "object"
}

Deterministic steps

Lifted verbatim from the procedure above by toaster.py toast. Run them in order, substituting the typed parameters; do not paraphrase:

open -a "Microsoft PowerPoint" <deck>.pptx

Gives 0 of the 12 instructions most pdf office docs skills give in ~8.8k tokens

Counted across 635 of the 690 authors here whose files we hold, read 2026-08-06

extract text using pdfplumberin 92 of 635, across 25 files
create PDFs using reportlabin 83 of 635, across 16 files
read FORMS.md to fill out PDF formsin 80 of 635, across 13 files
OCR scanned PDFs using pytesseractin 77 of 635, across 10 files
merge or split PDFs using qpdfin 70 of 635, across 3 files
use Excel formulas instead of hardcoded calculated valuesin 68 of 635, across 12 files
unpack edit xml and repack existing documentsin 63 of 635, across 8 files
document sources for hardcoded valuesin 61 of 635, across 9 files
write minimal python code without unnecessary commentsin 59 of 635, across 7 files
run the recalculation script after adding or modifying formulasin 58 of 635, across 6 files
fix all identified formula errors and recalculatein 58 of 635, across 6 files
format years as text stringsin 57 of 635, across 5 files

Said here and by no other author read

use python-pptx to build decks
use segoe ui fonts and the specified palette
limit slides to ten or fewer
strip personally identifiable information
render the pptx to pdf
loop fixes until visual pass is clean

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.