cs-escalation-brief

cs-escalation-brief is a skill for Claude Code, Codex from mohitagw15856/pm-claude-skills. It costs 94 tokens per session (2,444 once invoked), scanned A, original, MIT.

A concise internal report about a serious customer problem, including the facts, timeline, customer request, likely cause, account risk, and proposed response.

In plain words
What is it for?
Use it when a customer threatens to cancel, a major support issue needs executive attention, or a team is preparing a customer-retention plan.
Why use it?
It gives leaders the context needed to make a quick decision without turning the report into an unstructured complaint. It also makes ownership and next steps explicit.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when a customer threatens to cancel, a major support issue needs executive attention, or a team is preparing a customer-retention plan.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mohitagw15856/pm-claude-skills/cs-escalation-brief
About the project

PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.

mohitagw15856/pm-claude-skills · 1,449 stars · on GitHub · mohitagw15856.github.io

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 mohitagw15856/pm-claude-skills --skill cs-escalation-brief
Clone the repo
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills

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 cs-escalation-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/cs-escalation-brief/github.svg)](https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/cs-escalation-brief)
Your own site
<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/cs-escalation-brief"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/cs-escalation-brief/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 cs-escalation-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/cs-escalation-brief"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/cs-escalation-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,444 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.
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.00094 $0.02444
Opus 5.5 $0.00038 $0.00978
Sonnet 5.5 $0.00019 $0.00489
Haiku 4.5 $0.00009 $0.00244

Measured 2d ago against content hash 907924c3f3be, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cs-escalation-brief 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 2d 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.

i18n/es/skills/cs-escalation-brief/SKILL.md · 211 lines

How it starts

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

Skill de Informe de Escalada de Cliente

Produce un informe de escalada claro y conciso que proporcione a los stakeholders internos — VP de CS, CCO, liderazgo de producto, o el CEO — todo lo que necesitan para comprender la situación, tomar decisiones y actuar rápidamente.

Un buen informe de escalada no es una queja. Es un documento profesional que expone los hechos, asigna responsabilidad con honestidad y propone un plan de resolución específico.

Inputs Requeridos

Solicita estos si no se proporcionan ya:

  • Nombre de la cuenta, tier y ARR
  • Nombre del CSM y propietario de la cuenta
  • Naturaleza de la escalada — qué pasó, qué dice el cliente
  • Cronología de eventos que llevaron a la escalada
  • Contacto del cliente que escaló (nombre, rol, nivel de influencia)
  • Qué quiere el cliente — su solicitud explícita
  • Cuál creemos que es la causa raíz
  • Qué se ha hecho ya para abordar la situación
  • Fecha de renovación y evaluación actual del riesgo de renovación

Niveles de Escalada

Calibra la urgencia y la audiencia según el nivel de escalada:

Nivel Desencadenante Audiencia Tiempo de respuesta
L1 — Riesgo de Cuenta Cliente expresando insatisfacción; renovación en riesgo CSM + CS Manager 24 horas
L2 — Escalada Ejecutiva Cliente escalado a su ejecutivo; solicitando implicación de ejecutivo del proveedor VP CS + Account Exec 4 horas
L3 — Riesgo de Churn Cliente ha emitido aviso o está en conversación activa de churn CCO / CEO + Revenue leadership 1 hora
L4 — Riesgo Público Cliente amenazando con escalada pública, legal o prensa CCO / Legal / Comms Inmediato

Formato de Output


Informe de Escalada: [Nombre de Cuenta]

Nivel de escalada: L[1/2/3/4] — [Etiqueta] Fecha de escalada: [Fecha] Escalada por: [nombre del CSM] Propietario de escalada: [Nombre del ejecutivo o stakeholder sénior que ahora lidera la respuesta]


Cuenta de un Vistazo

Read the full file on GitHub · 211 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. 2d ago First seen · 211 lines · 94 tokens per session scan A 907924c3f3be

Subscribe to this mod's changes

cs-escalation-brief is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 94 tokens to every session and 2,444 once invoked, about $0.0004 per session on Opus 5.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-10-12.

Related

Other skills, from other repositories

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

systematic-debugging

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

obra/superpowers · 21 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