Communitygithub.com

amplitude/builder-skills

访问每个竞争对手的首页、功能页、定价页和博客(使用 Chrome MCP),然后编写结构化的竞争情报报告并保存到 Google Drive。可用于每周固定竞争态势分析或按需深度调研。

builder-skills 是什么?

该技能是一款自动化竞争情报分析师,专为需要持续跟踪竞争对手动态的团队设计。它从 Google Drive 加载竞品列表,然后利用 Chrome MCP(模型上下文协议)自动访问每个竞争对手的首页、产品/功能页、定价页和博客/更新日志。技能会获取最新消息、功能发布、定价变更和博客文章等关键信号,并生成一份包含执行摘要、竞争对手快照、一览表和推荐行动的结构化 Markdown 报告。报告最终保存回 Google Drive 的指定文件夹。该技能支持按需执行和定时调度(如每周一上午 8 点),适用于 Claude Code、Cursor 和 Codex 等 AI 代理平台。用户需填写公司名称、描述、竞品文件夹路径和输出文件夹路径等占位符以完成配置。报告会为每个竞争对手重点标注一个“关注点”,帮助团队快速识别当周最重要的竞争信号。

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

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

竞争对手监控

一位每周运行的竞争情报分析师——读取你的竞品列表,访问他们的网站,然后为你撰写一份报告。

手动跟踪竞争对手意味着每周访问数十个页面、做笔记并撰写摘要。此技能可完成所有工作:从 Google 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 / 浏览器
输入位于 /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.

相关技能