client-health-radar — Claude Code skill for client health
The client-health-radar skill reviews Littlebird evidence for churn risk, scope creep, and margin pressure. Use it for an account check or a weekly client review.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install littlebird-toolkit@wasp-nestWhat client-health-radar does
client-health-radar gathers client evidence from Littlebird meetings, messages, and captured data. Its report separates observed facts from inferences, external information, and unknowns. Rather than assigning an overall health score, it gives dated signals the account owner can check.
The skill requires Littlebird MCP on a Power or Pro plan. It checks which tools are available and stops if Littlebird tools cannot be accessed. Without the MCP connection, the analysis will not run. A weekly observer can be set for Mondays at 07:30; the subscription plan is checked before creating it.
What it helps with
- spot signs that a client may churn
- catch work expanding beyond the agreed scope
- find pressure on an account’s margin
- prepare a weekly account review
Example prompts for the agent
- Check whether this client shows signs of churn.
- Look for scope growth and pressure on this account’s margin.
- Set up a weekly review of client health.
How to install client-health-radar
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install littlebird-toolkit@wasp-nestThis installs the whole littlebird-toolkit plugin with all its skills
2Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill client-health-radar -a claude-code3Manually: put the files in place
~/.claude/skills/client-health-radar/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/client-health-radar/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill client-health-radar -a codex2Manually: put the files in place
.agents/skills/client-health-radar/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill client-health-radar -a cursor2Manually: put the files in place
.cursor/skills/client-health-radar/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/littlebird-toolkit/skills/client-health-radar2Manually: put the files in place
.github/skills/client-health-radar/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill client-health-radar -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/littlebird-toolkit/skills/client-health-radarManually: put the files in place
.devin/skills/client-health-radar/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about client-health-radar
How do I install client-health-radar in Claude Code?
Add the marketplace with /plugin marketplace add legioncodeinc/vibe-coding-tools, then install the plugin with /plugin install littlebird-toolkit@wasp-nest.
What does client-health-radar do?
It reviews Littlebird evidence for churn, scope growth, and margin pressure. Its findings are tied to dated observations rather than a single health score.
What does client-health-radar need to run?
It needs Littlebird MCP connected on a Power or Pro plan. If Littlebird tools are unavailable, the skill stops instead of attempting an analysis.