Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

account-health-review

Estrellas1

Forks0

Actualizado19 de julio de 2026 a las 00:57

Use when you need to assess whether a client account is healthy, at risk, or slipping — before renewal, after a rough patch, or on a regular cadence — and decide what to do about it.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

ever-works

ever-works/orgs

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Especialistas en gestión de proyectosOperaciones empresariales y financieras·SOC 13-1082

SKILL.md

readonly

name	account-health-review
description	Use when you need to assess whether a client account is healthy, at risk, or slipping — before renewal, after a rough patch, or on a regular cadence — and decide what to do about it.

Account Health Review

Run this on a fixed cadence for every live account, and again after any bump — a missed deadline, a tense call, a delayed invoice. Its purpose is to catch a declining relationship while it can still be repaired, not to explain a non-renewal after it lands.

Steps

Pull the facts first. Scope status, budget spent versus scoped, deadlines hit versus missed, open Tasks, and time since the last real conversation. Numbers before feelings.
Score three dimensions. Rate each green / yellow / red, with one line of evidence: Delivery (are we shipping what we promised, on time), Commercial (is the account profitable and paid up), Relationship (does the client trust us and answer our calls).
Name the trend, not just the state. A green account sliding toward yellow matters more than a stable yellow. Compare against the last review.
Find the one thing. Identify the single biggest risk to renewal. Resist listing ten; fix the one that moves the others.
Write the action. One owner, one date, one concrete step for the top risk — and escalate to the account director now if it is commercial or above your line.
Decide the client conversation. Does this need a proactive call this week, or is a status note enough? Say which, and who makes it.

Quality bar

Every rating carries evidence a colleague could verify.
The trend is stated explicitly, not implied.
The top risk has exactly one owner and one dated action — not a committee.
Nothing red is left without either an action or an escalation.

Output format

ACCOUNT: <name>   REVIEW DATE: <date>   PRIOR: <green/yellow/red>
DELIVERY:      <green/yellow/red> — <evidence>
COMMERCIAL:    <green/yellow/red> — <evidence>
RELATIONSHIP:  <green/yellow/red> — <evidence>
TREND: <improving / stable / declining> vs last review
TOP RISK: <one sentence>
ACTION: <step> — owner <name>, by <date>
CLIENT CONTACT: <proactive call | status note> — <who>

Más de este repositorio

mismo repositorio

campaign-brief

ever-works/orgs

Use when a client request is ready to become production work and you must brief creative or media — turning a vague ask into an objective, an audience, and constraints the team can build against.

2026-07-191

client-proposal-rfp

ever-works/orgs

Use when responding to an RFP or writing a new-business proposal — to decide whether to pursue it, shape the offer, and produce a document a client can say yes to.

2026-07-191

quarterly-business-review

ever-works/orgs

Use when preparing the quarterly review a client account faces — to report results against the objective honestly, read what worked, and set what the next quarter buys.

2026-07-191

scope-and-sow

ever-works/orgs

Use when you need to write or change a statement of work — turning an agreed offer into a scope, deliverables, price, and terms that both protect the client and defend the agency's margin.

2026-07-191

comp-band-review

ever-works/orgs

Use when reviewing compensation for a role, a team, or the whole population — checks where people sit against defensible bands, finds equity gaps, and produces a ranked, costed set of adjustments.

2026-07-191

employee-faq

ever-works/orgs

Use when building or maintaining the self-serve answers employees reach for — turns the questions people actually ask into clear, sourced FAQ entries that deflect repeat questions and stay consistent with policy.

2026-07-191

Account Health Review

Steps

Pull the facts first. Scope status, budget spent versus scoped, deadlines hit versus missed, open Tasks, and time since the last real conversation. Numbers before feelings.

Score three dimensions. Rate each green / yellow / red, with one line of evidence: Delivery (are we shipping what we promised, on time), Commercial (is the account profitable and paid up), Relationship (does the client trust us and answer our calls).

Name the trend, not just the state. A green account sliding toward yellow matters more than a stable yellow. Compare against the last review.

Find the one thing. Identify the single biggest risk to renewal. Resist listing ten; fix the one that moves the others.

Write the action. One owner, one date, one concrete step for the top risk — and escalate to the account director now if it is commercial or above your line.

Decide the client conversation. Does this need a proactive call this week, or is a status note enough? Say which, and who makes it.

Quality bar

Every rating carries evidence a colleague could verify.

The trend is stated explicitly, not implied.

The top risk has exactly one owner and one dated action — not a committee.

Nothing red is left without either an action or an escalation.

Output format

ACCOUNT: <name> REVIEW DATE: <date> PRIOR: <green/yellow/red> DELIVERY: <green/yellow/red> — <evidence> COMMERCIAL: <green/yellow/red> — <evidence> RELATIONSHIP: <green/yellow/red> — <evidence> TREND: <improving / stable / declining> vs last review TOP RISK: <one sentence> ACTION: <step> — owner <name>, by <date> CLIENT CONTACT: <proactive call | status note> — <who>