preparar-una-reunion

preparar-una-reunion is a skill for Claude Code, Codex from gethouston/houston. It costs 88 tokens per session (2,059 once invoked), scanned A, original, MIT.

A meeting-preparation brief creates either a one-page plan for an upcoming sales call or a quarterly review of an existing customer account. The review covers delivered results, usage trends, open requests, risks, and the next-quarter goal.

In plain words
What is it for?
Use it before discovery calls, demos, follow-ups, advanced sales conversations, or customer renewal reviews.
Why use it?
It replaces generic preparation with questions, objections, and discussion points tied to the specific deal or account.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it before discovery calls, demos, follow-ups, advanced sales conversations, or customer renewal reviews.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gethouston/houston/preparar-una-reunion
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add gethouston/houston --skill preparar-una-reunion
Clone the repo
git clone --depth 1 https://github.com/gethouston/houston

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for preparar-una-reunion

README.md
[![agentmods](https://agentmods.dev/badge/skills/gethouston/houston/preparar-una-reunion/github.svg)](https://agentmods.dev/skills/gethouston/houston/preparar-una-reunion)
Your own site
<a href="https://agentmods.dev/skills/gethouston/houston/preparar-una-reunion"><img src="https://agentmods.dev/badge/skills/gethouston/houston/preparar-una-reunion/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for preparar-una-reunion

Your own site · 80×15
<a href="https://agentmods.dev/skills/gethouston/houston/preparar-una-reunion"><img src="https://agentmods.dev/badge/skills/gethouston/houston/preparar-una-reunion.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,059 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00088 $0.02059
Opus 5 $0.00044 $0.01030
Sonnet 5 $0.00018 $0.00412
Haiku 4.5 $0.00009 $0.00206

Measured 9d ago against content hash 8573942d5ac6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

preparar-una-reunion scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

store/agents-i18n/es/sales/.agents/skills/preparar-una-reunion/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Preparar una reunión

Una sola skill, dos formatos de preparación de reunión. El parámetro type define la estructura. Comparten el anclaje al playbook y la regla de "sin plantillas genéricas".

Parámetro: type

  • call: hoja de una página previa a la llamada (descubrimiento / demo / seguimiento / etapa avanzada). Objetivo, asistentes, preguntas, objeciones, criterios de salida.
  • account-review: paquete trimestral de revisión de cuenta para un cliente existente. Resultados, tendencia de uso, pedidos abiertos, riesgos, meta del próximo trimestre.

Si el pedido del usuario nombra el tipo en lenguaje simple ("preparación de llamada", "revisión de cuenta"), lo infiero. Si no, hago UNA pregunta que nombre las 2 opciones.

Cuándo usarla

  • Disparadores explícitos en la descripción.
  • Implícito: brief-me-for-today detecta una reunión inminente sin preparación y encadena aquí con type=call; la rutina de retención de clientes encadena aquí con type=account-review antes de la ventana de renovación.

Conexiones que necesito

Todo el trabajo externo lo hago a través de Composio. Antes de ejecutar esta skill, verifico que las categorías de abajo estén conectadas. Si falta alguna, digo cuál es, te pido que la conectes desde la pestaña de Integraciones, y me detengo.

  • Calendario: obtengo la hora de la reunión y los asistentes. Obligatorio.
  • CRM: leo el registro del negocio o del cliente (etapa, dueño, contactos). Obligatorio.
  • Reuniones: obtengo transcripciones de llamadas previas para type=call. Opcional.
  • Redes sociales: enriquezco los perfiles de los asistentes vía LinkedIn. Opcional.
  • Facturación: obtengo el estado de facturación para type=account-review. Opcional.

Si el calendario o el CRM no están conectados, me detengo y te pido que los conectes primero. La preparación se ancla en la reunión y en el negocio.

Información que necesito

Primero leo tu contexto de ventas. Por cada campo obligatorio que falte, hago UNA pregunta en lenguaje sencillo (mejor modalidad: app conectada > archivo > URL > texto pegado) y espero.

Read the full file on GitHub · 128 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 128 lines · 88 tokens per session scan A 8573942d5ac6

Subscribe to this mod's changes

preparar-una-reunion is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 2,059 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

magpie-security-issue-import-from-md

Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.

apache/magpie · 73 tokens