Communitygithub.com

amplitude/builder-skills

用于在用户希望赢得AI引用(目前由竞争对手主导的提示)时使用的技能。它能从AI Visibility中获取竞争对手的可见性数据,找出竞争对手获胜但Amplitude缺席的特定提示,按意图进行聚类,然后生成有针对性的比较页面、替代方案内容或反驳资产,最后将草稿推送到CMS。

builder-skills 是什么?

该技能是一个AI驱动的竞争对手提示劫持器,专为内容团队设计,旨在从竞争对手手中夺回AI模型对Amplitude的引用。它首先识别用户品牌并拉取竞争对手可见性数据,然后找出特定提示(如“最佳产品分析工具”或“Mixpanel vs Amplitude”),在这些提示中竞争对手具有高可见性而Amplitude缺席。技能将这些提示按“直接比较”、“替代方案与发现”和“品类占领”三个意图桶进行聚类,并为每个桶生成优化的内容结构,包括H1标题、特性比较表、FAQ块和元数据字段。最后,它通过与CMS(支持Sanity、Contentful、HubSpot、WordPress、Ghost、Webflow)的直接集成将草稿推送到平台,确保内容团队可以直接审核和发布。该技能的核心价值在于其数据驱动的方法:分析实际的AI模型响应和竞争对手内容,识别引用差距,并生成在公平比较竞争对手的同时突出Amplitude优势的内容,从而提升AI模型引用Amplitude的可能性。

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

在你喜欢的 AI 中提问

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

文档

竞争对手提示劫持器

你正在帮助内容团队从竞争对手那里夺回AI引用。当AI模型被问到“最好的产品分析工具是什么”或“Mixpanel vs Amplitude”时,答案取决于已有的内容。这个技能会找出每一个竞争对手获胜且Amplitude缺席的提示——并生成专门设计来翻转这些引用的内容。


步骤 0 — CMS发现(每次会话开始时运行一次)

在开始其他操作之前,先确定修改后的内容将发布到哪里。这可以避免工作流程结束时出现复制粘贴的死胡同。

检查是否已连接CMS工具

扫描当前上下文中可用的工具。已知的CMS MCP模式:

CMS要查找的工具名称模式
Sanitysanity, create_documents_from_markdown, patch_document_from_markdown
Contentfulcontentful, create_entry, update_entry
HubSpot CMShubspot, update_blog_post, create_blog_post
WordPresswordpress, wp_update_post, wp_create_post
Ghostghost, update_post, create_post
Webflowwebflow, update_cms_item, create_cms_item

如果已连接CMS MCP: 用一句话确认: “我看到[CMS]已连接——完成后我会将新内容作为草稿推送到那里。听起来不错吧?” 然后继续步骤1。

如果未连接任何CMS: 简洁地询问一次:

“在我们开始之前——你通常使用哪个CMS发布内容?我可以直接将内容作为草稿推送到那里,而不是给你一段文本让你粘贴。”

提供选项:Sanity · Contentful · HubSpot · WordPress · Webflow · Ghost · 其他 · “只需给我内容”

然后根据他们的回答提供量身定制的设置建议(与prompt-gap-to-publish中的指导相同)。不要因设置而阻塞——立即开始分析,并说明在他们连接完成时你将准备好推送。


步骤 1 — 识别品牌并拉取竞争对手情况

使用list_ai_visibility_org_brands识别品牌(或使用用户指定的品牌)。

然后调用get_ai_visibility_competitors并传入选定的orgBrandId。这将返回完整的竞争对手列表,包含以下字段:brandId、brandName、brandUrl、visibility、avgRank。

按visibility降序排序。可见性最高的竞争对手是最活跃地赢得本应属于Amplitude的引用的对手。

提供一个快速表格来为用户提供方向:

竞争对手可见性 %平均排名
Google Analytics 446%2.1
Mixpanel34%2.8
...

如果用户已经指定了某个竞争对手,则使用该竞争对手并跳过选择步骤。否则询问:“你想先对付哪个竞争对手?”


步骤 2 — 找到竞争对手获胜的提示

使用get_ai_visibility_prompts并传入orgBrandId。对于每个提示,你需要了解:

  • 目标竞争对手在该提示上的可见性有多高?
  • Amplitude在该提示上的可见性有多高?

寻找以下提示:

  • 竞争对手可见性高(超过50%)并且 Amplitude可见性低(低于30%)
  • 该提示具有较高的responseCount——更多的AI回答意味着更多的引用机会
  • 提示意图是Amplitude应该可信地获胜的(而不是“如何使用Google Analytics”)

同时为最弱的5-10个提示调用get_ai_visibility_prompt_responses。阅读实际的LLM响应可以准确告诉你AI模型目前说了什么——以及你需要反驳的语言、框架和主张。


步骤 3 — 按意图对提示进行聚类

将识别出的提示分为三个类别。这些类别直接映射到内容类型:

类别1:直接比较 — 类似“[Competitor] vs Amplitude”、“Amplitude or [Competitor]”、“which is better [Competitor] or Amplitude”的提示。这些需要专门的比较页面,公平地涵盖两种工具,并为特定用例提供明确推荐。

类别2:替代方案与发现 — 类似“alternatives to [Competitor]”、“[Competitor] competitors”、“tools like [Competitor]”、“best [Competitor] replacement”的提示。这些需要一篇列表文章或替代方案页面,将Amplitude定位为首选推荐。

类别3:品类占领 — 类似“best product analytics tool”、“top digital analytics platforms”、“what should I use instead of GA4”的提示。Amplitude未出现在AI回答中,即使它直接相关。这些需要一个新的品类页面或对现有页面的升级。

呈现聚类细分:

