Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问许可证需确认审计通过

deck-refresh甲板刷新

Agent Skill

deck-refresh 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

8,387

周安装

353

GitHub Stars

7,821

下载量

2,937
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:deck-refresh(甲板刷新)
来源仓库:https://github.com/anthropics/financial-services-plugins
仓库路径:skills/deck-refresh
安装命令:
npx skills add https://github.com/anthropics/financial-services-plugins --skill deck-refresh
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/anthropics/financial-services-plugins --skill deck-refresh

简介

更新演示文稿中的数值数据,保持格式不变仅替换值。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

  • 区分PowerPoint插件与聊天模式两种编辑机制。
  • 最小化变更范围,确保原有排版与图表结构不受影响。
  • 适用于定期同步市场数据、财务指标等动态内容场景。
  • deck-refresh 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

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:

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.

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

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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.59%
按下载量换算1,045

Claude

31.41%
按下载量换算923

Cursor

17.66%
按下载量换算519

Gemini CLI

8.69%
按下载量换算255

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills