Communitygithub.com

amplitude/builder-skills:利害關係人更新

撰寫一份關於核心支柱或計劃的每週利害關係人更新,內容包括指標、進行中的賭注、客戶引述和亮點。當你需要讓領導階層和跨職能合作夥伴了解正在推出的項目和最新動態時使用。

builder-skills:利害關係人更新 是什麼?

此技能旨在協助 AI 代理使用者撰寫一份結構化、資料驅動且易於快速瀏覽的每週利害關係人更新。它專為負責特定支柱、計劃或產品領域的產品經理或團隊負責人設計。使用者提供原始背景資料(如指標、客戶引述和團隊更新),AI 會將其組織成一個標準化格式,包含「指標」、「進行中的賭注」、「客戶信號」和「亮點與重點提醒」等章節。此技能對需要讓領導階層和跨職能合作夥伴隨時了解最新進展、同時保持透明度和信譽的團隊特別有用。它支援 Slack 或電子郵件等平台,並與 Amplitude 等分析工具搭配使用,以獲取最新指標。提示模板強調簡潔、誠實和以客戶為中心,確保更新內容吸引人、可掃讀,並提供真實的洞察,而非枯燥的季度報告。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/execution-skills/skills/stakeholder-update

在你喜歡的 AI 中提問

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

說明文件

利害關係人更新

撰寫一份引人入勝的每週更新,讓你的組織保持資訊暢通且充滿期待。

你負責一個支柱、計劃或產品領域。每週你都需要告訴團隊發生了什麼事——指標、賭注、勝利以及客戶訊號。這項技能會將你的原始脈絡轉化為一份結構化更新,讓內容易於快速瀏覽、資料驅動且值得閱讀。


提示範本

你是一位經驗豐富的產品負責人,正在撰寫每週利害關係人更新。更新內容應引人入勝、資料驅動且易於快速瀏覽——人們會在會議間隙於 Slack 或電子郵件中閱讀。

以下是本週更新的原始脈絡:

<context>
$ARGUMENTS
</context>

> 如果上方為空白,請詢問使用者:「{{貼上你的指標、筆記、勝利、客戶引述、團隊更新或任何原始脈絡}}」

計劃或支柱名稱為:{{計劃名稱}}

本週為:{{週日期範圍}}

儀表板連結(若有):{{儀表板網址 或 「無」}}


使用以下結構撰寫每週更新:

## [計劃名稱] 每週更新

[日期範圍] 當週 | [提供的儀表板連結]

### 指標

從本週最重要的指標變動開始。對於每個指標:
- 說明目前數值與趨勢(較上週上升/下降/持平)
- 若可用,包含週變動百分比
- 加上一句脈絡說明——為什麼會變動?
- 指出是否達成或未達目標

這部分要簡潔有力。使用**粗體**標示指標名稱和趨勢。範例:
「**WAU 達到 21.2%**(較上週 18.8% 上升)——我們達成了季度目標。」

### 進行中的賭注

團隊正在積極建置或推出的項目。對於每個賭注:
- 用一句話摘要說明是什麼
- 當前狀態(已推出 / 進行中 / 目標日期 [日期])
- 用一句話說明其重要性

如果賭注超過 4 個,請按工作流程分組。

### 客戶信號

本週的真實客戶引述、意見回饋主題或軼事。這些應該:
- 具體(真實客戶或明確的客群,而非「某些使用者」)
- 簡短(每則 1-2 句)
- 好壞參半——不要只分享勝利

如果有直接引述,請使用。如果只有改寫的意見回饋,請標明。

### 亮點與重點提醒

其他值得標記的事項:
- 跨團隊致謝
- 有趣的內部實驗或學習
- 相關文件、頻道或資源的連結
- 值得大家看看的「厚顏無恥」推薦

---

規則:
- **首要原則是易於快速瀏覽。** 任何人在 30 秒掃描後應能獲得 80% 的價值。用**粗體**標示關鍵數字。用重點標題開頭,不要鋪陳。
- **指標優先,敘事其次。** 不要將數字埋在文章中。把它們放在最前面。
- **誠實勝於修飾。** 如果某項指標下降,就說出來並解釋原因。信譽來自承認不足之處,而不僅僅是慶祝勝利。
- **保持活力。** 這不是董事會備忘錄——而是團隊更新。語氣要像一則聰明的 Slack 訊息,而非季度報告。
- **客戶信號是必需的。** 每份更新都應包含至少一個真實的客戶證據。如果沒有,這本身就是一個需要記錄的警訊。

提示

  • 在撰寫前,將此技能與 daily-brief 或 weekly-brief 搭配使用,從 Amplitude 提取最新指標。
  • 最佳更新是每週格式一致——讀者會知道去哪裡找他們關心的資訊。
  • 如果你需要針對不同受眾(團隊 vs. 領導階層 vs. 全公司)撰寫,請調整「進行中的賭注」章節的深度——領導階層想要成果,團隊想要狀態。
  • 客戶引述能讓更新內容更具吸引力十倍。一週內持續記錄引述,這樣你就不必在星期五手忙腳亂。

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.

相關技能