Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add vivy-yi/finance-skills --skill board-deck-preparationgit clone --depth 1 https://github.com/vivy-yi/finance-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/vivy-yi/finance-skills/board-deck-preparation)<a href="https://agentmods.dev/skills/vivy-yi/finance-skills/board-deck-preparation"><img src="https://agentmods.dev/badge/skills/vivy-yi/finance-skills/board-deck-preparation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vivy-yi/finance-skills/board-deck-preparation"><img src="https://agentmods.dev/badge/skills/vivy-yi/finance-skills/board-deck-preparation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00097 | $0.02417 |
| Opus 5.5 | $0.00039 | $0.00967 |
| Sonnet 5.5 | $0.00019 | $0.00483 |
| Haiku 4.5 | $0.00010 | $0.00242 |
Grade A, and why
board-deck-preparation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
加载上下文
首次使用时: 读取 ../../CLAUDE.md 获取场景级配置(Board 风格规范/披露标准/数据保密要求)。
/board-deck-preparation — Board Deck 编制
Examples
→ 示例:用户说"下周三董事会,需要准备 Q2 的 Board Deck,帮我看看框架有没有问题",系统应调用本技能,按董事会模板生成 Deck 框架和内容要点。
→ 示例:用户说"Board Deck 里需要加一页 ESG 进展,评级刚提升了",系统应调用本技能,补充 ESG 进展页面。
→ 示例:用户说"这次 Board Deck 要特别说明一下收购标的的整合进展",系统应调用本技能,生成整合进展专项页面。
第一步:确认会议类型和内容框架
会议类型对应的标准内容:
□ 董事会(Board Meeting):
→ 执行摘要(1 页)
→ 财务业绩(2-3 页):收入/利润/现金流/关键财务比率
→ 战略进展(2-3 页):战略目标达成/市场变化/竞争态势
→ 重大事项(1-2 页):M&A/融资/组织调整/诉讼
→ 风险分析(1 页):主要风险及应对
→ 下阶段计划(1 页):重点工作和里程碑
□ 审计委员会(Audit Committee):
→ 审计发现跟踪(1-2 页)
→ 内控状态(1-2 页):SOX 合规/缺陷整改
→ 财务报告质量(1 页):关键会计判断
→ 合规状态(1 页):监管合规
□ 战略委员会(Strategy Committee):
→ 战略执行进度(2-3 页)
→ 市场与竞争分析(1-2 页)
→ 战略调整建议(1-2 页)
→ 新战略规划(如适用)(3-5 页)
补充内容(如有特殊事项):
□ 须单独披露的重大事项:[列表]
□ 保密信息处理:[脱敏/删除/单独附件]
第二步:收集和核实数据
数据提取:
□ 财务数据(从 [BI/ERP/财务系统]):
→ 期间:[YYYY-MM]
→ 收入:[X] 亿 — YoY [±X]%
→ EBITDA:[X] 亿 — YoY [±X]%
→ 净利润:[X] 亿 — YoY [±X]%
→ 经营现金流:[X] 亿
→ 关键比率:毛利率 [X]%、净利率 [X]%、ROE [X]%
□ 业务数据(从 [CRM/运营系统]):
→ 客户数量:[X] — QoQ [±X]%
→ 订单量:[X] — QoQ [±X]%
→ 重点项目进度:[X] 项 — 其中里程碑达成 [X] 项
□ 数据来源确认:
→ 财务数据:[✅ 已从审计口径确认 / ⚠️ 待确认]
→ 业务数据:[✅ 已核实 / ⚠️ 待核实]
→ 数据截止时间:[YYYY-MM-DD HH:MM]
数据一致性检查:
□ Deck 数据 vs 审计数据:[✅ 一致 / ⚠️ 差异 [X],原因:[描述]]
□ 同比/环比数据计算口径:[✅ 一致 / ⚠️ 口径差异]
□ 四舍五入差异:[✅ 在合理范围内 / ⚠️ 需调整]
第三步:设计 Deck 结构
页面结构(参考,可按实际情况调整):
总页数:[X] 页
1. 执行摘要(1 页)
→ 核心亮点 [3-5 条,每条一句话]
→ 本期 vs 上期 vs 全年目标
→ 风险预警(如有)
2. 财务业绩(2-3 页)
→ 收入/利润/现金流趋势图(3 年)
→ 部门/业务线贡献分解
→ 关键财务比率
3. 战略进展(2-3 页)
→ 战略目标达成追踪
→ 市场与竞争态势变化
→ 重点战略项目进度
4. 重大事项(1-2 页)
→ M&A/融资进展
→ 组织调整
→ 重大诉讼/监管事项
5. 风险分析(1 页)
→ Top 3 风险及应对
→ 风险趋势变化
6. 下阶段计划(1 页)
→ 重点工作计划
→ 下次会议前里程碑
Board 风格规范:
□ 配色:[深蓝/企业蓝] — 与公司品牌一致
□ 字体:[无衬线字体,如 Helvetica/Arial]
□ 图表风格:[简洁/数据优先/减少装饰]
□ 数据呈现:[同比 YoY / 环比 QoQ / 完成率]
□ 每页建议字数:≤ [X] 字(Board 层注意力有限)
第四步:撰写内容
执行摘要(1 页模板):
□ 核心信息(3-5 条):
1. 收入 [X] 亿,YoY [+X]%,完成全年目标的 [X]%
2. EBITDA [X] 亿,YoY [+X]%,利润率 [X]%
3. 重点战略项目 [X] 项进展符合预期,[X] 项偏差
4. 主要风险:[风险1](影响可控/须关注)
5. 下阶段重点:[一句话]
□ 数据佐证(如须详细数据):
→ 见财务业绩页 [X]/战略进展页 [X]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 263 lines · 97 tokens per session scan A daf82e33c8d5
board-deck-preparation is a skill published in the GitHub repository vivy-yi/finance-skills (42 stars, last pushed 4mo ago), licensed MIT. It adds 97 tokens to every session and 2,417 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
stable-diffusion-image-generation
State-of-the-art text-to-image generation with Stable Diffusion models via HuggingFace Diffusers. Use when generating images from text prompts, performing image-to-image translation, inpainting, or building custom diffusion pipelines.
excalidraw
Create hand-drawn style diagrams using Excalidraw JSON format. Generate .excalidraw files for architecture diagrams, flowcharts, sequence diagrams, concept maps, and more. Files can be opened at excalidraw.com or uploaded for shareable links.
app_evaluator
A professional skill for App Evaluation (evaluating app's performance with score) and App Improvement (giving professional suggestions for improving the app's performance).
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
tailwind-shadcn
Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.