使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/victor-shulga/account-management-skills --skill client-health-check開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
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)
| # | Criterion | 2 (green) | 1 (yellow) | 0 (red) |
|---|---|---|---|---|
| 1 | Work volume trend | growing or stable | slight decline | shrinking 2+ months |
| 2 | Payment behavior | on time | occasional delays | overdue / disputes |
| 3 | Communication tone | engaged, proactive | neutral, reactive only | cold, short, or silent |
| 4 | Decision-maker access | regular contact with the economic buyer | only day-to-day contacts | buyer changed / unreachable |
| 5 | Result visibility | client sees and confirms value | value delivered but not shown | client questions the value |
| 6 | Expansion signals | asks about more scope | none | mentions competitors / budget cuts |
Total: 10–12 = green · 6–9 = yellow · 0–5 = red.
Process
- Ask for the list of active clients (or pull from CRM if an MCP connection exists).
- 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).
- Output the health table sorted worst-first.
- 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?
- 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):
- Open with «Словник цього документа»: only the terms that actually appear in it, at most 10, each as «термін: що це простими словами». Like the definitions section of a contract.
- 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».
- 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.
- 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.
- 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 reader | What it means |
|---|---|---|
| health score, green / yellow / red | стан клієнта: усе добре · під наглядом · ризик втрати | підсумок за кількома ознаками: обсяг робіт, оплати, тон, доступ до ОПР, видимість результату |
| churn | відтік клієнтів | частка клієнтів, які йдуть за місяць чи квартал. |
| economic buyer, sponsor | той, хто платить | людина, яка розпоряджається бюджетом і підписує; без доступу до неї угода або продовження під ризиком |
| day-to-day owner, champion | той, хто працюватиме з вами щодня | керівник проєкту, BIM-менеджер, керівник розробки; йому важливе інше, ніж ОПР |
<!-- glossary:end -->