Communitygithub.com

amplitude/builder-skills

運用 Richard Rumelt 的優良策略核心框架(診斷、指導方針、一致行動)來評估或制定策略。當你需要釐清模糊的戰略計劃、做出艱難抉擇,或懷疑你的「策略」其實只是一份目標清單時,可使用此技能。

builder-skills 是什麼?

此技能基於 Richard Rumelt 的《好策略.壞策略》框架,幫助 AI 代理及其使用者嚴格評估與制定策略。它能自動偵測「浮誇用語、逃避挑戰、混淆目標與策略、不良戰略目標」等四種壞策略特徵,並針對策略核心三元素——診斷、指導方針與一致行動——進行評分。對於需要制定新策略的使用者,技能會引導其逐步完成從精確診斷、擬定指導方針、設計協調行動,到識別槓桿與關鍵難題的完整流程。此技能支援 Claude Code、Cursor 等 AI 程式碼工具,適用於商業策略、產品規劃與團隊目標設定等場景。透過強制要求使用者面對真實挑戰並做出取捨,可以有效提升策略的品質與可行性。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/product-skills/skills/good-strategy-bad-strategy

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

好策略 / 壞策略

大多數的策略根本不是策略。它們只是目標清單、模糊的願望,或是拒絕做出艱難的抉擇。這個技能強迫你分辨兩者之間的差異——並且加以修正。

一個好的策略包含三個要素:對挑戰的清晰診斷、應對挑戰的指導方針,以及一套執行該方針的一致行動。如果缺少任何一個部分,你擁有的就不是策略,只是一個願望。

如需詳細的框架定義與診斷模式,請參閱 framework.md。


提示模板

你是一位應用 Richard Rumelt 好策略/壞策略框架的戰略家。

以下是相關背景資料:

<context>
$ARGUMENTS
</context>

> 如果上方為空白,請詢問使用者:「請提供以下任一項目:
- 一份您希望被評估的策略文件、計劃或 OKR
- 一個需要制定策略的商業挑戰或競爭局勢
- 一個需要被強化為真正策略的模糊戰略方向」

---

**如果使用者提供了要評估的策略:**

### 壞策略偵測器

首先,檢查壞策略的四個標誌:

1. **浮誇用語** — 聽起來專業但實際上空洞的誇大語言。充斥著聽起來很厲害但毫無意義的流行詞與術語。例如:「利用我們的綜效能力來驅動轉型價值。」去除華麗詞藻後,底下是否還有真正的想法?

2. **逃避面對挑戰** — 策略沒有承認核心難題。如果你說不出具體的障礙,就無法設計繞過它的方法。一個在景氣好壞時都同樣適用的策略,並沒有正視現實。

3. **混淆目標與策略** — 「營收成長 20%」是目標,不是策略。策略要解釋如何以及為什麼某種方法能達成目標。沒有路徑的目標只是願望。

4. **不良戰略目標** — 一長串未能解決實際挑戰的優先事項,或者彼此矛盾。如果你有 15 個策略優先事項,那你其實沒有策略優先事項。

針對每個發現的標誌,請提供:
- 表現出該標誌的具體文字或元素
- 為什麼這是個問題
- 需要如何改變

### 核心評估

然後評估策略中是否具備三個優良策略要素:

**1. 診斷** — 是否清楚定義了挑戰的本質?
- 挑戰是否具體且誠實?
- 是否區分了關鍵因素與雜訊?
- 是否點出了這個情況的困難之處?
- 評分:強 / 弱 / 缺失

**2. 指導方針** — 是否提供了克服挑戰的整體方法?
- 是否引導行動朝向明確的方向?
- 是否透過集中能量來創造優勢?
- 是否排除了某些選項?(允許所有事物的方針等於沒有方針。)
- 評分:強 / 弱 / 缺失

**3. 一致行動** — 是否說明了執行指導方針的協調步驟?
- 行動之間是否彼此協調(而非隨機清單)?
- 是否將努力集中在關鍵挑戰上?
- 在現有資源下是否可行?
- 評分:強 / 弱 / 缺失

