本文へ移動
cccskills
無料GitHub で公開

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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:

# Onboarding flows
find . -name "*.tsx" -o -name "*.jsx" -o -name "*.vue" 2>/dev/null | xargs grep -l "onboard\|welcome\|setup\|getting.started\|checklist\|tour" 2>/dev/null | head -10

# Email lifecycle
find . -name "*.ts" -o -name "*.json" -o -name "*.md" 2>/dev/null | xargs grep -l "lifecycle\|drip\|nurture\|activation.email\|day.1\|day.7\|welcome.email" 2>/dev/null | head -10

# Health and metrics
find . -name "*.md" -o -name "*.ts" 2>/dev/null | xargs grep -l "health.score\|churn\|NRR\|MRR\|retention\|cohort\|CSAT\|NPS" 2>/dev/null | head -10

# CS docs
find . -name "*.md" 2>/dev/null | xargs grep -l "customer.success\|onboarding\|expansion\|renewal\|QBR\|success.plan" 2>/dev/null | head -10

Step 1: Diagnose CS Stage

SignalStage 1 ($0-$1M)Stage 2 ($1M-$10M)Stage 3 ($10M-$100M)
CS motionFounder-ledFirst CSMCS team
OnboardingManual callsMixed auto/humanMostly automated
Health scoringNone/informalDefinedMulti-signal
ExpansionReactiveProactive triggersCS owns quota

Step 2: Map the Customer Journey

Walk each stage:

StageMechanismInstrumented?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

MetricCurrentTargetGap
Gross Revenue Retention[%]90%+
Net Revenue Retention[%]100-120%
Onboarding completion[%]80%+
D30 activation[%]40%+
Average churn reason[category]

Step 4: Inventory CS Assets

AssetExists?Quality
Onboarding checklist/flow[✓/✗]
Welcome email sequence[✓/✗]
Health score model[✓/✗]
Churn risk playbook[✓/✗]
Expansion playbook[✓/✗]
QBR template[✓/✗]
Success plan template[✓/✗]

Step 5: Present Assessment

## Customer Success Reconnaissance

**Stage:** [1/2/3] | **NRR:** [%] | **Primary churn reason:** [category]
**Onboarding completion:** [%] | **Aha moment defined:** [✓/✗]
**Biggest CS constraint:** [single bottleneck]

### Journey State
[table from Step 2, compressed]

### Critical Gaps
- [Gap 1]
- [Gap 2]
- [Gap 3]

### Highest Leverage Action
[Single most important CS improvement this week]

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

apex

無料

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

apex-gate

無料

Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

apex-plan

無料

Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

tonone-ai のスキルをすべて見る

このスキルの問題を報告する