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 strategy-execution-trackinggit 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/strategy-execution-tracking)<a href="https://agentmods.dev/skills/vivy-yi/finance-skills/strategy-execution-tracking"><img src="https://agentmods.dev/badge/skills/vivy-yi/finance-skills/strategy-execution-tracking/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/strategy-execution-tracking"><img src="https://agentmods.dev/badge/skills/vivy-yi/finance-skills/strategy-execution-tracking.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.00089 | $0.02092 |
| Opus 5 | $0.00044 | $0.01046 |
| Sonnet 5 | $0.00018 | $0.00418 |
| Haiku 4.5 | $0.00009 | $0.00209 |
Grade A, and why
strategy-execution-tracking 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 9d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
加载上下文
首次使用时: 读取 ../../CLAUDE.md 获取场景级配置(战略目标/里程碑/追踪频率)。
/strategy-execution-tracking — 战略执行追踪
Examples
→ 示例:用户说"战略举措执行了大半年了,帮我看看对业绩指标的实际影响",系统应调用本技能,执行战略举措与业绩指标关联分析。
→ 示例:用户说"有几个战略举措落后于计划,帮我识别瓶颈和调整建议",系统应调用本技能,执行战略执行差距分析和改进建议。
→ 示例:用户说"半年度战略回顾,帮我准备一份战略执行进度全景报告",系统应调用本技能,生成半年度战略执行报告。
第一步:战略目标达成评估
财务目标追踪:
□ 战略规划周期:[YYYY - YYYY]
□ 本期追踪期间:[YYYY-QX]
□ 规划执行进度:[X]%([X]/[X] 年)
□ 财务目标达成:
| 指标 | [YYYY]年目标 | 本期实际 | 达成率 | 趋势 |
|------|------------|---------|--------|------|
| 收入 | [X]亿 | [X]亿 | [X]% | [↑↓—] |
| EBITDA | [X]亿 | [X]亿 | [X]% | [↑↓—] |
□ 整体达成评估:
→ 综合达成率:[X]%([X] 项达标 / [X] 项)
→ 达成评价:[✅ 超额/符合/低于]
战略目标达成:
□ 战略目标追踪:
| 战略目标 | 成功标志 | 当前状态 | 达成评估 |
|---------|---------|---------|---------|
| [目标1] | [标志] | [状态] | [✅/⚠️/🔴] |
| [目标2] | [标志] | [状态] | [✅/⚠️/🔴] |
□ 整体战略目标达成:[X]/[X] 项达标([X]%)
第二步:里程碑达成评估
关键里程碑追踪:
□ 本期应达成里程碑:[X] 项
□ 实际达成:[X] 项
□ 达成率:[X]%
□ 里程碑明细:
| 里程碑 | 原计划日期 | 实际日期 | 状态 | 偏差说明 |
|--------|-----------|---------|------|---------|
| [里程碑1] | [日期] | [日期/—] | [✅/⚠️/🔴] | [说明] |
| [里程碑2] | [日期] | [日期/—] | [✅/⚠️/🔴] | [说明] |
延期里程碑分析:
□ 延期里程碑:[X] 项
□ 延期原因分类:
→ 内部执行问题:[X] 项 — [描述]
→ 外部因素:[X] 项 — [描述]
→ 资源不足:[X] 项 — [描述]
→ 计划过于激进:[X] 项 — [描述]
第三步:执行偏差分析
偏差识别:
□ 重大偏差项(> [X]% 偏离目标):
→ [指标/里程碑] — 目标 [X],实际 [X],偏差 [±X]%
→ 原因:[描述]
→ 影响:[对战略目标的影响]
□ 中等偏差项([X-X]% 偏离):
→ [指标/里程碑] — 偏差 [±X]%
→ 原因:[描述]
偏差根因分析:
□ 针对 [重大偏差项] 的根因:
→ 直接原因:[描述]
→ 深层原因:[描述]
→ 根因分类:[执行问题/资源问题/外部环境/计划问题]
□ 执行问题 vs 环境变化:
→ 执行问题导致:[X]% 的偏差
→ 环境变化导致:[X]% 的偏差
第四步:战略健康度评估
战略健康度维度:
□ 财务健康度:[✅ 良好 / ⚠️ 承压 / 🔴 危险]
→ 收入增速 vs 战略要求:[X]% vs [X]%
→ 盈利能力:[描述]
□ 执行健康度:[✅ 良好 / ⚠️ 承压 / 🔴 危险]
→ 里程碑达成率:[X]%
→ 战略举措推进:[描述]
□ 组织健康度:[✅ 良好 / ⚠️ 承压 / 🔴 危险]
→ 关键人才到位:[X]%
→ 组织能力:[描述]
□ 整体战略健康度:[✅ 绿色 / 🟡 黄色 / 🔴 红色]
战略风险信号:
□ 风险信号:
→ 信号 1:[描述] — 影响 [目标/里程碑]
→ 信号 2:[描述]
□ 机会信号:
→ 机会 1:[描述] — 潜在收益 [描述]
第五步:调整建议
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.
- 9d ago First seen · 244 lines · 89 tokens per session scan A f53bead7516b
strategy-execution-tracking is a skill published in the GitHub repository vivy-yi/finance-skills (29 stars, last pushed 3mo ago), licensed MIT. It adds 89 tokens to every session and 2,092 once invoked, about $0.0004 per session on Opus 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-09-03.
Other skills, from other repositories
infographics
Create professional infographics using Nano Banana Pro AI with smart iterative refinement. Uses Gemini 3 Pro for quality review. Integrates research-lookup and web search for accurate data. Supports 10 infographic types, 8 industry styles, and colorblind-safe palettes.
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
figma-implement-design
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a…
datavis
Comprehensive data visualization toolkit for creating beautiful, mathematically elegant visualizations with D3.js, Chart.js, and custom SVG. Use when (1) building interactive data visualizations, (2) designing color palettes for charts, (3) choosing scales and visual encodings, (4) creating data pipelines from…
spec-kit-vibe-compat
Compatibility router for /speckit. workflows into /vibe-first Codex execution.
detecting-data-anomalies
Investigate outliers, rare events, spikes, and suspicious records in datasets. Use as an explicit anomaly-analysis helper when you want concrete anomaly-detection workflow guidance, not generic data validation or end-to-end ML ownership.