**結論:** 這是一個好策略、壞策略,還是根本不算策略?請直接說明。

### 改寫建議

如果策略薄弱,請提供具體的修正指導——專注於核心中最弱的那個要素。

---

**如果使用者需要制定策略:**

### 步驟 1:診斷

精準且誠實地指出挑戰。

**透過回答以下問題來診斷情況:**
- 這個業務/產品/團隊目前面臨的最關鍵挑戰是什麼?
- 什麼讓它變得困難?具體的障礙是什麼,而不只是症狀?
- 發生了什麼變化,導致舊的方法不再足夠?
- 在所有相關因素中,哪 2-3 個關鍵因素最重要?

**一個好的診斷:**
- 透過找出問題的核心來簡化複雜性
- 具體到足以暗示一個方向(而不是「市場很有競爭力」)
- 說出團隊可能迴避的難堪事實
- 區分真正的問題與症狀和雜訊

**用 2-3 個段落寫出診斷。** 它應該讀起來像你在董事會上所做的誠實評估,而不是放在簡報中的樂觀敘述。

### 步驟 2:指導方針

定義能解決診斷問題的方法。

**指導方針應該:**
- 將努力導向診斷中發現的挑戰
- 排除某些事物——限制是特色,不是缺陷
- 透過專注、槓桿或定位來創造優勢
- 足夠清晰,讓人們可以根據它做出日常決策

**用 1-2 個段落寫出指導方針。** 它應該是一個單一、連貫的方向——而不是一堆不相關的計劃。

**測試指導方針:**
- 它是否源自於診斷?(如果你可以換成另一個診斷而方針仍然適用,那就太籠統了。)
- 它是否排除了某些事物?(如果它允許一切,那就不是方針。)
- 前線團隊成員能否用它來做決策?(如果不能,那就太抽象了。)

### 步驟 3:一致行動

設計執行指導方針的協調行動組合。

**一致行動應該:**
- **協調:** 它們必須協同運作——每個行動都能強化其他行動。一組不協調的計劃不是策略,而是待辦事項清單。
- **專注:** 將資源集中在關鍵點上。平均分配資源是策略的相反。
- **可行:** 在現有資源下可以達成。沒有可行性的野心只是妄想。
- **貼近:** 它們必須足夠具體以利執行——不是抽象的目標,而是有明確負責人和時間表的具体動作。

**列出 3-5 個一致行動。** 針對每個行動,說明它如何服務於指導方針,以及如何與其他行動協調。

### 步驟 4:力量來源

找出策略在哪裡創造不對稱優勢:

- **槓桿:** 用相對小的行動產生巨大的效果(找到支點)
- **貼近的目標:** 可達成的目標,能建立動能並為下一步做好準備
- **鏈條系統:** 每個環節都必須堅強的活動——競爭對手無法透過複製單一環節來模仿
- **專注:** 將努力集中在此刻最重要的地方,而不是分散
- **利用動態:** 順應變革浪潮(技術轉變、市場轉變、監管變化)來放大你的行動

### 步驟 5:關鍵難題

每個情況都有一個關鍵難題——決定成敗的單一最困難部分。指出它:
- 哪一件事如果我們做對了,其他一切都會變得更容易?
- 哪一件事如果我們搞砸了,其他一切都會變得無關緊要?
- 我們的策略是為了解決這個關鍵難題,還是迴避了它?

---

一般規則:
- 要極度誠實。一個把所有東西都評為「強」的策略檢討是沒有用的。
- 目標不是策略。預算不是策略。願景不是策略。策略是連結挑戰與行動的橋樑。
- 好策略的考驗是它「可能」失敗。如果你的「策略」保證成功(或者模糊到無法評估),那它就不是策略。
- 具體是一種美德。「在企業市場取勝」不是策略。「在金融服務業中透過成為唯一能通過 SOC2 而無需自定義配置的廠商,來贏得 IT 安全採購者的青睞」才可能是策略。

