Skill Tracer
Skills › Financial Services › deck-refresh

deck-refresh

skill · 111 lines · Apache-2.0 · plugins/vertical-plugins/financial-analysis/skills/deck-refresh/SKILL.md

The facts

Its description

Updates a presentation with new numbers — quarterly refreshes, earnings updates, comp rolls, rebased market data. Use whenever the user asks to "update the deck with Q4 numbers", "refresh the comps", "roll this forward", "swap in the new earnings", "change all the $485M to $512M", or any request to swap figures across an existing deck without rebuilding it.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent picks this skill when someone asks to swap new figures into a presentation that already exists — a quarterly refresh, an earnings update, a comp roll — rather than to build a deck from scratch. The request is about changing values across an existing deck while leaving its formatting alone.

Things a person might say (the model's guesses)

  • “Update the deck with the Q4 numbers.”
  • “Can you change all the $485M to $512M in the pitch deck?”
  • “Refresh the comps in this deck with the latest market data.”

A model's summary of when it is used.

A model's reading

What it leads to

Other skills this one hands off to, calls, requires or offers instead, as a model read them.

A model's reading

What leads to it

Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.

A model's reading

Licence

Apache-2.0, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: deck-refresh
3description: Updates a presentation with new numbers — quarterly refreshes, earnings updates, comp rolls, rebased market data. Use whenever the user asks to "update the deck with Q4 numbers", "refresh the comps", "roll this forward", "swap in the new earnings", "change all the $485M to $512M", or any request to swap figures across an existing deck without rebuilding it.
4---
5
6# Deck Refresh
7
8Update numbers across the deck. The deck is the source of truth for formatting; you're only changing values.
9

Deck Refresh

Update numbers across the deck. The deck is the source of truth for formatting; you're only changing values.

Raw lines 1 to 9
10## Environment check
12This 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:
14- **Add-in** — the deck is open live; edit text runs, table cells, and chart data directly.
15- **Chat** — the deck is an uploaded file; edit it by regenerating the affected slides with the new values and writing the result back.
17Either way: smallest possible change, existing formatting stays intact.
19This is a four-phase process and the third phase is an approval gate. Don't edit until the user has seen the plan.

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.

Raw lines 10 to 20
21## Phase 1 — Get the data
23Use `ask_user_question` to find out how the new numbers are arriving:
25- **Pasted mapping** — user types or pastes "revenue $485M → $512M, EBITDA $120M → $135M." The clearest case.
26- **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.
27- **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.
29Also 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 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.

Raw lines 21 to 30
31## Phase 2 — Read everything, find everything
33Read every slide. For each old value, find every instance — including the ones that don't look the same:
35| Variant | Example |
36|---|---|
37| Scale | `$485M`, `$0.485B`, `$485,000,000` |
38| Precision | `$485M`, `$485.0M`, `~$485M` |
39| Unit style | `$485M`, `$485MM`, `$485 million`, `485M` |
40| Embedded | "revenue grew to $485M", "a $485M business", axis labels |
42A 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.
44**Where numbers hide:**
45- Text boxes (obvious)
46- Table cells
47- Chart data labels and axis labels
48- Chart source data — the numbers driving the bars, not just the labels on them
49- Footnotes, source lines, small print
50- Speaker notes, if the user cares about those
52Build 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 2 — Read everything, find everything

Read every slide. For each old value, find every instance — including the ones that don't look the same:

VariantExample
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.

Raw lines 31 to 53
54## Phase 3 — Present the plan, get approval
56**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:
58```
59$485M → $512M (Revenue)
60 Slide 3 — Title box: "Revenue grew to $485M"
61 Slide 8 — Chart axis label: "485"
62 Slide 15 — Footnote: "$485.0 million in FY24 revenue"
64$120M → $135M (Adj. EBITDA)
65 Slide 3 — Table cell
66 Slide 11 — Body text: "$120M of Adj. EBITDA"
68FLAGGED — possibly derived, not in your mapping:
69 Slide 3 — "+15% YoY" (growth rate — stale if base year didn't change?)
70 Slide 7 — "12% market share" (was this computed from $485M / market size?)
71```
73The 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.
75Use `ask_user_question` for the approval: proceed as shown, proceed but skip the flagged items, or let them revise the mapping first.

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.

Raw lines 54 to 76
77## Phase 4 — Execute, preserve, report
79For each change, make the smallest edit that accomplishes it. How that happens depends on your environment:
81- **Add-in** — edit the specific run, cell, or chart series directly in the live deck.
82- **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.
84Either way, the standard is the same:
86- **Text in a shape** — change the value, leave font/size/color/bold state exactly as they were. If `$485M` is 14pt navy bold inside a sentence, `$512M` is 14pt navy bold inside the same sentence.
87- **Table cell** — change the cell, leave the table alone.
88- **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.
90Don'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.
92After the last edit, report what actually happened:
94```
95Updated 11 values across 8 slides.
97Changed:
98 [the list from Phase 3, now past-tense]
100Still flagged — did NOT change:
101 Slide 3 — "+15% YoY" (derived; confirm separately)
102 Slide 7 — "12% market share"
103```
105Run 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.

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 $485M is 14pt navy bold inside a sentence, $512M is 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.

Raw lines 77 to 106
Names a skill ib-check-deck :105
107## What you're not doing
109- **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.
110- **Not recalculating unless asked** — derived numbers are the user's call. Your Phase 1 question covers this.
111- **Not touching formatting** — if the deck uses `$MM` and the user's mapping says `$M`, match the deck, not the mapping. Values change; style stays.

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 $MM and the user's mapping says $M, match the deck, not the mapping. Values change; style stays.
Raw lines 107 to 111

From anthropics/financial-services at 6056506, 2026-10-28. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.