Keep Recon
Customer success reconnaissance — audit current onboarding completion, health signals, NRR, churn patterns, and CS motion. Use when asked to "audit our customer success", "why are customers churning", "what's our NRR", or before designing any CS playbook.
Works with: Claude Code (native)
native: this artifact type is that client's own format
Install (Claude Code):
/plugin marketplace add tonone-ai/tonone
/plugin install keep-recon@tonone-ai- tashan score: 40.0
- Adoption: 1 repos
- Upkeep: 81.0
- Freshness: 97.0
- Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
- Health: active
- Contributors: 2
- License: MIT
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
You searched for one. Check the rest of your stack:
npx tashan-cli doctorReads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.
Keep Recon scores 40 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down — and tells you the day it moves.
- Every score since we started measuring, for any capability
- The named replacement when something you run is dying — not just that it is
tashan doctorover the config you already have, on your machine
Start a 7-day trial › Everything measured on this page stays free.
Show your score
source ↗ · plugin:tonone-ai/tonone/keep-recon
Everything on this page is public evidence and free. What it cannot know is whether you run this — npx tashan-cli doctor reads your own config and names what is wrong in it, also free. tashan Pro tells you the day any of it changes.
Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›
Measured 2026-08-14 · scorer s5 · how · something wrong here?