提示

  • 最常見的失敗模式是跳過診斷,直接跳到行動。沒有誠實的診斷,行動就是隨機的。
  • 如果你的「策略」文件有 30 頁長,那它很可能不是策略。核心應該能寫在一頁上。
  • 診斷是勇氣所在。它要求你說出真正困難的事情——而不是那些容易談論的事情。
  • 可以與 7-powers 結合使用,來檢查你的策略是否朝著建立持久競爭優勢的方向前進。
  • 可以與 playing-to-win 結合使用,在擁有核心框架後進行更結構化的選擇串聯。
  • 使用 pre-mortem(事前驗屍)來壓力測試一致行動,然後再做出承諾。
  • 當你有太多潛在行動需要專注於少數關鍵項目時,可以使用 prioritize(優先排序)。

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

amplitude/builder-skills

Performs deep analysis of a specific Amplitude chart to explain trends, anomalies, and likely drivers. Use when a metric looks unusual, investigating a spike or drop, or understanding the "why" behind numbers.

amplitude/builder-skills

Deeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends.

amplitude/builder-skills

Designs A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.

amplitude/builder-skills

Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.

amplitude/builder-skills

Analyze MCP server usage instrumented with Amplitude's MCP Analytics SDK: break usage and errors down by tool, read the rationales within each tool to see what callers are trying to do, and produce a prioritized write-up of actionable fixes. Use this skill whenever the user asks to understand how their MCP server is being used, what agents/users are trying to do with it, why tool calls are failing, what to fix or improve in their MCP server, or asks for an "MCP usage report", "tool error analysis", "intent analysis", "rationale clustering", or "MCP insights". Also trigger when the user mentions [MCP]-prefixed events, tool rationale, tool call errors, or just finished instrumenting their MCP server and wants to see what the data says. Requires the Amplitude MCP connector.

amplitude/builder-skills

Read lost deals and churned accounts from your CRM, extract reasons clustered by theme (missing features, pricing, competitors, UX), and write a prioritized weekly analysis with product improvement recommendations. Use before roadmap planning or to build the case for prioritizing retention work.

amplitude/builder-skills

Creates Amplitude charts from natural language descriptions, handling event selection, filters, groupings, and visualization choices. Use when you know what you want to measure but prefer not to build the chart manually.

amplitude/builder-skills

Guide an Amplitude user through building a custom agent by suggesting use cases grounded in their role and data, shaping the idea into a well-formed spec, and generating a ready-to-run Global Agent deeplink that creates it. Use to create, build, or set up a custom agent, automate a recurring analysis, or put a repeated report on a schedule.

amplitude/builder-skills

Builds comprehensive Amplitude dashboards from requirements or goals, organizing charts into logical sections with appropriate layouts. Use when creating a complete dashboard from scratch or assembling existing charts into a cohesive view.

amplitude/builder-skills

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

amplitude/builder-skills

Pull Intercom tickets and Slack support messages from the past 7 days, classify each signal, enrich with CRM data (ARR, plan, renewal), score by customer value and churn risk, and output a tiered priority report saved to Drive. Use when you need a fast, data-driven view of what support signals matter most.

amplitude/builder-skills

Use this skill whenever a user wants to improve existing pages on their website to get cited more by AI models — whether they say "our pages aren't getting cited", "improve this page for AI visibility", "which of our pages should we update", "make this article more cite-worthy", "our competitors are getting cited instead of us", "update our content for AI search", or any variation where the goal is improving an existing asset rather than creating something new. This skill pulls owned pages from AI Visibility, identifies which ones have citation potential but are underperforming, compares them against the external pages that are winning citations on the same topics, and produces section-level rewrites or a full-page update — then pushes the revision to the CMS as a draft. Trigger even if the user just says "help me get cited more" or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to win AI citations on prompts that competitors currently dominate — whether they say "competitors are getting cited instead of us", "we're losing on these prompts", "how do I outrank [competitor] in AI answers", "find prompts where we should be winning", "create content to beat [competitor]", or any variation where the goal is capturing AI share on prompts a competitor currently owns. This skill pulls competitor visibility data from AI Visibility, identifies the specific prompts where competitors win and Amplitude is absent, clusters them by intent, and produces targeted comparison pages, alternatives content, or rebuttal assets — then pushes drafts to CMS. Trigger on any mention of competitor, prompt hijack, outrank, or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to turn AI Visibility data into published content — whether they say "find content gaps", "what should we write about", "which topics have low visibility", "help me get cited by AI models", "create a blog post from our AI Visibility gaps", "we're losing to competitors on these prompts", or any variation where they want to go from AI visibility weakness to a draft article, landing page, or FAQ. This skill connects directly to Amplitude AI Visibility data (topics, prompts, visibility scores, citations, competitor data, full LLM responses and sources) and produces a publish-ready content brief plus full article draft. If the user mentions CMS (WordPress, Webflow, Contentful, Sanity, HubSpot, Ghost, Shopify), also trigger this skill to push the draft directly. Trigger even if they just say something vague like "what content should we create?" in an AI Visibility context.

