Image To Editable Ppt
ningzimu/image-to-editable-ppt-skill
Rebuild slide images, scanned or image-based PPT/PPTX files, and PDF decks into object-level editable PowerPoint (.pptx), preserving speaker notes when supplied.
Autopsy a slide deck from photos or screenshots of its slides — the narrative arc, the numbers, and what each slide is hiding.
Install Deck Autopsy
$ npx skills add mohitagw15856/pm-claude-skills --skill deck-autopsy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills deck-autopsy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/deck-autopsy .claude/skills/deck-autopsy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deck-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deck-autopsy into .claude/skills/deck-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deck-autopsy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deck-autopsyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill deck-autopsy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills deck-autopsy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/deck-autopsy .agents/skills/deck-autopsy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deck-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deck-autopsy into .agents/skills/deck-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deck-autopsy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill deck-autopsy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills deck-autopsy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/deck-autopsy .cursor/skills/deck-autopsy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deck-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deck-autopsy into .cursor/skills/deck-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deck-autopsy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/deck-autopsy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill deck-autopsy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills deck-autopsy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/deck-autopsy .gemini/skills/deck-autopsy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deck-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deck-autopsy into .gemini/skills/deck-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deck-autopsy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills deck-autopsyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill deck-autopsy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/deck-autopsy .github/skills/deck-autopsy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deck-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deck-autopsy into .github/skills/deck-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deck-autopsy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill deck-autopsy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills deck-autopsy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/deck-autopsy .opencode/skills/deck-autopsy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deck-autopsy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/deck-autopsy into .opencode/skills/deck-autopsy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deck-autopsy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
deck-autopsy- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 593 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Autopsy a slide deck from photos or screenshots of its slides — the narrative arc, the numbers, and what each slide is hiding.
- Works in 6 steps: Read each slide twice. Once for the… → Read the design as rhetoric. Truncated… → Reconstruct the chain. The deck's… → …
- Given slide images (a competitors pitch
- SKILL.md covers What This Skill Produces, Required Inputs, Autopsy Method and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Deck Autopsy is an agent skill from mohitagw15856/pm-claude-skills. Autopsy a slide deck from photos or screenshots of its slides — the narrative arc, the numbers, and what each slide is hiding. Use when given slide images (a competitor's pitch, a conference talk, your own deck before a big meeting) and asked what the deck argues, whether it holds up, or how to counter or improve it. Produces a slide-by-slide read, the reconstructed argument chain, weak links, and the questions the deck is engineered to avoid. Requires image input.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering Slides and decks. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Given slide images (a competitors pitch
- A conference talk
- Your own deck before a big meeting) and asked what the deck argues
- Whether it holds up
Example prompts
- “/deck-autopsy”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Read each slide twice. Once for the claim (usually the headline), once for the support (the chart, the numbers, the logos). A slide whose…
- Read the design as rhetoric. Truncated y-axes, cherry-picked date ranges, percentages without denominators, log scales unannounced…
- Reconstruct the chain. The deck's argument as numbered premises leading to its ask. Every deck has one; most hide a step. The hidden step…
- Cross-examine the numbers. Do the figures agree across slides (TAM vs revenue math, growth rate vs the chart, headcount vs burn)?…
- List the avoided questions. Given the claims made, what would a sceptic ask next that no slide answers? Absence is evidence of the sore…
- Anchor everything. Every finding cites its slide number. Unreadable content is flagged, never guessed.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Deck Autopsy loads about 1.1k tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 593 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 593 words, ~1,145 tokens.
Download SKILL.mdSave it as
.claude/skills/deck-autopsy/SKILL.md (or your agent's skills folder).- name
- deck-autopsy
- description
- Autopsy a slide deck from photos or screenshots of its slides — the narrative arc, the numbers, and what each slide is hiding. Use when given slide images (a competitor's pitch, a conference talk, your own deck before a big meeting) and asked what the deck argues, whether it holds up, or how to counter or improve it. Produces a slide-by-slide read, the reconstructed argument chain, weak links, and the questions the deck is engineered to avoid. Requires image input.
Deck Autopsy Skill
A deck is an argument wearing design. This skill reads slide images the way a sceptical partner does — reconstructing the claim chain, checking the numbers against each other across slides, and naming the questions the deck is built to keep the room from asking.
What This Skill Produces
- A slide-by-slide read: each slide's claim, its evidence, and what the design emphasises or buries
- The reconstructed argument chain — the deck's whole case as explicit premises → conclusion, with the weak links marked
- A cross-slide consistency check on the numbers
- The avoided questions — what a hostile reader asks that the deck never answers, and (if it's your deck) how to fix that before they do
Required Inputs
- The slide images, in order if possible. If none attached, ask — this skill autopsies real slides, not deck ideas.
- Whose deck and why (ask if missing): analysing a competitor/pitch, or hardening your own before the meeting — the output's stance flips accordingly.
Autopsy Method
- Read each slide twice. Once for the claim (usually the headline), once for the support (the chart, the numbers, the logos). A slide whose headline isn't proven by its own body gets flagged on the spot.
- Read the design as rhetoric. Truncated y-axes, cherry-picked date ranges, percentages without denominators, log scales unannounced, "representative" logos — chart crimes are claims about weakness. Note them per slide.
- Reconstruct the chain. The deck's argument as numbered premises leading to its ask. Every deck has one; most hide a step. The hidden step is the weakest link.
- Cross-examine the numbers. Do the figures agree across slides (TAM vs revenue math, growth rate vs the chart, headcount vs burn)? Cross-slide inconsistency is the highest-value finding an autopsy produces.
- List the avoided questions. Given the claims made, what would a sceptic ask next that no slide answers? Absence is evidence of the sore spot.
- Anchor everything. Every finding cites its slide number. Unreadable content is flagged, never guessed.
Output Format
Show full SKILL.md (264 more words)Show less
Deck autopsy: [deck] — [n] slides examined
The deck's argument, reconstructed:
- [premise — slide #]
- [premise — slide #] ∴ [the ask/conclusion — slide #] Weakest link: [which step, why]
Slide-by-slide: [#n] — Claims: [headline]. Support: [what's actually shown]. Design notes: [emphasis/burial/chart crimes]. Verdict: holds / overreaches / unproven.
Numbers cross-check:
| Figure | Slide(s) | Consistent? | Note |
|---|
Questions this deck is built to avoid:
- [question] — [what triggers it, which slide dances around it]
[If it's your deck] Hardening list: [the 3-5 fixes, in order of how likely each hole is to be found in the room]
Quality Checks
- Every finding cites a slide number; illegible content is flagged, not guessed
- Each slide's headline was checked against its own body, not just read
- Chart integrity was examined (axes, ranges, denominators), not just chart content
- Numbers were cross-checked between slides, not only within them
- The avoided-questions list follows from the deck's own claims, not generic due-diligence boilerplate
Anti-Patterns
- Do not autopsy from a deck's reputation or your memory of the company — only from the slides provided
- Do not proceed without slide images — for text notes about a future deck, use board-deck-narrative or investor-pitch-deck instead
- Do not treat beautiful design as evidence of a strong argument — the correlation runs the other way often enough
- Do not list ten nitpicks and skip the structural weakness — one broken chain link outweighs every font choice
- Do not soften findings on your own deck — the room won't
Example Trigger Phrases
- "What is this deck really arguing?"
- "Pick apart this competitor's pitch deck."
- "Here are photos of their slides: what are they hiding?"
- "Does my deck hold up before the big meeting?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/deck-autopsy of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Deck Autopsy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deck Autopsy this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Image To Editable Pptningzimu/image-to-editable-ppt-skill | 2.9k | — | ~4.3k | Automated safety check: Pass | MIT | |
| Slidesfcakyon/claude-codex-settings | 1.2k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Ppt Image FirstNyxTides/ppt-image-first | 1.2k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Vibe to Agentic Engineering Frameworkshanraisshan/claude-code-best-practice | 67k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Gpt Image2 PptJuneYaooo/gpt-image2-ppt-skills | 1.3k | — | ~8.9k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Slides
fcakyon/claude-codex-settings
Create and edit presentation slide decks (.pptx) with PptxGenJS, bundled layout helpers, and render/validation utilities.
Ppt Image First
NyxTides/ppt-image-first
Build presentation plans for PPT / slides / decks through a conversation-first workflow, then propose multiple visual directions with preview images before writing deck specs.
Vibe to Agentic Engineering Framework
shanraisshan/claude-code-best-practice
Explains the conceptual model behind a presentation on moving from unstructured vibe coding to fully configured agentic engineering, including its 4-level scoring system and slide conventions.
Gpt Image2 Ppt
JuneYaooo/gpt-image2-ppt-skills
Generate visually striking PPT slides via OpenAI's gpt-image-2 -- use any style in styles/<collection/STYLEID.md or mimic a user-supplied .pptx template; outputs high-res slide PNGs and a 16:9 .pptx.
Compiledeck
scunning1975/MixtapeTools
Create and compile beautiful Beamer presentations following the Rhetoric of Decks philosophy.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Deck Autopsy
What does Deck Autopsy do?
Autopsy a slide deck from photos or screenshots of its slides — the narrative arc, the numbers, and what each slide is hiding. Deck Autopsy is an agent skill from mohitagw15856/pm-claude-skills. Autopsy a slide deck from photos or screenshots of its slides — the narrative arc, the numbers, and what each slide is hiding.
When should I use Deck Autopsy?
Deck Autopsy fits situations like: given slide images (a competitors pitch; A conference talk; your own deck before a big meeting) and asked what the deck argues; whether it holds up.
How do I install Deck Autopsy in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill deck-autopsy -a claude-code`. Or copy the skill folder (skills/deck-autopsy in mohitagw15856/pm-claude-skills) into .claude/skills/deck-autopsy in your project. Claude Code loads it when a task matches its description.
How do I install Deck Autopsy in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill deck-autopsy -a codex`. Or copy the skill folder (skills/deck-autopsy in mohitagw15856/pm-claude-skills) into .agents/skills/deck-autopsy in your project. Codex loads it when a task matches its description.
Can I use Deck Autopsy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill deck-autopsy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deck-autopsy, .gemini/skills/deck-autopsy, .github/skills/deck-autopsy and .opencode/skills/deck-autopsy in your project.
What does Deck Autopsy need to run?
SKILL.md names no scripts, command-line tools or credentials: Deck Autopsy is instructions for the agent only.
Does Deck Autopsy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Deck Autopsy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Deck Autopsy use?
Deck Autopsy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Deck Autopsy use?
About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Deck Autopsy?
Skills that share tags, products or a category with Deck Autopsy: Image To Editable Ppt (ningzimu/image-to-editable-ppt-skill, 2.9k stars), Slides (fcakyon/claude-codex-settings, 1.2k stars), Ppt Image First (NyxTides/ppt-image-first, 1.2k stars) and Vibe to Agentic Engineering Framework (shanraisshan/claude-code-best-practice, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deck Autopsy?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.