Communitygithub.com

amplitude/builder-skills

Leia negócios perdidos e contas canceladas do seu CRM, extraia motivos agrupados por tema (funcionalidades ausentes, preço, concorrentes, UX) e escreva uma análise semanal priorizada com recomendações de melhoria do produto. Use antes do planejamento do roadmap ou para construir o caso de priorização do trabalho de retenção.

O que é builder-skills?

Esta skill permite que você transforme dados brutos de perda de negócios e cancelamentos do seu CRM em um sinal acionável para o roadmap do produto. Ela analisa automaticamente notas de CRM, campos de motivo de perda, tags e menções a concorrentes, agrupa os feedbacks por temas (como funcionalidades ausentes, problemas de preço, vitórias da concorrência e problemas de UX) e gera um relatório priorizado. O relatório é salvo no Google Drive e inclui análises por tema, inteligência sobre concorrentes e recomendações específicas de melhoria do produto, com base na frequência e no ARR afetado. É ideal para usar antes de sessões de planejamento de roadmap ou para justificar investimentos em retenção, funcionando com CRMs como HubSpot, Attio, Intercom e Salesforce, e requer os MCPs de CRM e Google Drive.

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/analytics-skills/skills/churn-lost-deal-analysis

Perguntar na sua IA favorita

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

Documentação

Análise de Churn / Negócios Perdidos

Transforme dados de perda do CRM em sinal para o roadmap do produto — temas, padrões e recomendações concretas.

As notas de negócios perdidos e motivos de churn estão espalhadas por campos de CRM, notas de ligações e tags. Esta skill lê tudo isso, agrupa o feedback por tema, classifica os padrões mais frequentes e os traduz em sugestões específicas de melhoria do produto — fornecendo a você uma base baseada em evidências para o próximo ciclo de planejamento.


Template de Prompt

/schedule Atue como um analista de produto investigando por que {{NOME_DA_EMPRESA}} perde negócios e clientes.

### Etapa 1 — Obter negócios perdidos e contas canceladas
Leia do {{NOME_DO_CRM}} todos os negócios marcados como perdidos e contas que cancelaram nos últimos {{JANELA_DE_TEMPO}}.
Para cada registro, colete:
- Nome do negócio ou conta, ARR, data da perda/cancelamento
- Motivo da perda (do campo do CRM, se preenchido)
- Notas do negócio, notas de ligações e comentários
- Tags ou rótulos aplicados ao registro
- Concorrente mencionado, se houver

### Etapa 2 — Extrair motivos
- Funcionalidades ausentes — "precisamos de X", "seu produto não faz Y"
- Problemas de preço — "muito caro", "o concorrente é mais barato"
- Vitórias da concorrência — qual concorrente e qual vantagem eles citaram
- UX ou qualidade do produto — "difícil de usar", "muitos bugs", "lento"
- Problemas de adequação — incompatibilidade de caso de uso, ICP errado
- Problemas de processo ou vendas — anotar separadamente

### Etapa 3 — Agrupar por tema
Um tema precisa de pelo menos 2 ocorrências. Para cada tema:
- Nome do tema, número de ocorrências, ARR total afetado
- 2–3 citações diretas representativas
- A lacuna específica do produto que isso aponta

### Etapa 4 — Classificar e recomendar
Classificar por: (ocorrências × ARR médio afetado). Para cada tema principal (até 5):
**Tema**: [nome]
**Frequência**: [N], **ARR em risco**: [total]
**Causa raiz**: [o que está faltando ou errado no produto]
**Recomendação**: [mudança específica e acionável no produto]
**Evidência**: [1–2 citações diretas]

### Etapa 5 — Salvar o relatório como AnaliseChurn_AAAA-MM-DD.md em {{PASTA_DE_SAIDA}}

## Resumo / ## Principais Temas / ## Inteligência sobre Concorrentes / ## Lista de Observação

Retorne o link do Drive quando terminar.

Configuração

CampoValor
MCPs necessáriosCRM (HubSpot / Attio / Intercom), Google Drive
SaídaAnaliseChurn_AAAA-MM-DD.md → /Produto/Análise de churn
AgendadorSemanalmente, ou manualmente antes de sessões de planejamento

Placeholders para preencher

  • {{NOME_DA_EMPRESA}} — Nome da sua empresa
  • {{NOME_DO_CRM}} — Ex.: HubSpot, Attio ou Salesforce
  • {{JANELA_DE_TEMPO}} — Ex.: nos últimos 30 dias ou neste trimestre
  • {{PASTA_DE_SAIDA}} — Ex.: /Produto/Análise de churn

Dicas

  • A classificação ponderada pelo ARR é a alavanca principal — um negócio de $100K supera cinco solicitações de plano gratuito.
  • A seção de Inteligência sobre Concorrentes alimenta diretamente o monitoramento-de-concorrentes.
  • Execute trimestralmente além de semanalmente — tendências lentas se perdem no ruído semanal.
  • Compartilhe os Principais Temas com seu head de produto e líder de vendas antes de cada ciclo de planejamento.

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

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

Turn one or more meeting transcripts, notes, or Slack threads into concise takeaways and clear action items with DRIs. Works with a single meeting or a batch from the whole week.

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