Deck Refresh
AnthropicOfficialPublished by Anthropic
- Skill
- Content generator
- Documents and content
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Deck Refresh provides a systematic, four-phase procedure for updating figures in presentation files, such as quarterly earnings or market data. It emphasizes precision by identifying all instances of a value—including variations in scale, units, and embedded text—and requires user approval before applying changes. The skill is designed to act as a surgical tool that modifies data without altering the deck's original design, formatting, or narrative structure.
What it does
- Maps new data points to existing values across slides, tables, and charts.
- Identifies all variations of a number, including different units, scales, and formatting styles.
- Flags potentially stale derived metrics, such as growth rates or percentages, for user review.
- Executes updates while maintaining original font, color, and styling attributes.
- Updates underlying chart data to ensure visual representations remain accurate.
- Provides a post-execution report detailing all changes made and items left unchanged.
When to use it
- When performing quarterly refreshes or earnings updates on an existing presentation.
- When you need to roll forward financial comps or rebase market data.
- When you must swap specific figures across a deck without rebuilding slides.
- When you need to ensure consistency across text, tables, and charts for a single data point.
Advantages
- Prevents formatting errors by preserving original design elements.
- Reduces the risk of missed updates by locating numbers in footnotes, labels, and speaker notes.
- Provides a safety gate by requiring user approval of a change plan before execution.
- Ensures data integrity by updating underlying chart data rather than just labels.
Usage examples
- “Update the deck with Q4 numbers: revenue is now $512M and EBITDA is $135M.”
- The agent will scan the deck for all instances of the old revenue and EBITDA figures, present a plan for approval, and update the values while preserving formatting.
- “Refresh the comps in this presentation using the provided Excel file.”
- The agent will read the Excel file, map the new values to the existing deck data, flag any derived metrics that might be affected, and update the deck upon approval.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/anthropics/deck-refresh/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip deck-refresh.zip -d .agents/skills
Documentation by Anthropic
Deck Refresh
Update numbers across the deck. The deck is the source of truth for formatting; you're only changing values.
Environment check
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:
Add-in — the deck is open live; edit text runs, table cells, and chart data directly.
Chat — the deck is an uploaded file; edit it by regenerating the affected slides with the new values and writing the result back.
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.
Phase 1 — Get the data
Use ask_user_question to find out how the new numbers are arriving:
Pasted mapping — user types or pastes "revenue $485M → $512M, EBITDA $120M → $135M." The clearest case.
Uploaded Excel — old/new columns, or a fresh output sheet the user wants pulled from. Read it, confirm which column is which before you trust it.
Just the new values — "Q4 revenue was $512M, margins were 22%." You figure out what each one replaces. Workable, but confirm the mapping before you touch anything — a "$512M" that you map to revenue but the user meant for gross profit is a quiet disaster.
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.
Phase 2 — Read everything, find everything
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:
Text boxes (obvious)
Table cells
Chart data labels and axis labels
Chart source data — the numbers driving the bars, not just the labels on them
Footnotes, source lines, small print
Speaker notes, if the user cares about those
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.
Phase 3 — Present the plan, get approval
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.
Phase 4 — Execute, preserve, report
For each change, make the smallest edit that accomplishes it. How that happens depends on your environment:
Add-in — edit the specific run, cell, or chart series directly in the live deck.
Chat — regenerate the affected slide with the new value in place, preserving every other element exactly as it was, and write it back to the file.
Either way, the standard is the same:
Text in a shape — change the value, leave font/size/color/bold state exactly as they were. If
$485Mis 14pt navy bold inside a sentence,$512Mis 14pt navy bold inside the same sentence.Table cell — change the cell, leave the table alone.
Chart data — update the underlying series values so the bars/lines actually move. Editing just the label without the data leaves a chart that lies.
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.
What you're not doing
Not rebuilding slides — if a slide's narrative no longer makes sense with the new numbers ("margins compressed" but margins went up), flag it, don't rewrite it.
Not recalculating unless asked — derived numbers are the user's call. Your Phase 1 question covers this.
Not touching formatting — if the deck uses
$MMand the user's mapping says$M, match the deck, not the mapping. Values change; style stays.
Files
- ATTRIBUTION.mdAdded by AutoGineer916 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md6.0 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/financial-services · plugins/agent-plugins/pitch-agent/skills/deck-refresh · commit 6056506
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- anthropics/financial-services
AutoGineer is not affiliated with or endorsed by Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download deck-refresh.zip