Communitygithub.com

amplitude/builder-skills

各競合のホームページ、機能ページ、料金ページ、ブログをChrome MCPで訪問し、構造化された競合インテリジェンスレポートを作成してGoogle Driveに保存します。定期的な週次競合パルスやオンデマンドの詳細分析に使用します。

builder-skills とは?

このスキルは、週次の競合インテリジェンス分析を自動化するAIエージェントです。Google Driveから競合リストを読み込み、Chrome MCP(ブラウザ操作機能)を使用して各競合の主要ページ(ホームページ、機能ページ、料金ページ、ブログ)を訪問し、その情報を構造化されたマークダウンレポートとして生成します。レポートはエグゼクティブサマリー、競合スナップショット、一覧表、推奨アクションで構成され、最終的にGoogle Driveに保存されます。Claude CodeやCursorなどのAIエージェントプラットフォームで動作し、週次の定期実行やオンデマンドでの詳細分析に利用できます。このスキルを使うことで、手動での競合調査にかかる時間を大幅に削減し、常に最新の競合情報をチームで共有できるようになります。

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

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

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

ドキュメント

競合モニタリング

週次の競合インテリジェンスアナリスト — 競合リストを読み取り、各サイトを訪問し、レポートを作成します。

競合の動向を手動で把握するには、毎週多数のページを訪問し、メモを取り、サマリーを作成する必要があります。このスキルはそのすべてを自動化します。Driveから競合リストを取得し、各競合の主要ページを閲覧し、競合ごとのスナップショットと推奨アクションセクションを含む構造化されたMarkdownレポートを作成します。


プロンプトテンプレート

/schedule Act as a competitive intelligence analyst for {{COMPANY_NAME}}, {{COMPANY_DESCRIPTION}}.

### Step 1 — 競合リストのロード
Google Driveから競合リストを取得します。{{COMPETITORS_FOLDER}} および名前に「competitor」または「landscape」を含むファイルを確認します。リストが見つからない場合は、その旨を記録して停止します。

### Step 2 — 各競合の調査
Chrome MCPを使用して、各競合の以下を訪問します:
- ホームページ — メッセージング、ポジショニング、ヘッドラインのバリュープロポジション
- 製品/機能ページ — 新機能や変更された機能
- 料金ページ — プラン名、価格帯、パッケージの変更
- ブログまたはチェンジログ — 最近の投稿、発表、リリースノート

各競合について、以下を取得します:
- 前回のレポート以降のメッセージングの変更(利用可能な場合)
- 発表またはリリースされた新機能
- 価格変更または新しいプラン
- 注目すべき最近のブログ投稿や発表
- 1つの「ウォッチアウト」 — 私たちにとって最も重要なシグナル

### Step 3 — レポートの作成

## エグゼクティブサマリー
今週の最も重要な競合動向と、それが自社にとって何を意味するかを2〜3文で。

## 競合スナップショット
競合ごとに1セクション:
**[競合名]**
- ヘッドライン:現在のポジショニングを1文で
- 新機能:リリースまたは発表されたもの
- 料金:変更の有無、または「変更なし」
- 最近のコンテンツ:注目すべきブログ投稿や発表
- ウォッチアウト:注意すべき1つのこと

## 一目でわかる表
| 競合 | 今週の最大の動き | 料金変更 | ウォッチアウト |
|---|---|---|---|

## 推奨アクション
今週の調査結果を受けてチームが取るべき具体的なアクションを3〜5つ。各アクションは動詞で始めてください。

### ルール
- レポートを Competitor-Report-YYYY-MM-DD.md としてGoogle Driveの {{OUTPUT_FOLDER}} に保存する
- 完了時にDriveリンクを返す
- 競合のサイトが利用できない場合はその旨を記録してスキップする — 捏造しない
- エグゼクティブサマリーは最大3文に抑える

セットアップ

フィールド値
必要なMCPGoogle Drive, Chrome / Browser
入力/Product/Competitors/ または名前に「competitor」を含む任意のDriveファイル内の競合リスト
出力Competitor-Report-YYYY-MM-DD.md → /Product/Competitors
スケジューラー毎週月曜午前8時

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

  • {{COMPANY_NAME}} — 自社の会社名
  • {{COMPANY_DESCRIPTION}} — 自社の事業と対象顧客を1文で
  • {{COMPETITORS_FOLDER}} — 競合フォルダへのDriveパス(例: /Product/Competitors/)
  • {{OUTPUT_FOLDER}} — レポートの保存先(例: /Product/Competitors/)

ヒント

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

関連スキル