escrever-um-case-de-sucesso

escrever-um-case-de-sucesso is a skill for Claude Code, Codex from gethouston/houston. It costs 63 tokens per session (1,348 once invoked), scanned A, original, MIT.

A case-study drafting tool that turns a customer’s experience into a story about the challenge, approach, and results. Any result it cannot verify is marked for confirmation.

In plain words
What is it for?
Use it to turn a customer interview, testimonial, or notes into a case study for a website or sales material. It requires source material and company positioning.
Why use it?
It gives sales and website teams a structured customer story while separating verified facts from details that still need checking. This helps avoid unsupported claims.

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 turn a customer interview, testimonial, or notes into a case study for a website or sales material. It requires source material and company positioning.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gethouston/houston/escrever-um-case-de-sucesso
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 escrever-um-case-de-sucesso
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 escrever-um-case-de-sucesso

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/gethouston/houston/escrever-um-case-de-sucesso"><img src="https://agentmods.dev/badge/skills/gethouston/houston/escrever-um-case-de-sucesso.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,348 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.00063 $0.01348
Opus 5 $0.00032 $0.00674
Sonnet 5 $0.00013 $0.00270
Haiku 4.5 $0.00006 $0.00135

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

Security

Grade A, and why

escrever-um-case-de-sucesso 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/pt/marketing/.agents/skills/escrever-um-case-de-sucesso/SKILL.md · 92 lines

How it starts

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

Escrever um case de sucesso

Quando usar

  • Explícito: "redija um case de sucesso do {cliente}", "escreva a história do {cliente}", "transforme esta entrevista em um case de sucesso".
  • Implícito: depois que o agente de SDR / vendas sinaliza um cliente fechado disposto a servir de referência + o fundador aprova.
  • Um case de sucesso por cliente por trimestre = cadência razoável.

Conexões que eu preciso

Executo trabalho externo através do Composio. Antes de esta skill rodar, verifico se as categorias abaixo estão conectadas. Faltando → nomeio a categoria, peço para você conectá-la na aba Integrações, paro.

  • Banco de notas (Airtable, Notion) - puxa a entrevista do cliente, o depoimento ou o registro de notas. Obrigatório (ou você cola o material de origem).

Se nenhum dos dois estiver conectado e você não puder colar a entrevista, eu paro e peço para você conectar o Airtable ou o Notion.

Informações que eu preciso

Leio seu contexto de marketing primeiro. Para cada campo obrigatório que estiver faltando, faço UMA pergunta em linguagem simples (melhor modalidade: app conectado > envio de arquivo > URL > colar) e espero.

  • Seu posicionamento - Obrigatório. Por que preciso: cases de sucesso têm que reforçar o posicionamento, não desviar dele. Se faltar, pergunto: "Quer que eu redija seu posicionamento primeiro? É uma skill só, leva uns cinco minutos."
  • Sua voz e CTA principal - Obrigatório. Por que preciso: o CTA de fechamento combina com o que todas as outras páginas pedem. Se faltar, pergunto: "Conecte sua caixa de enviados para eu amostrar sua voz, e me diga a única ação que o leitor deve tomar depois de ler o case de sucesso."
  • O cliente - Obrigatório. Se faltar, pergunto: "De qual cliente é este case de sucesso, nome mais uma descrição de uma linha?"
  • A entrevista, o depoimento ou as notas - Obrigatório. Por que preciso: não vou fabricar citações nem métricas. Se faltar, pergunto: "Envie a gravação da entrevista, cole o depoimento, ou me aponte para o registro do cliente no Airtable ou no Notion."
  • Números reais de antes / depois - Obrigatório para um case de sucesso forte. Se faltar, pergunto: "Que mudança mensurável esse cliente viu, e em qual período? Se você não tiver, eu sigo com TBD."

Read the full file on GitHub · 92 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 · 92 lines · 63 tokens per session scan A a4a9aeeda11e

Subscribe to this mod's changes

escrever-um-case-de-sucesso is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,348 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-09-03.

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