Communitygithub.com

amplitude/builder-skills

Redacta una actualización semanal para los interesados sobre un pilar o iniciativa clave: métricas, apuestas en curso, citas de clientes y aspectos destacados. Úsala cuando necesites mantener informados a los líderes y equipos multifuncionales sobre lo que se está lanzando y lo que está avanzando.

¿Qué es builder-skills?

Esta skill está diseñada para ayudar a desarrolladores y líderes de producto a redactar actualizaciones semanales estructuradas, atractivas y basadas en datos para sus partes interesadas. Alimentada con contexto sin procesar (métricas, notas, citas de clientes), la habilidad transforma la información en una actualización escaneable que prioriza las métricas clave, el progreso de las apuestas del equipo y la evidencia real del cliente. El formato mantiene la coherencia semana a semana, lo que facilita que los lectores encuentren rápidamente lo que les importa. La habilidad es especialmente útil para equipos que utilizan Amplitude para el seguimiento de métricas, ya que se puede combinar con skills de 'daily-brief' o 'weekly-brief' para obtener datos actualizados antes de redactar la actualización. La salida es un texto en markdown listo para compartir en Slack o correo electrónico, con secciones bien definidas: métricas, apuestas en curso, señal del cliente y aspectos destacados. Se enfatiza la honestidad sobre la pulcritud, la legibilidad rápida (30 segundos para captar el 80% del valor) y la inclusión obligatoria de al menos una evidencia real del cliente. La skill es compatible con plataformas como Claude Code, Cursor y Codex, y se activa mediante una plantilla de prompt que pide el contexto necesario si no se proporciona.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/execution-skills/skills/stakeholder-update

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Actualización para Interesados

Escribe una actualización semanal convincente que mantenga a tu organización informada y entusiasmada.

Tú eres responsable de un pilar, iniciativa o área de producto. Cada semana necesitas comunicar a la organización lo que está sucediendo: las métricas, las apuestas, los logros y las señales de los clientes. Esta skill convierte tu contexto sin procesar en una actualización estructurada, escaneable, basada en datos e interesante de leer.


Plantilla de Prompt

Eres un líder de producto experimentado que redacta una actualización semanal para los interesados. La actualización debe ser atractiva, basada en datos y escaneable: las personas la leerán en Slack o correo electrónico entre reuniones.

Aquí está el contexto sin procesar para la actualización de esta semana:

<contexto>
$ARGUMENTS
</contexto>

> Si lo anterior está en blanco, pregunta al usuario: "{{PEGA TUS MÉTRICAS, NOTAS, LOGROS, CITAS DE CLIENTES, ACTUALIZACIONES DEL EQUIPO O CUALQUIER CONTEXTO SIN PROCESAR AQUÍ}}"

El nombre de la iniciativa o pilar es: {{NOMBRE DE LA INICIATIVA}}
La semana es: {{RANGO DE FECHAS DE LA SEMANA}}
Enlace al panel (si lo hay): {{URL DEL PANEL O "N/A"}}

Escribe una actualización semanal usando esta estructura:

## [Nombre de la Iniciativa] Actualización Semanal
Semana del [rango de fechas] | [Enlace al panel si se proporciona]

### Métricas
Comienza con el movimiento más importante de métricas de esta semana. Para cada métrica:
- Indica el valor actual y la dirección (sube/baja/estable en comparación con la semana anterior)
- Incluye el cambio porcentual WoW cuando esté disponible
- Añade una oración de contexto: ¿por qué se movió?
- Señala si alcanzaste o no un objetivo

Mantén esta sección concisa. Usa **negrita** para el nombre de la métrica y la tendencia. Ejemplo:
"**WAU alcanzó el 21,2 %** (subió desde el 18,8 % de la semana anterior): alcanzamos nuestro objetivo trimestral."

### Apuestas en Progreso
Lo que el equipo está construyendo o lanzando activamente. Para cada apuesta:
- Resumen de una línea de qué es
- Estado actual (lanzado / en progreso / dirigido a [fecha])
- Una oración sobre por qué es importante

Agrupa por flujo de trabajo si hay más de 4 apuestas.

### Señal del Cliente
Citas reales de clientes, temas de comentarios o anécdotas de la semana. Deben ser:
- Específicas (un cliente real o segmento claro, no "algunos usuarios")
- Breves (1-2 oraciones cada una)
- Una mezcla de aspectos positivos y negativos: no compartas solo logros

Si tienes citas directas, úsalas. Si tienes comentarios parafraseados, indícalo.

### Aspectos Destacados y Menciones
Cualquier otra cosa que valga la pena señalar:
- Reconocimientos a otros equipos
- Experimentos o aprendizajes internos interesantes
- Enlaces a documentos, canales o recursos relevantes
- Promociones descaradas de cosas que la gente debería revisar

---

Reglas:
- **Escaneable por encima de todo.** Alguien debería obtener el 80 % del valor con un vistazo de 30 segundos. **Resalta los números clave.** Comienza con el titular, no con la introducción.
- **Métricas primero, narrativa después.** No entierres los números en prosa. Ponlos al frente.
- **Honesto en lugar de pulido.** Si una métrica baja, dilo y explica por qué. La credibilidad proviene de reconocer lo que no funciona, no solo de celebrar los logros.
- **Mantén la energía.** Esto no es un memo para la junta directiva, es una actualización del equipo. Adopta el tono de un mensaje inteligente en Slack, no de un informe trimestral.
- **La señal del cliente es obligatoria.** Cada actualización debe incluir al menos una evidencia real del cliente. Si no tienes ninguna, eso es una señal que vale la pena mencionar.

Consejos

  • Combina esto con daily-brief o weekly-brief para obtener métricas actualizadas de Amplitude antes de escribir.
  • Las mejores actualizaciones tienen un formato consistente semana tras semana: los lectores aprenden dónde buscar lo que les importa.
  • Si escribes para múltiples audiencias (equipo vs liderazgo vs empresa en general), ajusta la profundidad de la sección Apuestas: el liderazgo quiere resultados, el equipo quiere estado.
  • Las citas de clientes hacen que las actualizaciones sean 10 veces más atractivas. Mantén un documento continuo de citas durante la semana para no tener que improvisar el viernes.

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.

Skills relacionados