Claude Skill

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

LLM Mart · 0 points · 16 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download cbrock84-headcount-plugins_revenue_skills_activation-98d1c17.zip · 2 KB
Part of cbrock84/headcount — 160 skills

Install

skills CLI npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/revenue/skills/activation
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install cbrock84-headcount@llmmart
Git git clone https://github.com/cbrock84/headcount.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole cbrock84/headcount collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.
Files (headcount)
  • references
    • sources.md 1.5 KB
      # Sources — `revenue:activation`
      
      <!-- Generated by scripts/build-sources.py from sources/*.toml. Do not edit. -->
      
      Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce.
      
      ## 15 U.S.C. 8403 — Restore Online Shoppers' Confidence Act
      
      US Congress, via the Office of the Law Revision Counsel · US · public domain (US government) — quote freely
      
      <https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title15-section8403&num=0&edition=prelim>
      
      **Authoritative for:** Whether an online auto-renewal offer is lawful — clear disclosure of material terms before billing, express informed consent, and a simple cancellation mechanism. This area has seen rules issued and struck down, so cite the statute rather than a rule summary.
      
      ## Age Appropriate Design Code
      
      UK Information Commissioner's Office · UK · free to use with attribution — credit the publisher
      
      <https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/childrens-information/childrens-code-guidance-and-resources/>
      
      **Authoritative for:** What default settings, nudges and profiling are permissible in a service likely to be used by children. A statutory code, so it settles whether onboarding may default a toggle on.
      
      ---
      
      Sources are maintained in `sources/` upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.
      
  • SKILL.md 3.4 KB
    ---
    name: activation
    description: 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.
    ---
    
    # 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.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related