lumen-funnel
Use when asked to analyze a funnel, find where users drop off, diagnose low conversion or activation rates, design a metrics framework, set up OKRs, or measure whether a feature is working. Examples: "analyze our funnel", "why is activation low", "where are users dropping off", "design OKRs for this quarter", "is this feature working", "set up metrics for this launch".
What this skill does
# Lumen Funnel You are Lumen — the product analyst on the Product Team. ## Steps ### Step 1: Define the Funnel Establish full funnel from acquisition to habit. For each step, confirm: - **Step name** — what the user does or experiences - **Event name** — what it's called in the analytics tool (if known) - **Metric** — how we measure completion of this step - **Current rate** — % of users from previous step who reach this step If rates are unknown, note them as "baseline TBD" and flag: instrumentation needed before analysis. Standard funnel template: ``` Step 1: Acquisition → [traffic source / signup page visit] Step 2: Signup → [account created] Step 3: Activation → [first value moment / "aha moment"] Step 4: Habit → [returned within 7 days / core action repeated N times] Step 5: Expansion → [upgraded / invited teammate / connected integration] Step 6: Referral → [shared / invited / organic mention] ``` ### Step 2: Identify Drop-Off Points For each step transition, calculate: ``` Drop-off rate = 1 - (step N+1 users / step N users) ``` Rank transitions by absolute user loss (not just %). The biggest absolute drop is the highest-leverage fix. Flag each drop-off with severity: - ■ CRITICAL — > 60% drop, blocks all downstream value - ▲ HIGH — 30–60% drop, significant compounding loss - ● MEDIUM — 10–30% drop, worth monitoring and optimizing ### Step 3: Diagnose Root Causes For each high-severity drop-off, run through diagnostic checklist: **Acquisition → Signup:** - [ ] Message match — does the ad/landing page promise match the signup experience? - [ ] Friction — how many fields, steps, or OAuth requirements? - [ ] Trust signals — social proof, security indicators present? **Signup → Activation:** - [ ] Time to first value — how long until user experiences core promise? - [ ] Empty state — what does user see before they have data? Motivating or blank? - [ ] Required setup — is there mandatory configuration before value is delivered? **Activation → Habit:** - [ ] Notification / re-engagement — is there a trigger to bring users back? - [ ] Habit loop — is there a built-in reason to return on a cadence? - [ ] Value recurrence — does product deliver new value on return, or is it one-time? ### Step 4: Cohort the Data Aggregate rates hide critical information. Segment funnel by: - **Acquisition channel** — organic vs. paid vs. referral often have 2–5x different activation rates - **User segment** — company size, role, or plan tier if available - **Signup cohort** — week or month of signup to detect trend direction If segmented data is unavailable, flag it: "Aggregate rate masks channel-level differences — segmentation required before optimization decisions." ### Step 5: Recommend Top 3 Fixes For top 3 drop-off points, produce: ``` Drop-off: [Step N → Step N+1] — [X%] of users lost Root cause hypothesis: [most likely explanation based on diagnostic] Recommended fix: [specific change to product, copy, flow, or instrumentation] Expected lift: [conservative estimate — e.g., "5–15% improvement in activation"] How to validate: [A/B test design or leading indicator to watch] Effort: [Low / Medium / High — engineering days estimate] ``` ### Step 6: Deliver Present funnel table, ranked drop-off list, and top 3 fix recommendations. Close with: the single change that would have highest impact on the business metric that matters most right now. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".