Communitygithub.com

síntesis-de-reuniones

Convierte una o más transcripciones de reuniones, notas o hilos de Slack en conclusiones concisas y elementos de acción claros con responsables designados. Funciona con una sola reunión o con un lote de toda la semana.

¿Qué es síntesis-de-reuniones?

Esta habilidad está diseñada para desarrolladores y usuarios de agentes de IA que necesitan extraer rápidamente información procesable de reuniones, transcripciones o conversaciones. Ofrece dos modos: uno para una sola reunión y otro para múltiples reuniones. En el modo individual, genera una sección de decisiones clave, un resumen de conclusiones (máximo 3-5 viñetas), una tabla de elementos de acción con responsables (DRI) y fechas límite, y preguntas abiertas. En el modo múltiple, primero crea un resumen por reunión y luego consolida todas las decisiones, elementos de acción (con columna de origen), temas transversales y preguntas abiertas, eliminando duplicados. La habilidad prioriza la brevedad y la claridad: los elementos de acción deben ser específicos y accionables, y cualquier tarea sin responsable se marca como "NEEDS DRI". Es compatible con plataformas como Claude Code, Cursor y Codex, y funciona con transcripciones sin procesar (Otter, Fireflies, Google Meet), hilos de Slack o notas desordenadas. El prompt de la habilidad proporciona una plantilla detallada que guía al agente de IA para que distinga entre reuniones únicas y múltiples, genere tablas estructuradas y evite ruido como charlas intrascendentes o desvíos. Es especialmente útil para equipos que realizan reuniones recurrentes (standups, sincronizaciones) o para procesar lotes semanales los viernes, produciendo una lista limpia de todo lo que se debe a otros.

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

Preguntar en tu IA favorita

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

Documentación

Síntesis de Reuniones

Convierte notas de reuniones en conclusiones y elementos de acción — una reunión o una semana completa.

Tienes una transcripción, notas desordenadas, hilos de Slack o un lote de todo lo anterior. Esta habilidad extrae lo que importa: las decisiones, los elementos de acción y quién es responsable de qué, para que puedas compartirlo de inmediato y seguir adelante.


Plantilla de Prompt

Eres un PM experimentado que es implacablemente conciso. Tu trabajo es extraer señal del ruido.

Aquí están las notas, transcripciones o hilos a procesar:

<contexto>
$ARGUMENTS
</contexto>

> Si lo anterior está en blanco, pregunta al usuario: "{{PEGA UNA O MÁS TRANSCRIPCIONES DE REUNIONES, NOTAS, HILOS DE SLACK O DESCARGAS MENTALES AQUÍ. SI SON VARIAS, SEPÁRALAS CON UN DIVISOR CLARO O ETIQUETA CADA UNA.}}"

Detecta si se trata de una reunión única o de varias. Luego produce el resultado apropiado.

---

### Si es una reunión única:

## Decisiones Clave
Enumera las decisiones que se tomaron. Si algo se discutió pero NO se decidió, no lo pongas aquí — ponlo en Preguntas Abiertas.

## Conclusiones
Máximo 3-5 viñetas. Cada una debe ser una sola frase que capture algo importante que se dijo, acordó o surgió. Comienza con la idea, no con el hablante.

## Elementos de Acción
Formato de tabla. Cada elemento de acción debe tener un responsable (DRI). Si no se mencionó ningún responsable, márcalo como "NECESITA DRI".

| Elemento de Acción | DRI | Fecha Límite |
|--------------------|-----|--------------|
| [tarea específica y accionable] | [nombre] | [fecha o "PEND"] |

## Preguntas Abiertas
Cosas que se plantearon pero no se resolvieron. Necesitan seguimiento.

---

### Si son varias reuniones:

Primero, produce un resumen por reunión — para cada reunión, una línea con el nombre/tema de la reunión y 1-2 conclusiones clave. Mantenlo ajustado.

Luego produce una vista consolidada de TODAS las reuniones:

## Decisiones Clave (Todas las Reuniones)
Decisiones tomadas en todas las reuniones, agrupadas o etiquetadas por origen.

## Elementos de Acción Combinados
Una sola tabla que consolida los elementos de acción de cada reunión. Desduplica: si la misma acción surgió en dos reuniones, enumérala una vez. Incluye una columna "Origen" para que el DRI sepa de dónde vino.

| Elemento de Acción | DRI | Fecha Límite | Origen |
|--------------------|-----|--------------|--------|
| [tarea específica y accionable] | [nombre] | [fecha o "PEND"] | [nombre de la reunión] |

## Temas Transversales
Si surgen patrones en varias reuniones (el mismo tema sigue apareciendo, el mismo bloqueador mencionado en 3 llamadas, decisiones contradictorias), menciónalos. Máximo 2-3 viñetas.

## Preguntas Abiertas
Consolidadas de todas las reuniones. Desduplica.

---

Reglas:
- Sesgo hacia la brevedad. Si una conclusión puede ser una oración, no la hagas de dos.
- Los elementos de acción deben ser lo suficientemente específicos para que el DRI sepa exactamente qué hacer. "Dar seguimiento al precio" es malo. "Compartir los niveles de precios revisados con el equipo antes del viernes" es bueno.
- Si una reunión no tuvo decisiones claras, dilo — no las inventes.
- Si no puedes identificar un DRI para un elemento de acción, márcalo. Los elementos de acción sin dueño son la razón número 1 por la que las cosas no se hacen.
- No incluyas charlas triviales, desvíos ni discusiones que no llevaron a ninguna parte, a menos que hayan sacado a la luz una pregunta abierta importante.
- Al procesar varias reuniones, la tabla de elementos de acción combinados es el resultado más importante. Prioriza hacerla bien.

Consejos

  • Funciona con transcripciones sin procesar (Otter, Fireflies, Google Meet), hilos de Slack pegados o tus propias notas desordenadas.
  • Para procesamiento por lotes, pega todas tus reuniones con una etiqueta como "=== Sincronización de Producto ===" o "--- 1:1 con Sarah ---" entre ellas.
  • Si la transcripción es larga, el resultado más importante es la tabla de Elementos de Acción. Empieza por ahí.
  • Comparte el resultado directamente en Slack o en el documento de tu equipo — está formateado para copiar y pegar.
  • Para reuniones recurrentes (standups, sincronizaciones), ejecuta esto cada vez para construir un rastro ligero documental.
  • Ejecuta esto los viernes con todas las reuniones de la semana para producir una lista limpia de todo lo que debes a otras personas.

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