菜单
This skill should be used when the user asks to "stress-test these synergies," "is this deal's synergy case realistic," or has a deal or partnership's projected synergies that need cost/revenue separation, evidence checks, and a base-rate haircut.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Check installed community skills for updates. Shows a diff and requires explicit approval before applying. Use when the user says "check for updates", "update my skills", "anything new for my installed skills", or when invoked from the registry-sync agent.
Engagement-profile interview that recommends and installs a starter pack of community strategy skills. This IS the practice setup for the whole ecosystem — it asks what kind of strategist you are and recommends what to install first. Use on fresh install, when the user says "get me started" or "what should I install", or to re-run the integration-availability check after adding or removing an MCP connector.
Install a community skill from a watched registry. Reads the allowlist first, fetches, shows the RAW SKILL.md (not just a summary), runs structural trust checks, runs skills-qa, and only writes files after explicit user approval. Use when the user says "install [skill]", picks install from browse, or provides a direct skill URL.
Evaluate a skill against the Strategy Skill Design Framework — thirteen design parameters (including trust-surface, freshness, schema validation, and conflict detection), three strategy-specific failure modes, and a three-band verdict (Ready / Some Concern / Material Concerns). Use when deciding whether to trust a community skill before installing it, before deploying a first-party skill to your team, or whenever the user asks "should I trust this?" or "is this skill well-designed?". Runs automatically as part of /strategy-builder-hub:skill-installer.
This skill should be used when the user asks to "review our resource allocation," "are we funding the right things," "build a portfolio allocation view," or needs current spend, headcount, or management attention checked against strategic priority for misallocation.
This skill should be used when the user asks to "turn these numbers into a narrative," "write up our performance for the board," or provides metrics or tracker results that need to become a readable, BLUF-structured narrative rather than a table of numbers.
| name | synergy-stress-test |
| description | This skill should be used when the user asks to "stress-test these synergies," "is this deal's synergy case realistic," or has a deal or partnership's projected synergies that need cost/revenue separation, evidence checks, and a base-rate haircut. |
| allowed-tools | Read, Grep, Glob |
| metadata | {"version":"0.3.0","owner":"corporate-strategy practice","review_cadence":"quarterly","work_shape":"hypothesis-driven-analysis","permission_tier":"advisory","output_class":"draft-for-review","sourcing_policy":"volatile-facts-must-be-sourced"} |
Stress-test deal synergies — separate cost vs revenue, grade evidence, apply haircuts, bar-test deal economics. Revenue synergies must not borrow credibility from cost lines.
| Input | If missing |
|---|---|
| Synergy line items | Ask user or deck |
| Profile synergy haircut / track record | Use default base-rate table; cite source |
| Purchase price / hurdle for bar test | INPUT NEEDED — no fabricated IRR |
Default haircuts tagged [unverified — industry pattern] unless profile has org track record.
| Type | Typical realization |
|---|---|
| Cost strong evidence | ~70–90% |
| Cost weak | ~40–60% |
| Revenue any tier | ~20–40% |
Use profile overrides when configured.
~~bi analytics, ~~crm, ~~spreadsheet) require [sourced: <connector>, <asset>, <as-of>] on each load-bearing number; otherwise use INPUT NEEDED.CONFIDENCE: [...]
COST SYNERGIES: [table]
REVENUE SYNERGIES: [table]
DOUBLE-COUNTING FLAGS: [...]
TOTALS: [...]
DEAL BAR TEST: [...]
RECOMMENDATION: [...]
Input: $30M cost synergy (generic 10% G&A) + $50M revenue cross-sell (no mechanism).
Excerpt: Cost weak → ~50% haircut; revenue Weak → ~80% haircut; only works at optimistic number — material finding.
When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/corporate-strategy/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /corporate-strategy:practice-setup auto-applies a full profile write.
Follows plugin CLAUDE.md § Outputs. Next: renegotiate, evaluate-strategic-option, or IC with cost-only case.