Communitygithub.com

amplitude/builder-skills

將 Google Drive 檔案、Granola 會議記錄與網路訊號整合為一份結構化的每週 Markdown 研究摘要,包含趨勢、競爭者、想法與風險等章節。適合 PM 將零散的研究資料匯總成一份每週摘要。

builder-skills 是什麼?

此技能旨在協助產品經理或研究人員將散落在 Google Drive、Granola 會議記錄與網路上的零碎資訊,自動整合為一份結構清晰的每週研究摘要。它會讀取過去一週內指定 Google Drive 資料夾中的所有檔案與連結、查詢近 30 天的 Granola 會議記錄,並搜尋網路上的競爭者動態、產品趨勢、功能需求與潛在風險。最終產出一個包含「趨勢」「競爭者」「想法」與「風險」四個章節的 Markdown 檔案,並自動儲存回 Google Drive,確保所有利害關係人都能掌握最新資訊。此技能適用於 Claude Code、Cursor 等支援 MCP 協定的 AI 代理平台,需搭配 Google Drive、Granola 與瀏覽器相關的 MCP 伺服器。透過排程器可設定為每週自動執行,大幅節省手動整理時間。

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

在你喜歡的 AI 中提問

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

說明文件

市場研究摘要

將零散的研究資料轉化為結構化的每週摘要——趨勢、競爭者訊號、想法與風險,全在一處。

您有檔案在 Google Drive、會議記錄在 Granola,以及散落在網路上的各種訊號。此技能會讀取過去一週的所有內容,將其整合為四個清晰的章節,並將帶有日期的 Markdown 檔案儲存回 Google Drive——如此一來,資訊不會遺失,每位利害關係人都能掌握最新動態。


提示範本

/schedule 每週,讀取我在 Google Drive {{INPUT_FOLDER}} 資料夾中的所有檔案(以及其中的任何連結)、
查詢我過去 30 天內的 Granola 會議記錄,並搜尋網路上的競爭者訊號、產品趨勢、功能需求
以及與 {{PRODUCT_DESCRIPTION}} 相關的風險。

將所有內容整合為一份包含以下四個章節的 Markdown 摘要:

## 趨勢

市場、使用者行為或競爭格局正在發生哪些變化?以最重要的動態開頭。每個項目應包含 2-3 句觀察與來源引用。

## 競爭者

競爭者推出了什麼、改變了什麼或說了什麼?每個競爭者一個條目。包含:改變了什麼、為什麼重要,以及(如果有的話)該採取什麼行動。

## 想法

研究過程中發現的產品機會、功能想法或策略方向。請具體說明——「為 Z 使用者增加 X 來解決 Y 問題」優於「改善新手上路流程」。

## 風險

可能對產品造成損害的市場風險、競爭威脅或內部訊號。依嚴重程度排序。每個風險需包含建議的緩解措施。

## 來源

引用每個使用的檔案、會議與文件。格式:[標題] — [來源類型] — [日期(如已知)]

規則:
- 如果任何來源無法取得,請跳過並在檔案頂部註明
- 不要覆蓋現有的摘要——總是建立名為 research-summary-YYYY-MM-DD.md 的新檔案
- 儲存至 Google Drive 的 {{OUTPUT_FOLDER}}
- 完成時回傳 Drive 連結

設定

欄位值
需要的 MCPGoogle Drive、Granola、瀏覽器(用於網路訊號)
輸入資料夾/Product/Research(或您的資料夾)
輸出research-summary-YYYY-MM-DD.md → /Product/Research
排程器每週

需填入的變數

  • {{INPUT_FOLDER}} — Google Drive 中您的研究資料夾路徑,例如 /Product/Research
  • {{PRODUCT_DESCRIPTION}} — 一句話說明您的產品是做什麼的、服務哪些使用者
  • {{OUTPUT_FOLDER}} — 摘要的儲存位置,例如 /Product/Research

提示

  • 在您的研究資料夾中維護一個 competitors.md 檔案,列出要監控的競爭者——技能會自動找到它。
  • 將新聞通訊、部落格或分析師報告的連結加入您的研究資料夾,技能會自動擷取。
  • 可與 competitor-monitoring 技能搭配使用,以相同的排程進行更深入的競爭者分析。
  • 「來源」章節讓此摘要易於與領導層分享——每個陳述都可追溯。

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.

相關技能