Communitygithub.com

amplitude/builder-skills

将Google Drive文件、Granola会议记录和网络信号整合为一份每周Markdown研究摘要,包含趋势、竞争对手、想法和风险等部分。适用于产品经理将零散的研究成果整合为单一周报。

builder-skills 是什么?

这个技能旨在帮助用户将分散在Google Drive、Granola会议记录和网络各处的零散研究素材,自动整合为一份每周发布的Markdown格式研究摘要。它支持Google Drive、Granola和浏览器MCP(模型上下文协议),能够读取指定文件夹中的文件、查询最近30天的Granola会议记录,并搜索网络上的竞争对手信号、产品趋势和功能请求。最终输出结构化的四部分摘要:趋势、竞争对手、想法和风险,并附带来源引用。用户只需配置输入输出文件夹和产品描述,即可每周自动生成永不覆盖的新文件(research-summary-YYYY-MM-DD.md),确保信息不丢失且利益相关者始终知情。该技能尤其适合产品经理、战略分析师或任何需要持续跟踪市场和竞争动态的团队,可与竞争对手监控技能配合使用,并为管理层提供可追溯的决策依据。

兼容平台~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.

相关技能