Communitygithub.com

Monitoramento de Concorrentes

Visite a página inicial, de recursos, de preços e o blog de cada concorrente usando o Chrome MCP e escreva um relatório estruturado de inteligência competitiva salvo no Google Drive. Use para um pulso competitivo semanal ou um mergulho profundo sob demanda.

O que é Monitoramento de Concorrentes?

Este skill automatiza a análise de inteligência competitiva, lendo sua lista de concorrentes do Google Drive, navegando pelas principais páginas de cada um e gerando um relatório estruturado em Markdown. Ele é ideal para equipes de produto e marketing que precisam de um resumo semanal ou de uma análise aprofundada de movimentos competitivos. O skill utiliza os MCPs do Google Drive para buscar a lista de concorrentes e do Chrome/Browser para visitar as páginas. O relatório inclui um resumo executivo, snapshots por concorrente, uma tabela de visão geral e ações recomendadas, tudo salvo de volta no Google Drive. Projetado para ser executado semanalmente, mas também funciona sob demanda.

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

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

O que Monitoramento de Concorrentes faz?

Um analista semanal de inteligência competitiva — lê sua lista de concorrentes, visita seus sites e escreve um relatório para você.

Manter-se atualizado sobre os concorrentes manualmente significa visitar dezenas de páginas, fazer anotações e escrever um resumo — toda semana. Este skill faz tudo isso: puxa sua lista de concorrentes do Drive, navega pelas páginas principais de cada concorrente e produz um relatório Markdown estruturado com um instantâneo por concorrente e uma seção de ações recomendadas.


Template do Prompt

/schedule Aja como um analista de inteligência competitiva para {{COMPANY_NAME}}, {{COMPANY_DESCRIPTION}}.

### Etapa 1 — Carregar a lista de concorrentes
Puxe a lista de concorrentes do Google Drive. Verifique {{COMPETITORS_FOLDER}} e qualquer arquivo com
"concorrente" ou "panorama" no nome. Se nenhuma lista for encontrada, anote e pare.

### Etapa 2 — Pesquisar cada concorrente
Use o Chrome MCP para visitar de cada concorrente:
- Página inicial — mensagem, posicionamento, proposta de valor principal
- Página de produto / recursos — capacidades novas ou alteradas
- Página de preços — nomes dos planos, valores, mudanças na estrutura
- Blog ou changelog — postagens recentes, anúncios, notas de versão

Para cada concorrente, capture:
- Quaisquer mudanças de mensagem desde o relatório anterior (se disponível)
- Novos recursos ou capacidades anunciados ou lançados
- Mudanças de preços ou novos planos
- Postagens de blog ou anúncios recentes que valem a pena notar
- Um "alerta" — o sinal mais importante para nós

### Etapa 3 — Escrever o relatório

## Resumo Executivo
2–3 frases sobre o desenvolvimento competitivo mais importante desta semana e o que significa para nós.

## Instantâneos dos Concorrentes
Uma seção por concorrente:
**[Nome do Concorrente]**
- Manchete: Uma frase sobre seu posicionamento atual
- Novos recursos: O que eles lançaram ou anunciaram
- Preços: Quaisquer mudanças, ou "sem mudanças"
- Conteúdo recente: Postagens de blog ou anúncios que valem a pena ler
- Alerta: A única coisa que devemos prestar atenção

## Tabela de Visão Geral
| Concorrente | Maior movimento esta semana | Mudança de preço | Alerta |
|---|---|---|---|

## Ações Recomendadas
3–5 coisas concretas que nosso time deve fazer em resposta às descobertas desta semana. Comece cada uma com um verbo.

### Regras
- Salve o relatório como Competitor-Report-YYYY-MM-DD.md no Google Drive em {{OUTPUT_FOLDER}}
- Retorne o link do Drive quando terminar
- Se o site de um concorrente estiver indisponível, anote e pule — não invente
- Mantenha o resumo executivo em no máximo 3 frases

Configuração

CampoValor
MCPs necessáriosGoogle Drive, Chrome / Navegador
EntradaLista de concorrentes em /Product/Competitors/ ou qualquer arquivo do Drive com "concorrente" no nome
SaídaCompetitor-Report-YYYY-MM-DD.md → /Product/Competitors
AgendadorSemanal, segunda-feira às 8h

Placeholders para preencher

  • {{COMPANY_NAME}} — Nome da sua empresa
  • {{COMPANY_DESCRIPTION}} — Uma frase sobre o que você faz e para quem
  • {{COMPETITORS_FOLDER}} — Caminho do Drive para a pasta de concorrentes, ex. /Product/Competitors/
  • {{OUTPUT_FOLDER}} — Onde salvar os relatórios, ex. /Product/Competitors/

Dicas

  • Mantenha um competitors.md na sua pasta de Concorrentes listando as URLs das páginas principais de cada concorrente — o skill usa isso como uma lista de verificação.
  • A coluna "Alerta" na tabela de visão geral é a maneira mais rápida de escanear por urgência em uma semana movimentada.
  • Combine com market-research-digest para integrar sinais competitivos em um contexto de mercado mais amplo.
  • Se os concorrentes tiverem changelogs públicos (ex. Linear, Notion), adicione a URL do changelog à sua lista de concorrentes para o rastreamento de recursos mais confiável.

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.

Habilidades Relacionadas