analizar-mis-tickets

analizar-mis-tickets is a skill for Claude Code, Codex from gethouston/houston. It costs 87 tokens per session (1,651 once invoked), scanned A, original, MIT.

A customer-feedback analysis that reviews support tickets and groups what people are saying. It covers complaints, feature requests, mismatches between your promises and the product, and wording customers use themselves.

In plain words
What is it for?
Use it to identify product requests, customer pain points, positioning problems, and phrases for landing pages or investor reports.
Why use it?
It turns scattered support conversations into recurring themes, so product and marketing decisions are based on customer evidence instead of isolated messages.

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 identify product requests, customer pain points, positioning problems, and phrases for landing pages or investor reports.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gethouston/houston/analizar-mis-tickets
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 analizar-mis-tickets
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 analizar-mis-tickets

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/gethouston/houston/analizar-mis-tickets"><img src="https://agentmods.dev/badge/skills/gethouston/houston/analizar-mis-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,651 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.00087 $0.01651
Opus 5 $0.00044 $0.00826
Sonnet 5 $0.00017 $0.00330
Haiku 4.5 $0.00009 $0.00165

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

Security

Grade A, and why

analizar-mis-tickets 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/support/.agents/skills/analizar-mis-tickets/SKILL.md · 121 lines

How it starts

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

Analizar mis tickets

Distinta de flag-a-signal signal=repeat-question. Esa skill genera candidatos a vacíos en la base de conocimiento (vista operativa). Esta genera un reporte estratégico de voz del cliente (vista de producto/posicionamiento). Mismos datos de origen, distinto consumidor.

Cuándo usarla

  • "analiza los últimos {N} tickets en busca de temas."
  • "¿qué están pidiendo los clientes?"
  • Antes de escribir el roadmap, una actualización de landing page, o un reporte para inversionistas.
  • Solicitudes puntuales de investigación estratégica.

Conexiones que necesito

Hago el trabajo externo a través de Composio. Antes de ejecutar esta skill, verifico que las categorías de abajo estén conectadas. Si falta alguna → nombro la categoría, te pido que la conectes desde la pestaña de Integraciones, y me detengo.

  • Bandeja de entrada (Gmail) - fuente de los hilos de clientes cuando conversations.json no cubre el periodo. Opcional si los datos locales están al día.
  • Help-desk de soporte (Intercom / Zendesk / Help Scout) - fuente alterna de tickets. Opcional.

Si ninguna está conectada y el índice local de conversaciones es escaso, me detengo y te pido que conectes tu bandeja de entrada o tu help-desk para tener suficiente señal.

Información que necesito

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

  • Posicionamiento actual - Obligatorio. Por qué lo necesito: detecto fricción comparando el lenguaje real de los clientes contra lo que tú afirmas. Si falta, pregunto: "¿Cómo describes hoy lo que hace el producto? Comparte la URL de tu página principal o un párrafo."
  • Ventana de tiempo - Obligatorio. Por qué lo necesito: 30 días es el valor por defecto, pero lo amplío o reduzco si quieres. Si falta, pregunto: "¿Qué tan atrás debo mirar? ¿Últimos 30 días, el último trimestre, desde el lanzamiento?"
  • Filtro de segmento - Opcional. Por qué lo necesito: me permite agrupar por tipo de cliente en vez de mezclar todo. Si no lo tienes, sigo con TBD y muestro grupos mixtos.

Read the full file on GitHub · 121 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 · 121 lines · 87 tokens per session scan A ee009c0012cf

Subscribe to this mod's changes

analizar-mis-tickets is a skill published in the GitHub repository gethouston/houston (113 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 1,651 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens