Update numbers across the deck. The deck is the source of truth for formatting; you're only changing values.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondeck-refreshExecute the skills CLI command in your project's root directory to begin installation:
Fetches deck-refresh from anthropics/financial-services-plugins and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate deck-refresh. Access via /deck-refresh in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
7.3K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
7.3K
stars
Update numbers across the deck. The deck is the source of truth for formatting; you're only changing values.
This skill works in both the PowerPoint add-in and chat. Identify which you're in before starting — the edit mechanism differs, the intent doesn't:
Either way: smallest possible change, existing formatting stays intact.
This is a four-phase process and the third phase is an approval gate. Don't edit until the user has seen the plan.
Use ask_user_question to find out how the new numbers are arriving:
Also ask about derived numbers: if revenue moves, does the user want growth rates and share percentages recalculated, or left alone? Most decks have "+15% YoY" baked in somewhere that's now stale. Whether to touch those is a judgment call the user should make, not you.
Read every slide. For each old value, find every instance — including the ones that don't look the same:
| Variant | Example |
|---|---|
| Scale | $485M, $0.485B, $485,000,000 |
| Precision | $485M, $485.0M, ~$485M |
| Unit style | $485M, $485MM, $485 million, 485M |
| Embedded | "revenue grew to $485M", "a $485M business", axis labels |
A deck that says $485M on slide 3, 485 on slide 8's chart axis, and $485.0 million in a footnote on slide 15 has three instances of the same number. Find-replace misses two of them. You shouldn't.
Where numbers hide:
Build a list: for each old value, every location it appears, the exact text it appears as, and what it'll become. This list is the plan.
This is a destructive operation on a deck someone spent time on. Show the full change list before editing a single thing. Format it so it's scannable:
$485M → $512M (Revenue)
Slide 3 — Title box: "Revenue grew to $485M"
Slide 8 — Chart axis label: "485"
Slide 15 — Footnote: "$485.0 million in FY24 revenue"
$120M → $135M (Adj. EBITDA)
Slide 3 — Table cell
Slide 11 — Body text: "$120M of Adj. EBITDA"
FLAGGED — possibly derived, not in your mapping:
Slide 3 — "+15% YoY" (growth rate — stale if base year didn't change?)
Slide 7 — "12% market share" (was this computed from $485M / market size?)
The flagged section matters. You're not just executing a find-replace — you're catching the second-order effects the user would've missed at 11pm. If the mapping says $485M → $512M and slide 3 also has +15% YoY right next to it, that growth rate is probably wrong now. Flag it; don't silently fix it, don't silently leave it.
Use ask_user_question for the approval: proceed as shown, proceed but skip the flagged items, or let them revise the mapping first.
For each change, make the smallest edit that accomplishes it. How that happens depends on your environment:
Either way, the standard is the same:
$485M is 14pt navy bold inside a sentence, $512M is 14pt navy bold inside the same sentence.Don't reformat anything you didn't need to touch. The deck's existing style is correct by definition; you're a surgeon, not a renovator.
After the last edit, report what actually happened:
Updated 11 values across 8 slides.
Changed:
[the list from Phase 3, now past-tense]
Still flagged — did NOT change:
Slide 3 — "+15% YoY" (derived; confirm separately)
Slide 7 — "12% market share"
Run standard visual verification checks on every edited slide. A number that got longer ($485M → $1,205M) might now overflow its text box or push a table column width. Catch it before the user does.
$MM and the user's mapping says $M, match the deck, not the mapping. Values change; style stays.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added deck-refresh from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for deck-refresh matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in deck-refresh — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
deck-refresh reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for deck-refresh matched our evaluation — installs cleanly and behaves as described in the markdown.
We added deck-refresh from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
deck-refresh has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend deck-refresh for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
deck-refresh fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
deck-refresh is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 26