account-health-watch

Rank usage-health and support-signal account watch lists with cited evidence per row.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill account-health-watch-jyeswak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: account-health-watch
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/account-health-watch
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill account-health-watch-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Account health reviews often rely on gut feel or a single blended score that hides why an account is at risk. This Skill turns raw product usage and support signals into two ranked watch lists where every row carries named, citable evidence, so owners can see exactly which accounts need attention and why. ## Core Features & Use Cases - Dual ranked watch lists: Builds separate usage-health and support-signal rankings over a stated window, then joins them to surface accounts showing both declining usage and rising support friction. - Evidence-backed ranking: Every ranked row includes a stable account id, a one-line reason, and 2-4 cited evidence items (metric, window, value or delta, source); rows that cannot meet that bar drop to an unranked watch-closely note. - Run-over-run diffing: Compares against the prior watch lists to report new entries, exits, and rank moves of three or more places with the signal that caused each move. - Use Case: A customer success lead preparing a weekly review asks which accounts are quietly declining; the Skill reads usage and support data for the trailing 14 days and returns two dated, ranked lists plus the single account that most needs a decision. ## Quick Start Ask the assistant to run an account health review over the last 14 days using the current account roster, usage metrics, and support ticket data, and produce the two ranked watch lists with evidence per row.

Frequently Asked Questions about account-health-watch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify which customer accounts are at risk?▼

Run an account health review that scores each account on direction of usage (growing, flat, declining, dormant) from at least two usage signals, plus support load over the same window. Accounts appearing on both lists, declining usage plus rising support friction, rank highest risk.

How to build an account health watch list with evidence?▼

Fix a review window and roster first, then rank each list by risk with every row carrying a stable account id, a one-line reason, and 2-4 cited evidence items including metric, window, value or delta, and source. Rows missing evidence drop to an unranked watch-closely note.

What inputs does an account health review need?▼

It needs a roster with stable account ids, per-account usage signals (logins, active days, feature touches, API calls) over a stated window, support signals (ticket counts, reopens, escalations) over the same window, and optionally the prior run's watch lists for movement diffing.

Can this skill contact at-risk accounts or change their plans?▼

No. It is strictly read-only: it never messages accounts, opens or closes tickets, or changes plans or settings. Any suggested outreach is a draft that requires the owner's explicit approval of that exact message before sending.

Why not use a single blended account health score?▼

A blended score hides the method and the reasons behind a rank. Keeping usage-health and support-signal lists separate, with every rank citable to named signals, lets owners verify why an account is flagged instead of trusting an opaque number.