victor-shulga/account-management-skills

client-health-check

Scores every active client account green / yellow / red on 6 health criteria and outputs a health table + action plan for the reds.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/victor-shulga/account-management-skills --skill client-health-check

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Client Health Check

What it produces

A health table (one row per active client) + an action list for every yellow/red account, ready to paste into the client's task tracker or CRM.

The 6 criteria (score each 0–2)

#Criterion2 (green)1 (yellow)0 (red)
1Work volume trendgrowing or stableslight declineshrinking 2+ months
2Payment behavioron timeoccasional delaysoverdue / disputes
3Communication toneengaged, proactiveneutral, reactive onlycold, short, or silent
4Decision-maker accessregular contact with the economic buyeronly day-to-day contactsbuyer changed / unreachable
5Result visibilityclient sees and confirms valuevalue delivered but not shownclient questions the value
6Expansion signalsasks about more scopenonementions competitors / budget cuts

Total: 10–12 = green · 6–9 = yellow · 0–5 = red.

Process

  1. Ask for the list of active clients (or pull from CRM if an MCP connection exists).
  2. For each client, ask only for the facts the user can answer fast — or infer from

provided materials (email threads, invoices, meeting notes). Never guess a score: if a criterion is unknown, mark it ? and score conservatively (count as 1).

  1. Output the health table sorted worst-first.
  2. For every red and yellow account, add 1–3 concrete actions with an owner and a date:
  • red on tone/access → schedule a direct call with the decision-maker this week
  • red on result visibility → send a value recap: what was done, in their numbers
  • yellow on volume → check with delivery: is scope naturally ending or drifting away?
  1. Recommend the review rhythm: monthly rescoring, compare with last month's table.

Rules

  • Scores come from facts the user gives, not vibes. Note the evidence in the table.
  • A client can be red with perfect payments — silence is a stronger churn signal

than a late invoice.

  • The output ends with the single most urgent account and its next action.

Terms and plain-language output

<!-- glossary:start terms=account-health,churn,economic-buyer,day-to-day-owner --> Rules for every document a client or their team will read (review, roast, canvas, offer cards, instruction):

  1. Open with «Словник цього документа»: only the terms that actually appear in it, at most 10, each as «термін: що це простими словами». Like the definitions section of a contract.
  2. No internal codes or letter scales in the text (A/B/C, D L T E, BLEND numbers without words, Own/Shared/Generic, Z1.4, GATE 2.5, T1–T6). Write the meaning instead: «є цифра з клієнтом», not «A».
  3. Use the plain form from the table below. English stays only for tool names and for copy that ships in English (promises, hooks, subject lines). If the document is in another language, translate the plain form, never the internal term.
  4. Do not score what cannot exist yet. A block that depends on work not done (signal catalog, case studies, a previous step) gets «пропущено: спершу потрібно <що саме>», not a score.
  5. Every section of a review opens with one concrete action («до наступного дзвінка: …»), then at most five lines of why. No paragraph that only restates the framework.
Internal term (this skill)Write for the readerWhat it means
health score, green / yellow / redстан клієнта: усе добре · під наглядом · ризик втратипідсумок за кількома ознаками: обсяг робіт, оплати, тон, доступ до ОПР, видимість результату
churnвідтік клієнтівчастка клієнтів, які йдуть за місяць чи квартал.
economic buyer, sponsorтой, хто платитьлюдина, яка розпоряджається бюджетом і підписує; без доступу до неї угода або продовження під ризиком
day-to-day owner, championтой, хто працюватиме з вами щоднякерівник проєкту, BIM-менеджер, керівник розробки; йому важливе інше, ніж ОПР

<!-- glossary:end -->