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.
Stop presenting the working deck to executives — the two-deck split (answer-first exec cut vs.
Install Exec Vs Working Deck
$ npx skills add mohitagw15856/pm-claude-skills --skill exec-vs-working-deck -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exec-vs-working-deck --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/exec-vs-working-deck .claude/skills/exec-vs-working-deck && 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 "exec-vs-working-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exec-vs-working-deck into .claude/skills/exec-vs-working-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exec-vs-working-deck", 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/exec-vs-working-deckType 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 exec-vs-working-deck -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exec-vs-working-deck --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/exec-vs-working-deck .agents/skills/exec-vs-working-deck && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "exec-vs-working-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exec-vs-working-deck into .agents/skills/exec-vs-working-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exec-vs-working-deck", 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 exec-vs-working-deck -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exec-vs-working-deck --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/exec-vs-working-deck .cursor/skills/exec-vs-working-deck && 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 "exec-vs-working-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exec-vs-working-deck into .cursor/skills/exec-vs-working-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exec-vs-working-deck", 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/exec-vs-working-deck--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 exec-vs-working-deck -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exec-vs-working-deck --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/exec-vs-working-deck .gemini/skills/exec-vs-working-deck && 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 "exec-vs-working-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exec-vs-working-deck into .gemini/skills/exec-vs-working-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exec-vs-working-deck", 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 exec-vs-working-deckInstalls 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 exec-vs-working-deck -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/exec-vs-working-deck .github/skills/exec-vs-working-deck && 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 "exec-vs-working-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exec-vs-working-deck into .github/skills/exec-vs-working-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exec-vs-working-deck", 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 exec-vs-working-deck -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 exec-vs-working-deck --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/exec-vs-working-deck .opencode/skills/exec-vs-working-deck && 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 "exec-vs-working-deck" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exec-vs-working-deck into .opencode/skills/exec-vs-working-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exec-vs-working-deck", 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
exec-vs-working-deck- GitHub stars
- 1.4k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 716 words
- Files
- 1
- Skills in repo
- 1,322
- Repo updated
- First seen
- Licence
- MIT
At a glance
Stop presenting the working deck to executives — the two-deck split (answer-first exec cut vs.
- Works in 5 steps: Answer at slide 2: slide 1 orients (the… → Three evidence pieces, chosen not… → Methodology becomes one line plus a… → …
- Asked turn this analysis into an exec version
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Split Rules and Output Format, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Exec Vs Working Deck is an agent skill from mohitagw15856/pm-claude-skills. Stop presenting the working deck to executives — the two-deck split (answer-first exec cut vs. exploration-rich working deck), the compression rules from 40 slides to 8, and the appendix strategy that keeps the depth one click away. Use when asked turn this analysis into an exec version, my leadership readout went badly, how do I compress 40 slides to 10 minutes, or what do execs actually want in a deck. Produces the exec cut with the answer-first order, the compression map (what survived, where the rest went)…
Its SKILL.md is about 1.4k 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
- Asked turn this analysis into an exec version
- My leadership readout went badly
- How do I compress 40 slides to 10 minutes
- What do execs actually want in a deck
Example prompts
- “/exec-vs-working-deck”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Answer at slide 2: slide 1 orients (the question we set out to answer), slide 2 answers it, unhedged — everything after is evidence, risk…
- Three evidence pieces, chosen not accumulated: the working deck's twelve supporting analyses compress to the three that carry the most…
- Methodology becomes one line plus a pointer: "12 cohorts, 18 months, methodology in appendix A" — rigor gets asserted and…
- Risks and the ask close, always: the exec cut ends with the risks conceded (proposal-skeleton objections logic) and the specific ask…
- The appendix is a product, not a dump: ordered by question-likelihood (the hard questions' slides first), each appendix slide…
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
Exec Vs Working Deck loads about 1.4k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 716 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). 716 words, ~1,398 tokens.
Download SKILL.mdSave it as
.claude/skills/exec-vs-working-deck/SKILL.md (or your agent's skills folder).- name
- exec-vs-working-deck
- description
- Stop presenting the working deck to executives — the two-deck split (answer-first exec cut vs. exploration-rich working deck), the compression rules from 40 slides to 8, and the appendix strategy that keeps the depth one click away. Use when asked turn this analysis into an exec version, my leadership readout went badly, how do I compress 40 slides to 10 minutes, or what do execs actually want in a deck. Produces the exec cut with the answer-first order, the compression map (what survived, where the rest went), and the Q&A appendix plan.
Exec Vs Working Deck Skill
The working deck — forty slides of exploration, methodology, and dead ends — is a diary of the analysis. Presenting it to executives narrates the journey chronologically, landing the answer at slide 34 of a meeting that ended attention-wise at slide 6. The exec cut inverts the geometry: the answer first (slide 2 at the latest), the three pieces of evidence that carry it, the risks and the ask — 6–10 slides — with the working deck demoted to appendix, where it does its real executive job: existing, as the visible proof of rigor behind every Q&A answer ("slide 24 has that cohort — here").
What This Skill Produces
- The exec cut — answer-first, 6–10 slides, built from the working deck's strongest material
- The compression map — every working-deck section: promoted / compressed to a line / appendixed / cut
- The appendix strategy — the Q&A-ordered depth, indexed so retrieval is instant in the room
- The two-deck discipline — when each artifact is used, so the working deck stops leaking into exec rooms
Required Inputs
Ask for these if not provided:
- The working deck (or analysis) — the source material; the cut is extraction, not new writing
- The answer, committed: the exec cut requires the author to have a conclusion — "here's what we found, you decide" working decks first need the conclusion conversation (executive-summary BLUF discipline; no cut can rescue an uncommitted analysis)
- The executives' currencies — what this audience weighs (growth? risk? cost?) — the three surviving evidence pieces are chosen in their currency
- The likely hard questions — each one gets its appendix slide, pre-ordered by likelihood
Framework: The Split Rules
- Answer at slide 2: slide 1 orients (the question we set out to answer), slide 2 answers it, unhedged — everything after is evidence, risk, and the ask. The chronological reveal ("first we looked at…") is the working deck's structure leaking; executives fund conclusions, not journeys.
- Three evidence pieces, chosen not accumulated: the working deck's twelve supporting analyses compress to the three that carry the most weight in the audience's currency — each as one deck-outline-first claim-slide. The other nine live in the appendix, alive and retrievable, not deleted (slide-density-rules redistribution, applied at deck scale).
- Methodology becomes one line plus a pointer: "12 cohorts, 18 months, methodology in appendix A" — rigor gets asserted and evidenced-on-demand, not walked through. The exception: when the method IS the controversy (a contested model), it earns one slide, framed as the credibility answer.
- Risks and the ask close, always: the exec cut ends with the risks conceded (proposal-skeleton objections logic) and the specific ask — decision, resource, date. Working decks trail off into "next steps"; exec cuts land on a decision point.
- The appendix is a product, not a dump: ordered by question-likelihood (the hard questions' slides first), each appendix slide self-sufficient and findable in seconds ("slide 24" said confidently is worth two slides of preemptive defense). The in-room move — answer briefly, offer the depth — makes the appendix's existence do the persuading.
Show full SKILL.md (225 more words)Show less
Output Format
Exec Cut: [analysis] — [N] slides + appendix · audience currency: [their weights]
The Cut (slide order)
- The question · 2. The answer · 3–5. The three evidence claims · 6. Risks conceded · 7. The ask [Each slide as its headline claim]
The Compression Map
| Working-deck section | Fate | Where |
|---|---|---|
| [Promoted / one-line / appendix-# / cut] |
The Appendix Plan
[Q&A-ordered: likely question → its slide · the index card for in-room retrieval]
Quality Checks
- The answer lands by slide 2, unhedged
- Exactly three evidence pieces survived, chosen in the audience's currency
- Methodology compressed to assertion-plus-pointer (unless it's the controversy)
- The cut ends in risks and a specific ask
- The appendix is question-ordered and indexed for live retrieval
Anti-Patterns
- Do not present the diary — the journey structure is for the team that took it
- Do not hedge the answer to seem balanced — the risks slide is where balance lives; slide 2 is where the answer does
- Do not delete the depth — appendixed rigor answers Q&A; deleted rigor becomes "we'll get back to you"
- Do not walk through methodology uninvited — assert, evidence on demand
- Do not build the exec cut before committing to the answer — compression can't rescue an analysis that won't conclude
Example Trigger Phrases
- "Turn this analysis into an exec version."
- "My leadership readout went badly."
- "How do I compress 40 slides to 10 minutes?"
- "What do execs actually want in a deck?"
© 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/exec-vs-working-deck of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Exec Vs Working Deck 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 |
|---|---|---|---|---|---|---|
| Exec Vs Working Deck this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Image To Editable Pptningzimu/image-to-editable-ppt-skill | 2.8k | — | ~4.3k | Automated safety check: Pass | MIT | |
| Codex Slidesnexu-io/codex-slides | 924 | 1 repos | ~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 |
Similar skills
Codex Slides
nexu-io/codex-slides
Create, research, revise, restyle, present, inspect, and export Codex Slides slide decks from Codex, including scenario workflows, project Design Files, and always-on brand design systems.
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.
More from mohitagw15856/pm-claude-skills
All 1,322 skills in this repoExit 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.
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.
Offer Comparison
mohitagw15856/pm-claude-skills
Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed.
Refinance Breakeven
mohitagw15856/pm-claude-skills
Compute the month a refinance actually starts saving money — payment delta, breakeven month, and total interest on both paths including the term-reset trap.
Rent Vs Buy
mohitagw15856/pm-claude-skills
Model rent-vs-buy honestly — year-by-year net position for both paths including the assumption everyone drops (the renter invests the difference), with a breakeven horizon instead of a verdict.
Related
Categories
Questions about Exec Vs Working Deck
What does Exec Vs Working Deck do?
Stop presenting the working deck to executives — the two-deck split (answer-first exec cut vs. Exec Vs Working Deck is an agent skill from mohitagw15856/pm-claude-skills. Stop presenting the working deck to executives — the two-deck split (answer-first exec cut vs.
When should I use Exec Vs Working Deck?
Exec Vs Working Deck fits situations like: asked turn this analysis into an exec version; my leadership readout went badly; how do I compress 40 slides to 10 minutes; what do execs actually want in a deck.
How do I install Exec Vs Working Deck in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill exec-vs-working-deck -a claude-code`. Or copy the skill folder (skills/exec-vs-working-deck in mohitagw15856/pm-claude-skills) into .claude/skills/exec-vs-working-deck in your project. Claude Code loads it when a task matches its description.
How do I install Exec Vs Working Deck in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill exec-vs-working-deck -a codex`. Or copy the skill folder (skills/exec-vs-working-deck in mohitagw15856/pm-claude-skills) into .agents/skills/exec-vs-working-deck in your project. Codex loads it when a task matches its description.
Can I use Exec Vs Working Deck 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 exec-vs-working-deck -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/exec-vs-working-deck, .gemini/skills/exec-vs-working-deck, .github/skills/exec-vs-working-deck and .opencode/skills/exec-vs-working-deck in your project.
What does Exec Vs Working Deck need to run?
SKILL.md names no scripts, command-line tools or credentials: Exec Vs Working Deck is instructions for the agent only.
Does Exec Vs Working Deck 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 Exec Vs Working Deck 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 Exec Vs Working Deck use?
Exec Vs Working Deck 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 Exec Vs Working Deck use?
About 1.4k tokens (SKILL.md is roughly 5.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 Exec Vs Working Deck?
Skills that share tags, products or a category with Exec Vs Working Deck: Image To Editable Ppt (ningzimu/image-to-editable-ppt-skill, 2.8k stars), Codex Slides (nexu-io/codex-slides, 924 stars), Slides (fcakyon/claude-codex-settings, 1.2k stars) and Ppt Image First (NyxTides/ppt-image-first, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Exec Vs Working Deck?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,431 GitHub stars. The repository holds 1,322 skills in this directory. The repository was last updated on October 7, 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.