Conversion problems are easy to feel and hard to diagnose. The team senses that the funnel is leaking but cannot point to where. Activation might be the issue, or the signup form, or the third onboarding step, or the empty dashboard. Without the per-step view, the team picks an intervention by intuition and ships it, which is how teams accumulate a stack of activation experiments without measurable improvement. The real diagnosis requires the funnel mapped, drop-off measured per step, and cohorts compared by acquisition channel and signup date so the patterns surface.
The /lumen-funnel skill does the diagnosis end-to-end. It reads the project's analytics data, maps the funnel, computes drop-off per step, compares cohorts, identifies the highest-impact drop-off, and produces specific recommendations. The output is the diagnosis the team would otherwise spend a focused day building manually.
What useful funnel analysis requires
Five parts. Funnel mapping: the sequence of events from acquisition to value moment. Per-step conversion: percentage of users completing each step, with the time horizon (some steps complete in seconds, others over days). Cohort comparison: how does conversion differ by acquisition channel, signup week, plan tier. Drop-off prioritization: which step is the highest-impact place to invest. Recommendations: specific interventions calibrated to the drop-off (form simplification for a form drop, content for an empty-dashboard drop).
How /lumen-funnel works
The skill reads from the project's analytics tool (Amplitude, Mixpanel, PostHog, or warehouse-based events). It computes the funnel with cohort splits and identifies the steps with the largest absolute drop. For each big drop, the skill proposes hypotheses ("the email verification step is gating product use; users who do not verify within an hour rarely return") and the experiment to test. The output is the report plus the next experiment to ship.
Cohort comparison by acquisition channel often reveals that the funnel is not actually broken; one specific channel is bringing low-intent users. The right fix is then on the acquisition side, not the funnel side. /lumen-funnel surfaces this distinction explicitly.
Tonone's /lumen-funnel skill maps the conversion funnel, compares cohorts, identifies the highest-impact drop-off, and produces specific recommendations.
When to use /lumen-funnel
/lumen-funnel is the right call when conversion or activation rates are below benchmark and the cause is unclear, or when designing a metrics review that needs the funnel breakdown. Skip it for funnel analysis on already-instrumented well-defined funnels (use the BI tool directly). For activation funnel design specifically with an action plan, /surge-activation is the right call.
| Capability | Tonone | Generalist chatbot | Cursor / Copilot |
|---|---|---|---|
| Reads project analytics data | Yes, Amplitude/Mixpanel/PostHog/warehouse | No data access | Tool-specific |
| Cohort comparison by channel and date | Yes, surfaces channel-driven issues | Aggregate only | Variable |
| Drop-off ranking with hypothesis | Yes, with proposed experiment | Generic advice | Variable |
| Distinguishes funnel issue from acquisition issue | Yes, surfaces the distinction | Conflates them | Variable |
Related skills
/lumen-funnel analyzes funnels. For activation work specifically with a ranked improvement plan, /surge-activation is the right call. For metrics architecture more broadly, /lumen-metrics is calibrated to that work. For event tracking instrumentation, /lumen-instrument covers the upstream layer.
Install
/lumen-funnel ships with the Lumen agent in Tonone for Claude Code. Install Tonone, configure analytics access, and the skill produces the funnel diagnosis.
1. Add to marketplace
2. Install Lumen
Frequently asked questions
- What does /lumen-funnel do?
- It maps the conversion funnel, computes drop-off per step, compares cohorts by acquisition channel and date, identifies the highest-impact drop-off, and produces specific recommendations and an experiment to test.
- What analytics tools does /lumen-funnel support?
- Amplitude, Mixpanel, PostHog, Heap, and warehouse-based event analytics.
- When should I use /lumen-funnel?
- When conversion or activation rates are below benchmark and the cause is unclear, or when preparing a metrics review.
- How is /lumen-funnel different from /surge-activation?
- /lumen-funnel is the diagnosis: where is the loss. /surge-activation produces the action plan: what to ship to fix the loss. They are often used together.
- How do I install /lumen-funnel?
- Install Tonone for Claude Code via tonone.ai/get-started. /lumen-funnel ships with the Lumen agent. Tonone is free and MIT-licensed.
Pairs well with
The metrics that matter, the funnels that leak, and the cohorts no one noticed were churning.
Growth systems that compound. Acquisition loops, activation funnels, and retention hooks that don't stop working.
What users actually want: not what they say, not what the team guesses. What the evidence shows.