Communitygithub.com

amplitude/builder-skills

分析AI模型引用的外部来源,生成权威内容以超越这些来源,并将其作为草稿推送到CMS。

builder-skills 是什么?

该技能旨在帮助内容团队成为AI模型的首选引用来源,而不仅仅是针对品牌查询,还包括类别定义性问题。它通过分析AI Visibility数据,识别出AI模型在相关主题上引用的顶级第三方来源,并逆向工程分析这些页面为何具有权威性。技能会评估来源的答案结构、数据具体性、全面性、时效性和权威信号,然后识别出最佳的内容资产机会(如权威指南、基准报告或对比中心),并生成比现有来源更全面、更具体的发布就绪内容。最终,该技能会利用已连接的CMS工具(如Sanity、Contentful、HubSpot等)将内容作为草稿推送,并始终提供Markdown备份。此技能适用于希望了解品牌在AI模型中引用情况并创建超越第三方来源的内容团队,支持多种CMS平台和内容类型。

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

在你喜欢的 AI 中提问

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

文档

来源超越器

你正在帮助一个内容团队成为AI模型引用的首要来源——不仅仅是针对品牌查询,而是针对定义类问题。当AI被问到“什么是产品分析”或“数字分析工具如何工作”时,它会引用它认为最权威的页面。此技能负责找到这些页面,分析它们为何胜出,并构建出更好的内容。


第 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?我可以直接将内容作为草稿推送到那里,而不是给您一段需要粘贴的文本块。”

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

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


第 1 步 — 识别品牌并提取顶级引用来源

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

然后使用选定的 orgBrandId 调用 get_ai_visibility_sources,按 citationCount 降序排序。这将返回 AI 模型在与品牌相关的主题上引用的每个域名,包括以下字段:domain、citationCount、responseCount、url、title。

将结果分成两组:

  • 自有来源:品牌自己域名上的页面(例如 amplitude.com)
  • 第三方来源:其他所有内容——评论网站、媒体、文档、竞争对手博客

排名超过品牌自有域名的第三方来源就是目标。这些是你需要超越的页面。

按引用数识别前 10 个第三方来源。显示摘要:

来源域名引用数类型
g2.com340评论聚合器
contentsquare.com/blog180竞争对手博客
techradar.com150媒体
...

同时调用 get_ai_visibility_topics 来了解哪些主题正在驱动这些引用——你将用它来选择要构建哪个来源资产。


第 2 步 — 审计顶级来源获胜的原因

对于前 5 个第三方来源中的每一个,使用 web_fetch 获取实际页面内容。仔细阅读每一个。你需要寻找使这些页面在 AI 模型中具有权威性的结构和内容模式。

评估每个来源的以下方面:

答案结构:页面是否直接回答了一个清晰的问题?它是否具有映射到子问题的 H2 和 H3 层次结构?结构清晰的页面更可靠地被抓取。

数据和具体性:页面是否引用了统计数据、基准、调查结果或其他可验证的数据?AI 模型会不成比例地引用带有具体数据的页面,而不是观点。

全面性:它是否详尽地涵盖了主题——历史、机制、用例、比较、常见问题?覆盖范围窄的内容输给覆盖范围深的内容。

时效性信号:页面是否突出显示了日期、“[年]更新版”或引用了近期事件?AI 模型倾向于看起来是当前信息的来源。

权威性信号:作者资历、公司声誉、方法论披露、研究引用、同行参考。

资产类型:什么格式使此页面具有权威性?常见的获胜格式:

  • 定义指南(“什么是产品分析”)
  • 基准报告(“2025年产品分析状况”)
  • 方法论解释(“会话回放如何工作”)
  • 词汇表(“产品分析术语解释”)
  • 对比中心(“产品分析工具对比”)

将审计总结为一个模式:“关于此主题,顶级引用来源的特点是:[3–4 个模式]。品牌现有内容缺少:[2–3 个差距]。”


第 3 步 — 确定来源资产机会

基于审计,确定要构建的最高杠杆来源资产。根据以下标准对机会进行评分:

引用差距:顶级外部来源比品牌在同一主题上的最佳自有页面多出多少引用?200 次以上的差距是高价值目标。

主题战略重要性:与 get_ai_visibility_topics 交叉引用——这是品牌具有高相关性但低可见性的主题吗?如果是,拥有该来源将产生复合影响。

可构建性:品牌能否可信地拥有这种资产类型?基准报告需要数据;定义指南只需要专业知识。优先选择品牌能够以权威性产出的资产。

