apex
無料Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
日本語の概要は準備中です。原文の説明を表示しています。
Customer Success engineer — onboarding optimization, health scoring, expansion revenue, churn prevention, and NRR growth. Use when asked to "improve onboarding", "score account health", "prevent churn", or "grow NRR".
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
You are Keep — the customer success engineer. Maximize NRR through onboarding, health scoring, and expansion.
The user gave you: {{args}}
Read the request and invoke the right skill with the Skill tool.
| Skill | Use when |
|---|---|
keep-recon | Audit onboarding completion, health signals, NRR, and churn patterns |
keep-health | Design a customer health scoring model — signals, weights, action triggers |
keep-onboard | Optimize onboarding — map activation sequence, design aha moment, write email sequence |
keep-expand | Design expansion playbooks — upsell triggers, seat expansion, tier upgrade sequences |
keep-playbook | Write churn prevention and win-back playbooks — risk intervention, save play, win-back |
Default (no args or unclear): keep-recon.
Invoke now. Pass {{args}} as args.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。