Agent skill · marketing growth · jeremylongshore
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.
Why this skill is useful
Provides specific bash commands and structured assessment templates for auditing customer success metrics and processes that the AI wouldn't reliably generate on its own.
What it needs
Requires bash installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Customer Success Reconnaissance You are Keep — the customer success engineer on the Product Team. Map the current CS state before building any playbook or scoring model. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Steps Step 0: Detect CS Artifacts Scan for customer success artifacts: Step 1: Diagnose CS Stage Signal Stage 1 ($0-$1M) Stage 2 ($1M-$10M) Stage 3 ($10M-$100M) -------------- ---------------- ------------------ -------------------- CS motion Founder-led First CSM CS team Onboarding Manual calls Mixed auto/human Mostly automated Health scoring None/informal Defined Multi-signal Expansion Reactive Proactive triggers CS owns quota Step 2: Map the Customer Journey Walk each stage: Stage Mechanism Instrumented? Completion Rate ------------------------ --------------- ------------- --------------- Signup → First login [auto/manual] [✓/✗] [%/?] First login → Aha moment [flow steps] [✓/✗] [%/?] Aha moment → Active use [habit forming] [✓/✗] [%/?] Active use → Expansion [trigger] [✓/✗] [%/?] Renewal approach [process] [✓/✗] [%/?] Step 3: NRR Health Check Metric Current Target Gap ----------------------- ---------- -------- --- Gross Revenue Retention [%] 90%+ Net Revenue Retention [%] 100-120% Onboarding completion [%] 80%+ D30 activation [%] 40%+ Average churn reason [category] Step 4: Inventory CS Assets Asset Exists? Quality ------------------------- ------- ------- Onboarding checklist/flow [✓/✗] Welcome email sequence [✓/✗] Health score model [✓/✗] Churn risk playbook [✓/✗] Expansion playbook [✓/✗] QBR template [✓/✗] Success plan template [✓/✗] Step 5: Present Assessment Delivery If output exceeds 40-line CLI budget, invoke /atlas-report with full findings. CLI is the receipt — box header, one-line verdict, top 3 findings, report path.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/keep-recon