escribir-un-caso-de-exito

escribir-un-caso-de-exito is a skill for Claude Code, Codex from gethouston/houston. It costs 65 tokens per session (1,331 once invoked), scanned A, original, MIT.

A Spanish-language writing workflow for turning verified customer information into a case study: a short story about a customer's challenge, the approach taken, and the results.

In plain words
What is it for?
Use it to write one customer's success story from source material stored in Airtable or Notion, or from material you provide directly.
Why use it?
It reduces the work of organizing interviews, testimonials, and notes into a usable sales or website story. Unverified numbers are marked for confirmation instead of being presented as facts.

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 to write one customer's success story from source material stored in Airtable or Notion, or from material you provide directly.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gethouston/houston/escribir-un-caso-de-exito
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 escribir-un-caso-de-exito
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 escribir-un-caso-de-exito

README.md
[![agentmods](https://agentmods.dev/badge/skills/gethouston/houston/escribir-un-caso-de-exito/github.svg)](https://agentmods.dev/skills/gethouston/houston/escribir-un-caso-de-exito)
Your own site
<a href="https://agentmods.dev/skills/gethouston/houston/escribir-un-caso-de-exito"><img src="https://agentmods.dev/badge/skills/gethouston/houston/escribir-un-caso-de-exito/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 escribir-un-caso-de-exito

Your own site · 80×15
<a href="https://agentmods.dev/skills/gethouston/houston/escribir-un-caso-de-exito"><img src="https://agentmods.dev/badge/skills/gethouston/houston/escribir-un-caso-de-exito.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,331 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.00065 $0.01331
Opus 5 $0.00032 $0.00665
Sonnet 5 $0.00013 $0.00266
Haiku 4.5 $0.00006 $0.00133

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

Security

Grade A, and why

escribir-un-caso-de-exito 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 13d 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/marketing/.agents/skills/escribir-un-caso-de-exito/SKILL.md · 76 lines

How it starts

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

Escribir un caso de éxito

Cuándo usarlo

  • Explícito: "redacta un caso de éxito para {customer}", "escribe la historia de {customer}", "convierte esta entrevista en un caso de éxito".
  • Implícito: después de que el agente de SDR/ventas marca a un cliente cerrado-ganado que está dispuesto a ser referencia, y el fundador lo aprueba.
  • Un caso de éxito por cliente por trimestre es una cadencia razonable.

Conexiones que necesito

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

  • Base de notas (Airtable, Notion): trae la entrevista, el testimonio o el registro de notas del cliente. Obligatoria (o puedes pegar el material fuente).

Si ninguna está conectada y no puedes pegar la entrevista, me detengo y te pido que conectes Airtable o Notion.

Información que necesito

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

  • Tu posicionamiento: Obligatorio. Por qué lo necesito: los casos de éxito tienen que reforzar el posicionamiento, no desviarse. Si falta, pregunto: "¿Quieres que redacte primero tu posicionamiento? Es una sola skill, toma unos cinco minutos."
  • Tu voz y CTA principal: Obligatorios. Por qué lo necesito: el CTA de cierre tiene que coincidir con lo que piden todas tus demás páginas. Si falta, pregunto: "Conecta tu bandeja de enviados para que pueda muestrear tu voz, y dime la única acción que un lector debería tomar después de leer el caso de éxito."
  • El cliente: Obligatorio. Si falta, pregunto: "¿Sobre qué cliente es este caso de éxito, nombre más una descripción de una línea?"
  • La entrevista, testimonio o notas: Obligatorios. Por qué lo necesito: no voy a fabricar citas ni métricas. Si falta, pregunto: "Sube la grabación de la entrevista, pega el testimonio, o indícame el registro del cliente en Airtable o Notion."
  • Números reales de antes/después: Obligatorios para un buen caso de éxito. Si falta, pregunto: "¿Qué cambio medible tuvo este cliente, y en qué periodo de tiempo? Si no lo tienes, sigo con TBD."

Read the full file on GitHub · 76 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. 13d ago First seen · 76 lines · 65 tokens per session scan A 2865ec547792

Subscribe to this mod's changes

escribir-un-caso-de-exito is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 1,331 once invoked, about $0.0003 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-08-30.

Related

Other skills, from other repositories

magazine-web-ppt

For marketing and gtm work: bind launches, campaigns, events, and brand plans to growth and pipeline outcomes. Built around the core query "annual-marketing-plan", with GTM strategy lead judgment, buyer-ready proof, and this outcome: approve launch plan, campaign budget, or GTM motion.

nexu-io/open-design · 67 tokens

html-ppt-zhangzara-coral

OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.

nexu-io/open-design · 55 tokens

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad…

coreyhaines31/marketingskills · 175 tokens

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives…

coreyhaines31/marketingskills · 220 tokens

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership…

coreyhaines31/marketingskills · 92 tokens

analytics

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this,"…

coreyhaines31/marketingskills · 152 tokens