跳到正文
cccskills
免费在 GitHub 公开

activation

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(2)

  • SKILL.md3.4 KB
  • references/sources.md1.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Activation

Acquisition spend is wasted downstream of a weak activation. This is usually the cheapest place to improve revenue and the least worked on.

Define the activation moment

Name the specific thing a new user does that predicts they will stay — not "logged in twice," but the action that delivers the value they came for. Find it in the data: compare what retained users did in week one against what churned users did.

Everything in onboarding exists to get people to that moment faster. Without it defined, onboarding becomes a feature tour.

Signup

Every field costs conversion, and each one must earn its place. Ask for what is needed to deliver value now; collect the rest later, in context, when the reason is obvious.

  • Defer email verification past first value where the product allows it.
  • Never ask for payment details before value is delivered unless the model requires it.
  • Show progress on multi-step flows, and let people finish later without losing work.
  • Errors inline and specific. A form that rejects on submit without saying which field is where people leave.

Onboarding

The goal is the first real outcome, not a completed tour.

  • Use their data, not sample data. The moment someone sees their own information in the product is the moment it becomes real.
  • One action at a time, each visibly advancing toward the outcome.
  • Skippable, resumable, and repeatable. Forced linear onboarding fails everyone whose situation differs from the assumed one.
  • Empty states do the teaching. They are the most-seen screens in a new account and usually the least designed.

Checklists work when the items lead to real value and the list can be dismissed. They fail when they are busywork.

Diagnosing

Instrument each step and find the largest drop. Then watch session recordings of people who dropped there — the quantitative data says where, and only observation says why.

Common causes, in rough order: asked for too much too early, value not visible before effort required, an empty product with no path out of it, and a required integration nobody has permissions for.

Measuring

Percentage reaching the activation moment, and time to reach it. Signup conversion alone will happily improve while activation falls.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Pick an activation moment because it is easy to measure. It has to be the point where the user gets the value they came for.
  • Add a step to onboarding without removing one. Every screen between signup and value costs you users.
  • Ask at signup for anything you do not need to deliver the first result. Collect the rest later, in context.
  • Count signups as activation. A user who never reached the value moment did not activate.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20702026年10月19日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20702026年10月19日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20702026年10月19日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20702026年10月19日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20702026年10月19日 更新

Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.

中文简介正在准备中。当前显示原文说明。

cbrock84/headcount20702026年10月19日 更新

查看 cbrock84 的全部技能

报告此技能的问题