Communitygithub.com

경쟁사 모니터링 (Competitor Monitoring)

Chrome MCP를 사용하여 각 경쟁사의 홈페이지, 기능 페이지, 가격 페이지, 블로그를 방문하고, 구조화된 경쟁 정보 보고서를 Google Drive에 저장합니다. 주간 정기 경쟁 분석 또는 필요시 심층 분석에 사용합니다.

경쟁사 모니터링 (Competitor Monitoring)란 무엇인가요?

이 스킬은 주간 경쟁 정보 분석을 자동화하는 AI 에이전트 스킬입니다. 사용자가 Google Drive에 저장한 경쟁사 목록을 읽어와 각 경쟁사의 주요 페이지(홈페이지, 기능 페이지, 가격 페이지, 블로그)를 Chrome MCP를 통해 방문하고, 그 결과를 구조화된 마크다운 보고서로 작성하여 Google Drive에 저장합니다. 보고서에는 경쟁사별 스냅샷, 주간 주요 변화 표, 권장 조치 항목이 포함되어 있어, 개발자와 제품 관리자가 수동으로 수십 개의 페이지를 방문하고 메모하는 수고를 덜어줍니다. 이 스킬은 Claude Code, Cursor, Codex 등 MCP(Model Context Protocol)를 지원하는 모든 플랫폼에서 사용할 수 있으며, 주간 스케줄러와 함께 사용하면 매주 월요일 아침 8시에 자동으로 실행되어 최신 경쟁 동향을 파악할 수 있습니다.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/product-skills/skills/competitor-monitoring

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

경쟁사 모니터링

주간 경쟁 정보 분석가 — 경쟁사 목록을 읽고, 사이트를 방문하여 보고서를 작성합니다.

경쟁사를 직접 추적하려면 매주 수십 개의 페이지를 방문하고, 메모를 하고, 요약을 작성해야 합니다. 이 스킬은 모든 작업을 자동으로 처리합니다: Drive에서 경쟁사 목록을 가져오고, 각 경쟁사의 주요 페이지를 탐색하며, 경쟁사별 스냅샷과 권장 조치 섹션이 포함된 구조화된 마크다운 보고서를 생성합니다.


프롬프트 템플릿

/schedule 경쟁 정보 분석가로 활동하며 {{COMPANY_NAME}}, {{COMPANY_DESCRIPTION}}을(를) 분석합니다.

### 1단계 — 경쟁사 목록 로드
Google Drive에서 경쟁사 목록을 가져옵니다. {{COMPETITORS_FOLDER}}와 파일 이름에 "competitor" 또는 "landscape"가 포함된 파일을 확인합니다. 목록이 없으면 기록하고 중단합니다.

### 2단계 — 각 경쟁사 조사
Chrome MCP를 사용하여 각 경쟁사의 다음 페이지를 방문합니다:
- 홈페이지 — 메시징, 포지셔닝, 헤드라인 가치 제안
- 제품/기능 페이지 — 신규 또는 변경된 기능
- 가격 페이지 — 요금제 이름, 가격, 패키징 변경
- 블로그 또는 변경 로그 — 최근 게시물, 발표, 릴리스 노트

각 경쟁사에 대해 다음을 캡처합니다:
- 이전 보고서 이후의 메시징 변경 사항 (가능한 경우)
- 발표 또는 출시된 새로운 기능
- 가격 변경 또는 새로운 요금제
- 주목할 만한 최근 블로그 게시물 또는 발표
- 하나의 "주의 사항" — 우리에게 가장 중요한 신호

### 3단계 — 보고서 작성

## 요약
이번 주 가장 중요한 경쟁 동향과 그것이 우리에게 의미하는 바를 2~3문장으로 작성합니다.

## 경쟁사 스냅샷
경쟁사별로 하나의 섹션:
**[경쟁사 이름]**
- 헤드라인: 현재 포지셔닝을 한 문장으로
- 새로운 기능: 출시 또는 발표한 기능
- 가격: 변경 사항 또는 "변경 없음"
- 최근 콘텐츠: 읽을 가치가 있는 블로그 게시물 또는 발표
- 주의 사항: 우리가 주목해야 할 단 한 가지

## 한눈에 보는 표
| 경쟁사 | 이번 주 주요 움직임 | 가격 변경 | 주의 사항 |
|---|---|---|---|

## 권장 조치
이번 주 조사 결과에 대응하여 팀이 수행해야 할 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}} — 회사가 하는 일과 대상 고객을 한 문장으로 설명
  • {{COMPETITORS_FOLDER}} — 경쟁사 폴더의 Drive 경로 (예: /Product/Competitors/)
  • {{OUTPUT_FOLDER}} — 보고서를 저장할 경로 (예: /Product/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.

관련 스킬