Communitygithub.com

amplitude/builder-skills

Driveファイル、Granolaミーティングノート、Webシグナルを統合し、トレンド、競合、アイデア、リスクのセクションで構成された週間のMarkdown調査サマリーを作成します。PMが散在するリサーチを1つの週間ダイジェストにまとめたい場合に使用します。

builder-skills とは?

このスキルは、プロダクトマネージャー(PM)やリサーチャーが、Google Drive、Granolaミーティングノート、Web上のシグナルなど、複数のソースに散在する情報を自動的に収集・統合し、構造化された週間調査ダイジェストを生成するためのツールです。主にClaude Codeや他のAIエージェントプラットフォームで動作するように設計されており、毎週のスケジュールで実行することで、トレンド、競合の動向、プロダクトアイデア、リスクの4つのセクションからなるMarkdownサマリーを作成します。これにより、情報の見落としを防ぎ、関係者全員が最新の状況を把握できるようになります。Google Drive MCPでファイルの読み書き、Granola MCPでミーティングノートのクエリ、Browser MCPでWebシグナルの収集を行い、最終的なサマリーは日付を含むファイル名でDriveに保存され、リンクが返されます。

対応~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/product-skills/skills/market-research-digest

お気に入りのAIに質問する

このエージェントスキルを事前に読み込んだ状態で新しいチャットを開きます。

ドキュメント

市場調査ダイジェスト

散在するリサーチを構造化された週間サマリーに変換します — トレンド、競合シグナル、アイデア、リスクを1か所にまとめます。

Google Driveにファイル、Granolaにミーティングノート、そしてWeb上に散らばったシグナルがあります。このスキルは、過去1週間のすべてを読み込み、4つの明確なセクションに統合し、日付付きのMarkdownファイルをDriveに保存します。これにより、情報が失われることなく、すべてのステークホルダーが情報を把握できます。


プロンプトテンプレート

/schedule 毎週、Google Driveの{{INPUT_FOLDER}}フォルダ内のすべてのファイル(およびその中のリンク)を読み込み、Granolaのミーティングノートから過去30日間の内容をクエリし、{{PRODUCT_DESCRIPTION}}に関連する競合シグナル、プロダクトトレンド、機能リクエスト、リスクについてWebを検索します。

すべてを4つのセクションで構成されたMarkdownサマリーに統合します。

## トレンド

市場、ユーザー行動、競合環境で何が変化しているか。最も重要な動きから始めてください。各項目は2〜3文の観察結果とソースの引用を含めてください。

## 競合

競合他社が出荷、変更、または発言していることは何か。競合ごとに1エントリ。変更内容、その重要性、および(該当する場合)何をすべきかを含めてください。

## アイデア

リサーチによって明らかになったプロダクトの機会、機能のアイデア、または戦略的な動き。具体的に記述してください — 「オンボーディングを改善する」よりも「ZユーザーのY問題を解決するためにXを追加する」の方が適切です。

## リスク

プロダクトに悪影響を及ぼす可能性のある市場リスク、競合の脅威、または内部シグナル。深刻度でランク付けしてください。それぞれに推奨される緩和策を含めてください。

## ソース

使用したすべてのファイル、ミーティング、ドキュメントを引用してください。形式: [タイトル] — [ソースタイプ] — [日付(既知の場合)]

ルール:
- ソースが利用できない場合はスキップし、ファイルの先頭にその旨を記載する
- 既存のサマリーを上書きしない — 常に research-summary-YYYY-MM-DD.md という新しいファイルを作成する
- Google Driveの{{OUTPUT_FOLDER}}に保存する
- 完了したらDriveリンクを返す

セットアップ

フィールド値
必要なMCPGoogle Drive, Granola, Browser(Webシグナル用)
入力フォルダ/Product/Research(または任意のフォルダ)
出力research-summary-YYYY-MM-DD.md → /Product/Research
スケジューラ毎週

入力が必要なプレースホルダ

  • {{INPUT_FOLDER}} — リサーチフォルダのGoogle Driveパス(例: /Product/Research)
  • {{PRODUCT_DESCRIPTION}} — プロダクトの機能と対象ユーザーを1文で説明
  • {{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.

関連スキル