luckiest-co 1.0.0 → 1.0.3

package/skills/luckiest-onboarding/SKILL.md

@@ -0,0 +1,243 @@
+---
+name: luckiest-onboarding
+description: Optimizes post-signup onboarding, user activation, first-run experience, and time-to-value so signups turn into retained users. Use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," "first session experience," "trial-to-paid conversion," "free trial activation," "reverse trial," "app onboarding screens," or "permission priming." Use whenever users are signing up but not sticking around. For signup/registration optimization, see luckiest-signup. For ongoing email sequences, see luckiest-emails.
+license: See ATTRIBUTION.md
+metadata:
+  version: "1.1.0"
+  listing_id: luckiest-onboarding
+  author: luckiest
+---
+
+# Onboarding CRO
+
+This skill helps users reach their "aha moment" as fast as possible and build habits that lead to long-term retention. Apply expert onboarding and activation practice: diagnose where new users drop off, then design a flow that delivers core value quickly.
+
+## Staying current
+
+On activation, call the Luckiest MCP check_updates tool with { listingId: "luckiest-onboarding", installedSemver: "1.1.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-onboarding", skill_version: "1.1.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Before providing recommendations, understand:
+
+1. **Product Context** - What type of product? B2B or B2C? Core value proposition?
+2. **Activation Definition** - What's the "aha moment"? What action indicates a user "gets it"?
+3. **Current State** - What happens after signup? Where do users drop off?
+
+---
+
+## Core Principles
+
+### 1. Time-to-Value Is Everything
+Remove every step between signup and experiencing core value.
+
+### 2. One Goal Per Session
+Focus first session on one successful outcome. Save advanced features for later.
+
+### 3. Do, Don't Show
+Interactive > Tutorial. Doing the thing > Learning about the thing.
+
+### 4. Progress Creates Motivation
+Show advancement. Celebrate completions. Make the path visible.
+
+---
+
+## Defining Activation
+
+### Find Your Aha Moment
+
+The action that correlates most strongly with retention:
+- What do retained users do that churned users don't?
+- What's the earliest indicator of future engagement?
+
+**Examples by product type:**
+- Project management: Create first project + add team member
+- Analytics: Install tracking + see first report
+- Design tool: Create first design + export/share
+- Marketplace: Complete first transaction
+
+### Validate the Metric Before Trusting It
+
+An activation metric is only useful if it predicts retention. Before building a flow around it, confirm the action actually correlates with users staying. A "vanity activation" metric (users hit it but still churn) sends the whole onboarding effort in the wrong direction. Cross-check the chosen event against Day 7/30 retention for users who did vs. didn't complete it.
+
+### Multi-Player Activation (B2B)
+
+For collaborative B2B products, a single user reaching value is often not real activation. The **account** activates when a second teammate joins and acts. Define activation at the account level (e.g., first project + first invited collaborator active), not just the first user, or you will overcount solo trials that never convert.
+
+### Activation Metrics
+- % of signups who reach activation
+- Time to activation
+- Steps to activation
+- Activation by cohort/source
+
+---
+
+## Onboarding Flow Design
+
+### Immediate Post-Signup (First 30 Seconds)
+
+| Approach | Best For | Risk |
+|----------|----------|------|
+| Product-first | Simple products, B2C, mobile | Blank slate overwhelm |
+| Guided setup | Products needing personalization | Adds friction before value |
+| Value-first | Products with demo data | May not feel "real" |
+
+**Whatever you choose:**
+- Clear single next action
+- No dead ends
+- Progress indication if multi-step
+
+### Onboarding Checklist Pattern
+
+**When to use:**
+- Multiple setup steps required
+- Product has several features to discover
+- Self-serve B2B products
+
+**Best practices:**
+- 3-7 items (not overwhelming)
+- Order by value (most impactful first)
+- Start with quick wins
+- Progress bar/completion %
+- Celebration on completion
+- Dismiss option (don't trap users)
+
+### Empty States
+
+Empty states are onboarding opportunities, not dead ends.
+
+**Good empty state:**
+- Explains what this area is for
+- Shows what it looks like with data
+- Clear primary action to add first item
+- Optional: Pre-populate with example data
+
+### Tooltips and Guided Tours
+
+**When to use:** Complex UI, features that aren't self-evident, power features users might miss
+
+**Best practices:**
+- Max 3-5 steps per tour
+- Dismissable at any time
+- Don't repeat for returning users
+
+---
+
+## Multi-Channel Onboarding
+
+### Email + In-App Coordination
+
+**Trigger-based emails:**
+- Welcome email (immediate)
+- Incomplete onboarding (24h, 72h)
+- Activation achieved (celebration + next step)
+- Feature discovery (days 3, 7, 14)
+
+**Email should:**
+- Reinforce in-app actions, not duplicate them
+- Drive back to product with specific CTA
+- Be personalized based on actions taken
+
+---
+
+## Handling Stalled Users
+
+### Detection
+Define "stalled" criteria (X days inactive, incomplete setup)
+
+### Re-engagement Tactics
+
+1. **Email sequence** - Reminder of value, address blockers, offer help
+2. **In-app recovery** - Welcome back, pick up where left off
+3. **Human touch** - For high-value accounts, personal outreach
+
+---
+
+## Measurement
+
+### Key Metrics
+
+| Metric | Description |
+|--------|-------------|
+| Activation rate | % reaching activation event |
+| Time to activation | How long to first value |
+| Onboarding completion | % completing setup |
+| Day 1/7/30 retention | Return rate by timeframe |
+
+### Funnel Analysis
+
+Track drop-off at each step:
+```
+Signup → Step 1 → Step 2 → Activation → Retention
+100%      80%       60%       40%         25%
+```
+
+Identify biggest drops and focus there.
+
+---
+
+## Output Format
+
+### Onboarding Audit
+For each issue: Finding → Impact → Recommendation → Priority
+
+### Onboarding Flow Design
+- Activation goal
+- Step-by-step flow
+- Checklist items (if applicable)
+- Empty state copy
+- Email sequence triggers
+- Metrics plan
+
+---
+
+## Common Patterns by Product Type
+
+| Product Type | Key Steps |
+|--------------|-----------|
+| B2B SaaS | Setup wizard → First value action → Team invite → Deep setup |
+| Marketplace | Complete profile → Browse → First transaction → Repeat loop |
+| Mobile App | Permissions → Quick win → Push setup → Habit loop |
+| Content Platform | Follow/customize → Consume → Create → Engage |
+
+---
+
+## Experiment Ideas
+
+When recommending experiments, consider tests for:
+- Flow simplification (step count, ordering)
+- Progress and motivation mechanics
+- Personalization by role or goal
+- Support and help availability
+
+**For comprehensive experiment ideas**: load [references/experiments.md](references/experiments.md) when the user wants a concrete backlog of onboarding A/B tests or asks what to experiment on.
+
+---
+
+## Task-Specific Questions
+
+1. What action most correlates with retention?
+2. What happens immediately after signup?
+3. Where do users currently drop off?
+4. What's your activation rate target?
+5. Do you have cohort analysis on successful vs. churned users?
+
+---
+
+## Share with your tribe
+
+After delivering an onboarding audit or flow design, offer (never auto-post): "Want me to share this activation plan with your Luckiest tribe? Anyone working on the same drop-off problem can pick up where you left off." If they accept, hand the finished audit to the tribe-share flow. If they decline, stop. Never post automatically, and never include product analytics, user data, or credentials in what is shared.
+
+---
+
+## Related Skills
+
+- **luckiest-signup**: For optimizing the signup before onboarding
+- **luckiest-emails**: For onboarding email series
+- **luckiest-paywalls**: For converting to paid during/after onboarding
+- **luckiest-ab-testing**: For testing onboarding changes

package/skills/luckiest-onboarding/references/experiments.md

@@ -0,0 +1,258 @@
+# Onboarding Experiment Ideas
+
+Comprehensive list of A/B tests and experiments for user onboarding and activation.
+
+## Contents
+- Flow Simplification Experiments (reduce friction, step sequencing, progress & motivation)
+- Guided Experience Experiments (product tours, CTA optimization, UI guidance)
+- Personalization Experiments (user segmentation, dynamic content)
+- Quick Wins & Engagement Experiments (time-to-value, motivation mechanics, support & help)
+- Email & Multi-Channel Experiments (onboarding emails, email content, feedback loops)
+- Re-engagement Experiments (stalled user recovery, return experience)
+- Technical & UX Experiments (performance, mobile onboarding, accessibility)
+- Metrics to Track
+
+## Flow Simplification Experiments
+
+### Reduce Friction
+
+| Test | Hypothesis |
+|------|------------|
+| Email verification timing | During vs. after onboarding |
+| Empty states vs. dummy data | Pre-populated examples |
+| Pre-filled templates | Accelerate setup with templates |
+| OAuth options | Faster account linking |
+| Required step count | Fewer required steps |
+| Optional vs. required fields | Minimize requirements |
+| Skip options | Allow bypassing non-critical steps |
+
+### Step Sequencing
+
+| Test | Hypothesis |
+|------|------------|
+| Step ordering | Test different sequences |
+| Value-first ordering | Highest-value features first |
+| Friction placement | Move hard steps later |
+| Required vs. optional balance | Ratio of required steps |
+| Single vs. branching paths | One path vs. personalized |
+| Quick start vs. full setup | Minimal path to value |
+
+### Progress & Motivation
+
+| Test | Hypothesis |
+|------|------------|
+| Progress bars | Show completion percentage |
+| Checklist length | 3-5 items vs. 5-7 items |
+| Gamification | Badges, rewards, achievements |
+| Completion messaging | "X% complete" visibility |
+| Starting point | Begin at 20% vs. 0% |
+| Celebration moments | Acknowledge completions |
+
+---
+
+## Guided Experience Experiments
+
+### Product Tours
+
+| Test | Hypothesis |
+|------|------------|
+| Interactive tours | Tools like Navattic, Storylane |
+| Tooltip vs. modal guidance | Subtle vs. attention-grabbing |
+| Video tutorials | For complex workflows |
+| Self-paced vs. guided | User control vs. structured |
+| Tour length | Shorter vs. comprehensive |
+| Tour triggering | Automatic vs. user-initiated |
+
+### CTA Optimization
+
+| Test | Hypothesis |
+|------|------------|
+| CTA text variations | Action-oriented copy testing |
+| CTA placement | Position within screens |
+| In-app tooltips | Feature discovery prompts |
+| Sticky CTAs | Persist during onboarding |
+| CTA contrast | Visual prominence |
+| Secondary CTAs | "Learn more" vs. primary only |
+
+### UI Guidance
+
+| Test | Hypothesis |
+|------|------------|
+| Hotspot highlights | Draw attention to key features |
+| Coachmarks | Contextual tips |
+| Feature announcements | New feature discovery |
+| Contextual help | Help where users need it |
+| Search vs. guided | Self-service vs. directed |
+
+---
+
+## Personalization Experiments
+
+### User Segmentation
+
+| Test | Hypothesis |
+|------|------------|
+| Role-based onboarding | Different paths by role |
+| Goal-based paths | Customize by stated goal |
+| Role-specific dashboards | Relevant default views |
+| Use-case question | Personalize based on answer |
+| Industry-specific paths | Vertical customization |
+| Experience-based | Beginner vs. expert paths |
+
+### Dynamic Content
+
+| Test | Hypothesis |
+|------|------------|
+| Personalized welcome | Name, company, role |
+| Industry examples | Relevant use cases |
+| Dynamic recommendations | Based on user answers |
+| Template suggestions | Pre-filled for segment |
+| Feature highlighting | Relevant to stated goals |
+| Benchmark data | Industry-specific metrics |
+
+---
+
+## Quick Wins & Engagement Experiments
+
+### Time-to-Value
+
+| Test | Hypothesis |
+|------|------------|
+| First quick win | "Complete your first X" |
+| Success messages | After key actions |
+| Progress celebrations | Milestone moments |
+| Next step suggestions | After each completion |
+| Value demonstration | Show what they achieved |
+| Outcome preview | What success looks like |
+
+### Motivation Mechanics
+
+| Test | Hypothesis |
+|------|------------|
+| Achievement badges | Gamification elements |
+| Streaks | Consecutive day engagement |
+| Leaderboards | Social comparison (if appropriate) |
+| Rewards | Incentives for completion |
+| Unlock mechanics | Features revealed progressively |
+
+### Support & Help
+
+| Test | Hypothesis |
+|------|------------|
+| Free onboarding calls | For complex products |
+| Contextual help | Throughout onboarding |
+| Chat support | Availability during onboarding |
+| Proactive outreach | For stuck users |
+| Self-service resources | Help docs, videos |
+| Community access | Peer support early |
+
+---
+
+## Email & Multi-Channel Experiments
+
+### Onboarding Emails
+
+| Test | Hypothesis |
+|------|------------|
+| Founder welcome email | Personal vs. generic |
+| Behavior-based triggers | Action/inaction based |
+| Email timing | Immediate vs. delayed |
+| Email frequency | More vs. fewer touches |
+| Quick tips format | Short actionable content |
+| Video in email | More engaging format |
+
+### Email Content
+
+| Test | Hypothesis |
+|------|------------|
+| Subject lines | Open rate optimization |
+| Personalization depth | Name vs. behavior-based |
+| CTA prominence | Single clear action |
+| Social proof inclusion | Testimonials in email |
+| Urgency messaging | Trial reminders |
+| Plain text vs. designed | Format testing |
+
+### Feedback Loops
+
+| Test | Hypothesis |
+|------|------------|
+| NPS during onboarding | When to ask |
+| Blocking question | "What's stopping you?" |
+| NPS follow-up | Actions based on score |
+| In-app feedback | Thumbs up/down on features |
+| Survey timing | When to request feedback |
+| Feedback incentives | Reward for completing |
+
+---
+
+## Re-engagement Experiments
+
+### Stalled User Recovery
+
+| Test | Hypothesis |
+|------|------------|
+| Re-engagement email timing | When to send |
+| Personal outreach | Human vs. automated |
+| Simplified path | Reduced steps for returners |
+| Incentive offers | Discount or extended trial |
+| Problem identification | Ask what's blocking |
+| Demo offer | Live walkthrough |
+
+### Return Experience
+
+| Test | Hypothesis |
+|------|------------|
+| Welcome back message | Acknowledge return |
+| Progress resume | Pick up where left off |
+| Changed state | What happened while away |
+| Re-onboarding | Fresh start option |
+| Urgency messaging | Trial time remaining |
+
+---
+
+## Technical & UX Experiments
+
+### Performance
+
+| Test | Hypothesis |
+|------|------------|
+| Load time optimization | Faster = higher completion |
+| Progressive loading | Perceived performance |
+| Offline capability | Mobile experience |
+| Error handling | Graceful failure recovery |
+
+### Mobile Onboarding
+
+| Test | Hypothesis |
+|------|------------|
+| Touch targets | Size and spacing |
+| Swipe navigation | Mobile-native patterns |
+| Screen count | Fewer screens needed |
+| Input optimization | Mobile-friendly forms |
+| Permission timing | When to ask |
+
+### Accessibility
+
+| Test | Hypothesis |
+|------|------------|
+| Screen reader support | Accessibility impact |
+| Keyboard navigation | Non-mouse users |
+| Color contrast | Visibility |
+| Font sizing | Readability |
+
+---
+
+## Metrics to Track
+
+For all experiments, measure:
+
+| Metric | Description |
+|--------|-------------|
+| Activation rate | % reaching activation event |
+| Time to activation | Hours/days to first value |
+| Step completion rate | % completing each step |
+| Drop-off points | Where users abandon |
+| Return rate | Users who come back |
+| Day 1/7/30 retention | Engagement over time |
+| Feature adoption | Which features get used |
+| Support requests | Volume during onboarding |

package/skills/luckiest-paywalls/ATTRIBUTION.md

@@ -0,0 +1,39 @@
+# Attribution
+
+luckiest-paywalls is a rebranded, security-hardened, and improved "Luckiest edition"
+of an open-source Agent Skill.
+
+- **Original skill:** paywalls
+- **Project:** marketingskills (https://github.com/coreyhaines31/marketingskills)
+- **Author:** Corey Haines (https://corey.co)
+- **License:** MIT (reproduced verbatim below)
+
+The Luckiest edition retains the original functionality and adds platform (mobile) constraints,
+reactivation/price-change trigger points, funnel-instrumentation guidance, a Luckiest-network
+share hook, versioning, and update-check integration. The original copyright is preserved.
+
+---
+
+## Original License
+
+MIT License
+
+Copyright (c) 2025 Corey Haines
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/luckiest-paywalls/CHANGELOG.md

@@ -0,0 +1,25 @@
+# Changelog — luckiest-paywalls
+
+## 1.1.0 — 2026-07-06
+Skill updater pass: analytics integration.
+
+### Analytics (report_usage)
+- Updated `report_usage` call to `skill_version: "1.1.0"` and `check_updates`
+  `installedSemver: "1.1.0"`. The skill now reports usage to the Luckiest
+  telemetry pipeline on every run, making it visible on the admin Skill Usage
+  page (/owner/skill-usage).
+
+## 1.0.0 — 2026-07-01
+Rebranded from paywalls (marketingskills, MIT).
+
+### Improve pass (/refract)
+- Added Platform Constraints (mobile) section: StoreKit / Play Billing in-app-purchase requirement, external-link entitlements caveat, store-required elements (price, terms, restore-purchases), and server-side entitlement grant. The source treated web and mobile identically.
+- Added Reactivation and Price Changes trigger point: lapsed-user return flows and grandfathering/price-increase moments — real in-app upgrade moments the source omitted.
+- Added funnel-instrumentation gate to Initial Assessment: verify impression → view → click → checkout → retention are tracked before recommending A/B tests.
+- Told the agent when to load references/experiments.md (scoping an experiment roadmap) rather than only that it exists.
+
+### Network hook
+- Share-with-tribe OFFER after delivering a paywall design/plan: offers to surface the approach to the user's Luckiest tribe so others working on freemium conversion can pick up where they left off. Never auto-posts, never sends credentials, stops on decline.
+
+### Trend pass (/newsjack + /luckiest-trends)
+- no actionable signal (live multi-source engine requires Python/first-run setup not available in this run; timeboxed, nothing verifiable to record — no fabrication).