amplitude/builder-skills

Use this skill whenever a user wants to test content variants before publishing to find which one will get cited most by AI models — whether they say "which version of this content will perform better", "test this article before we publish", "simulate how AI will respond to this content", "which angle should we use", "generate content variants and pick the winner", "run a simulation before publishing", or any variation where the goal is data-driven content selection rather than gut-feel publishing. This skill takes an identified content opportunity, generates 2–3 distinct variants with different angles or structures, scores them against actual AI model responses from AI Visibility, references the Simulate Changes feature for pre-publish validation, and produces a clear recommendation on which variant to publish — then pushes the winner to CMS. Trigger on any mention of "simulate", "test variants", "which performs better", "A/B content", or "before we publish".

amplitude/builder-skills

Use this skill whenever a user wants to understand which external sources are being cited by AI models on topics relevant to their brand, and wants to create content that will outrank those sources — whether they say "what sources are AI models citing", "why is [third-party site] being cited instead of us", "we want to be the definitive source on X", "build something that gets cited more than G2 or TechRadar", "create an authoritative asset", or any variation where the goal is producing a new reference asset (definition page, benchmark, methodology, glossary, comparison hub) designed to beat existing top-cited sources. This skill analyzes AI Visibility source data, reverse-engineers what makes top-cited pages authoritative, and produces a superior source asset — then pushes it to CMS as a draft. Trigger on any mention of "sources", "third-party citations", "authoritative content", "definitional pages", or "outrank".

amplitude/builder-skills

Instrument a Node/TypeScript MCP server with Amplitude's @amplitude/mcp-analytics SDK so tool calls, sessions, and rationale are tracked as Amplitude events. Use this skill whenever the user wants to add Amplitude analytics to their MCP server, mentions "MCP Analytics", "@amplitude/mcp-analytics", "instrument my MCP server", "track MCP tool calls", "add rationale to my MCP tools", or wants agent traffic (Claude, Cursor, ChatGPT) attributed back to Amplitude. Also use for adding UTM tagging to MCP-returned links, or for troubleshooting identity/user_id mismatches between MCP events and web/mobile Amplitude data.

amplitude/builder-skills

Instruments a pull request with Amplitude analytics that conform to the project's existing taxonomy. Reads the tracking plan via the Amplitude MCP server (events, properties, naming conventions), analyzes the PR diff to find the few user actions genuinely worth tracking, detects the codebase's SDK and tracking patterns, and adds instrumentation that matches both. Optionally (opt-in) stages new events and properties on an Amplitude tracking-plan branch for data-governance review. Use when asked to "instrument this PR", "add analytics to this change", "add tracking", "add Amplitude events", "instrument this feature", or "what should I track here".

amplitude/builder-skills

Diagnoses product health by cross-referencing Amplitude analytics (dashboards, charts, funnels, feedback, AI agent analytics), optionally Datadog (errors, latency, stack traces), and optionally Slack (qualitative feedback, bug reports, feature requests). Identifies what's broken, what's working, and what to do about it — with root causes, not just symptoms. Use when asked to "diagnose my product", "what's going on", "product health check", "what's broken", "where are users struggling", "give me a product diagnosis", or "what should I focus on".

amplitude/builder-skills

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

相關技能