资产类型选择指南:

  • 如果顶级来源是定义页面 → 构建一个更深入的全面指南
  • 如果顶级来源是评论聚合器(G2、Capterra) → 构建一个方法论/透明度页面,让 AI 模型将其引用为比较标准的主要来源
  • 如果顶级来源是竞争对手博客 → 构建一个中立、数据丰富的资产,比竞争对手的自利版本更具权威性
  • 如果顶级来源是媒体/分析师报告 → 构建一个专有基准或研究报告

提出 2–3 个资产选项 并附上推荐:

#资产类型目标主题预计引用差距推荐
1权威指南“什么是产品分析”−280优先构建:定义类,高搜索量
2基准报告“2025年产品分析采用情况”−140第二步构建:需要数据
3对比中心“产品分析工具对比”−95不错,但竞争激烈

提问:“您想构建哪个资产?” 等待他们的选择。


第 4 步 — 生成来源资产

编写完整的资产。不是框架——而是真正比它旨在超越的来源更有用、更具体、更全面的、可发布的完整内容。

资产类型模板

权威指南(“什么是 X”、“X 如何工作”、“X 完全指南”)

  • H1:直接回答定义性问题
  • 开头(2–3 段):第一句直接定义;为什么重要;本指南涵盖内容
  • 核心部分(5–8 个 H2):定义 → 工作原理 → 关键组件 → 按公司类型的使用案例 → 如何评估 → 实施考虑因素 → 常见问题
  • 数据点:至少包含 5 个具体统计数据或基准(注明来源,如果是专有数据则注明来自 Amplitude 研究)
  • 辅图描述:提及哪些图表、截图或表格可以强化每个部分——即使不包含图片,所描述的结构也标志着权威性
  • 常见问题块:6–8 个问答,使用与此主题上 AI Visibility 提示完全相同的关键词
  • 内部链接:4–5 个指向相关 Amplitude 内容的链接
  • 最后更新备注:在元数据中包含“最后更新:[当前月份/年份]”

基准报告(“X 的状况”、“X 趋势报告”、“X 数据洞察”)

  • H1:“[类别] 基准报告 [年]:关键指标和趋势”
  • 执行摘要:5–7 个主要发现,采用项目符号形式
  • 方法论部分:数据收集方式、样本量、时间段——AI 模型喜欢引用透明的方法论
  • 数据部分(4–6 个 H2):每个部分都有标题级发现、支持数据和解读
  • 按细分比较:企业级 vs 中小企业、行业垂直领域、公司阶段
  • 趋势分析:逐年变化(如果有数据)
  • 建议:数据对产品团队的意义
  • 常见问题块:4–5 个问答

对比中心(“X 工具对比”、“最佳 X 平台”、“[类别] 软件指南”)

  • H1:“[年]最佳 [类别] 工具:产品团队对比指南”
  • 选择标准:工具如何评估——这使对比值得信赖
  • 摘要对比表:8–10 个工具,关键维度,最佳适用标记
  • 每个工具的深度分析:每个 200–300 字,涵盖优势、局限性、定价模式、最佳适用场景
  • 决策框架:采用“如果 [条件],选择 X”格式,覆盖 5–6 种场景
  • 常见问题块:5–6 个问答

始终包含元字段

  • metaTitle — 50–60 个字符,包含主要关键词
  • metaDescription — 140–160 个字符,标记权威性和全面性
  • slug — 关键词丰富且具体(例如 /blog/what-is-product-analytics 而不是 /blog/analytics)
  • lastUpdated — 当前日期

第 5 步 — 推送到 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:[链接]。发布前请在那里查看。”

即使 CMS 推送成功,也始终输出完整内容的 Markdown 备用版本。


什么使来源对 AI 模型具有权威性

AI 模型引用来源不是因为它们来自大品牌。它们引用那些:

  • 比任何人都更好地回答了特定问题。 “什么是产品分析”的最佳来源是那个最清晰、最完整、最直接地定义它的页面。
  • 包含具有透明方法论的数据。 一个说“我们调查了 500 个产品团队”的基准报告比一个说“领先专家认为”的基准报告更有可能被引用。
  • 从各个角度覆盖主题。 AI 模型更喜欢全面的来源而非狭窄的来源。一个涵盖定义、机制、用例、评估标准和常见问题的指南,将在任何单一维度上击败较短的页面。
  • 明确标注了日期。 一个“2025 年 4 月更新”的标签标志着新鲜度。AI 模型避免引用在快速变化主题上过时的来源。
  • 链接到其他权威信号。 指向相关内容的内部链接、外部数据引用、作者资历——所有这些都会增加页面在 AI 训练和推理中的信任分数。

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

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.

相关技能