类别提示数示例提示Amplitude可见性竞争对手可见性
直接比较8"Mixpanel vs Amplitude"42%71%
替代方案5"Mixpanel alternatives"18%0%
品类占领12"best product analytics"29%55%

询问:“你想先攻击哪个类别——直接比较、替代方案还是品类占领?” 等待他们的选择,或者如果他们想要你的推荐,建议总响应计数最高的那个。


步骤 4 — 诊断竞争对手在说什么

使用web_fetch获取所选类别中排名最高的竞争对手页面的实际内容。如果无法从数据中识别竞争对手页面,则使用步骤2中的LLM响应来了解正在提出的主张。

同时使用get_ai_visibility_pages并传入mentionsBrandId(针对竞争对手)拉取该主题上现有的Amplitude页面,过滤到amplitude.com域名。

进行比较:

竞争对手提出但Amplitude没有反驳的主张:列出每一项。这些是需要填补的空白。

竞争对手拥有的框架优势:例如,“Mixpanel以‘专为产品团队打造’领先”而Amplitude的页面是通用的。具体的框架胜过泛泛的框架。

竞争对手回答但Amplitude页面未回答的问题:从实际的LLM响应中提取——AI回答说了什么Amplitude内容没有解决的内容?

缺失的证明点:定价透明度、集成列表、客户群体、迁移指南、性能基准。

在编写任何内容之前,用4-6个要点总结诊断结果。


步骤 5 — 生成内容

根据所选类别,生成以下一种内容。完整编写——真实的句子、真实的主张,而不是骨架。

对于类别1:直接比较页面

结构:

  • H1:“[Competitor] vs Amplitude:哪种产品分析工具适合你?”(或类似)
  • 顶部的TL;DR框(2-3句话):每种工具适合谁,直接回答
  • 概述部分:对两种工具进行简短公平的描述
  • 功能比较表:在8-12个对目标受众最相关的维度上(事件跟踪、会话回放、A/B测试、定价模型、数据治理等)进行并排比较
  • 何时选择[Competitor]:诚实的列表——3-4个它们更适合的场景
  • 何时选择Amplitude:3-4个具有具体能力说明的场景
  • 迁移部分(如果相关):“从[Competitor]切换?以下是预期”
  • FAQ块:从类别1中的实际提示提取的5个问答

对于类别2:替代方案页面

结构:

  • H1:“[Year]年最佳[Competitor]替代方案:由产品团队比较”
  • 开头段落:用2句话回答核心问题——谁从[Competitor]切换以及为什么
  • 比较表:前5-6个替代方案及其关键差异点和最佳适用场景说明;Amplitude排在第一位,定位最强
  • 每个替代方案的详细部分:150-200字,涵盖其优势、不足以及适合谁
  • 从[Competitor]迁移:数据可移植性、埋点变更、学习曲线
  • FAQ块:来自类别2提示的4-5个问答

对于类别3:品类占领页面

结构:

  • H1:“[Year]年最佳[Category]工具:产品团队指南”
  • 开头:直接用2句话回答“最好的X工具是什么”
  • 比较表:6-8个工具,Amplitude针对最有价值的用例进行定位
  • 每个工具或每个用例的深入部分
  • 如何选择:包含4-5个标准的决策框架
  • FAQ块:来自类别3提示的5个问答

元字段(所有页面类型)

始终包括:

  • metaTitle — 50-60个字符,关键词丰富,对于比较页面包括竞争对手名称
  • metaDescription — 140-160个字符,回答核心查询并包含行动号召
  • slug — 确认或建议一个关键词优化的URL路径

步骤 6 — 推送到CMS

使用你在步骤0中发现的信息。这是新文档(创建操作,不是更新)。

Sanity — 使用create_documents_from_markdown并传入完整的文章内容。设置_type以匹配博客/登陆页面模式。如果不确定,询问用户:“你的Sanity模式中比较页面的文档类型是什么?”未经明确指示,切勿使用publish_documents。

Contentful — 使用create_entry并设置contentType匹配他们的博客或登陆页面类型。设置fields.title、fields.slug、fields.body。保留published: false。

HubSpot — 使用create_blog_post并设置state: DRAFT。包括元描述和slug。

WordPress — 使用wp_create_post并设置status: draft。将H1映射到title,正文映射到content。

Ghost — 使用create_post并设置status: draft。包括slug、title、html或lexical以及meta_description。

Webflow — 使用create_cms_item并针对博客集合。将字段映射到集合的模式(如果从上下文中不明显,请询问用户字段名称)。

推送后,确认:“完成——[页面标题]已作为草稿保存在[CMS]中。这是ID/URL:[链接]。发布前请在那里查看。”

始终输出完整的Markdown后备内容,即使CMS推送成功,以便团队拥有本地副本。


什么使竞争对手内容被引用

AI模型会引用那些直接、公平且具体地回答比较问题的来源。以下原则能持续翻转引用:

  • 在第一段中回答“哪个更好”。 不要让读者滚动。如果答案是“取决于用例”,那就说出来——并说明哪些用例有利于哪种工具。
  • 公平对待竞争对手。 承认竞争对手优势的页面比纯粹推广内容被认为更值得信赖。说“Mixpanel非常适合专注于漏斗的移动优先团队”表明权威性。
  • 比较表会被直接抓取。 AI模型提取结构化数据。一个标记良好的功能差异表将被逐字引用。
  • 突出且准确地使用竞争对手的名称。 AI模型需要将查询匹配到页面。关于“Mixpanel vs Amplitude”的页面必须自然且重复地使用两个名称。
  • FAQ块映射到实际提示。 使用来自AI Visibility的确切问题语言。Q与提示越接近,A被引用的可能性就越大。

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 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

Turn one or more meeting transcripts, notes, or Slack threads into concise takeaways and clear action items with DRIs. Works with a single meeting or a batch from the whole week.

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.

相关技能