Communitygithub.com

amplitude/builder-skills

使用 Chrome MCP 瀏覽每個競爭對手的首頁、功能頁、定價頁和部落格,然後撰寫結構化的競爭情報報告並儲存到 Google Drive。可用於每週例行競爭監控或隨需深入分析。

builder-skills 是什麼?

此技能作為一個每週競爭情報分析師,自動執行競爭對手監控流程。它從 Google Drive 讀取競爭對手清單,使用 Chrome MCP 瀏覽每個競爭對手的關鍵頁面(首頁、產品/功能頁、定價頁和部落格),並產生結構化的 Markdown 報告。報告包含執行摘要、每個競爭對手的快照(包含定位、新功能、定價變更、近期內容和「注意事項」)、一個一目瞭然的比較表格,以及 3-5 項具體的建議行動。完成的報告會以每個競爭對手資料夾中的 `competitors.md` 檔案形式儲存到 Google Drive,方便定期更新。此技能支援 Google Drive 和 Chrome/Browser MCP,可排程每週執行,非常適合需要持續追蹤競爭動態的產品經理、行銷人員和策略規劃者。

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

在你喜歡的 AI 中提問

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

說明文件

競爭對手監控

一個每週的競爭情報分析師 — 讀取你的競爭對手清單,瀏覽他們的網站,並為你撰寫一份報告。

手動追蹤競爭對手意味著每週要瀏覽數十個頁面、做筆記並撰寫摘要。這個技能一次完成所有工作:從 Drive 拉取你的競爭對手清單,瀏覽每個競爭對手的關鍵頁面,並產生一份結構化的 Markdown 報告,包含每個競爭對手的快照和建議行動章節。


提示範本

/schedule 擔任 {{COMPANY_NAME}} 的競爭情報分析師,{{COMPANY_DESCRIPTION}}。

### 步驟 1 — 載入競爭對手清單
從 Google Drive 拉取競爭對手清單。檢查 {{COMPETITORS_FOLDER}} 以及任何檔名包含
「competitor」或「landscape」的檔案。如果找不到清單,請記錄下來並停止。

### 步驟 2 — 研究每個競爭對手
使用 Chrome MCP 瀏覽每個競爭對手的:
- 首頁 — 訊息傳遞、定位、標題價值主張
- 產品/功能頁 — 新增或變更的功能
- 定價頁 — 方案名稱、價格點、套裝變更
- 部落格或更新日誌 — 近期文章、公告、發行說明

針對每個競爭對手,擷取以下資訊:
- 自上次報告以來(如果有)的任何訊息變更
- 已公告或已發佈的新功能或能力
- 定價變更或新的方案
- 值得注意的近期部落格文章或公告
- 一個「注意事項」 — 對我們最重要的單一訊號

### 步驟 3 — 撰寫報告

## 執行摘要
2-3 句話說明本週最重要的競爭發展及其對我們的意義。

## 競爭對手快照
每個競爭對手一個章節:
**[競爭對手名稱]**
- 標題:一句話說明他們當前的定位
- 新功能:他們發佈或公告的內容
- 定價:任何變更,或「無變更」
- 近期內容:值得閱讀的部落格文章或公告
- 注意事項:我們應該關注的一件事情

## 一目瞭然表格
| 競爭對手 | 本週最大行動 | 定價變更 | 注意事項 |
|---|---|---|---|

## 建議行動
3-5 項我們的團隊應針對本週發現採取回應的具體事項。每個事項以動詞開頭。

### 規則
- 將報告儲存為 Competitor-Report-YYYY-MM-DD.md 並存放到 Google Drive 的 {{OUTPUT_FOLDER}}
- 完成後回傳 Drive 連結
- 如果競爭對手的網站無法使用,請記錄並跳過 — 切勿捏造
- 執行摘要最多維持 3 句話

設定

欄位值
需要的 MCPGoogle Drive、Chrome/Browser
輸入位於 /Product/Competitors/ 的競爭對手清單,或任何檔名包含「competitor」的 Drive 檔案
輸出Competitor-Report-YYYY-MM-DD.md → /Product/Competitors
排程器每週,週一上午 8 點

需要填寫的變數

  • {{COMPANY_NAME}} — 你的公司名稱
  • {{COMPANY_DESCRIPTION}} — 一句話說明你的業務內容及服務對象
  • {{COMPETITORS_FOLDER}} — Drive 中競爭對手資料夾的路徑,例如 /Product/Competitors/
  • {{OUTPUT_FOLDER}} — 儲存報告的位置,例如 /Product/Competitors/

提示

  • 在你的競爭對手資料夾中維護一個 competitors.md 檔案,列出每個競爭對手關鍵頁面的 URL — 此技能會將其用作檢查清單。
  • 一目瞭然表格中的「注意事項」欄位是在忙碌一週中最快掃描緊急性的方式。
  • 搭配 market-research-digest 使用,可將競爭訊號編織進更廣泛的市場背景中。
  • 如果競爭對手有公開的更新日誌(例如 Linear、Notion),請將更新日誌 URL 加入競爭對手清單,以獲得最可靠的功能追蹤。

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.

相關技能