luckiest-co 1.0.0 → 1.0.3

package/skills/luckiest-paywalls/SKILL.md

@@ -0,0 +1,256 @@
+---
+name: luckiest-paywalls
+description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where the user is asking someone to upgrade. Distinct from public pricing pages (see luckiest-cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see luckiest-pricing.
+license: See ATTRIBUTION.md
+metadata:
+  version: "1.1.0"
+  listing_id: luckiest-paywalls
+  author: luckiest
+---
+
+# Paywall and Upgrade Screen CRO
+
+This skill guides expert work on in-app paywalls and upgrade flows. The goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they have experienced enough value to justify the commitment.
+
+## Staying current
+
+On activation, call the Luckiest MCP check_updates tool with { listingId: "luckiest-paywalls", 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-paywalls", 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.
+
+**Verify the funnel is instrumented before optimizing.**
+Before recommending tests or redesigns, confirm the paywall funnel is actually tracked: impression, view-to-click, click-to-checkout, checkout completion, and post-upgrade retention. If these events are not captured, fixing instrumentation is the first recommendation — optimization without measurement is guessing.
+
+Before providing recommendations, understand:
+
+1. **Upgrade Context** - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit? Reactivation or price change?
+2. **Product Model** - What is free? What is behind the paywall? What triggers prompts? Current conversion rate?
+3. **User Journey** - When does this appear? What have they experienced? What are they trying to do?
+4. **Platform** - Web, mobile app, or both? Mobile changes what is possible (see Platform Constraints).
+
+---
+
+## Core Principles
+
+### 1. Value Before Ask
+- The user should have experienced real value first
+- The upgrade should feel like a natural next step
+- Timing: after the "aha moment," not before
+
+### 2. Show, Don't Just Tell
+- Demonstrate the value of paid features
+- Preview what they are missing
+- Make the upgrade feel tangible
+
+### 3. Friction-Free Path
+- Easy to upgrade when ready
+- Do not make them hunt for pricing
+
+### 4. Respect the No
+- Do not trap or pressure
+- Make it easy to continue free
+- Maintain trust for future conversion
+
+---
+
+## Paywall Trigger Points
+
+### Feature Gates
+When the user clicks a paid-only feature:
+- Clear explanation of why it is paid
+- Show what the feature does
+- Quick path to unlock
+- Option to continue without
+
+### Usage Limits
+When the user hits a limit:
+- Clear indication of limit reached
+- Show what upgrading provides
+- Do not block abruptly
+
+### Trial Expiration
+When the trial is ending:
+- Early warnings (7, 3, 1 day)
+- Clear "what happens" on expiration
+- Summarize value received
+
+### Time-Based Prompts
+After X days of free use:
+- Gentle upgrade reminder
+- Highlight unused paid features
+- Easy to dismiss
+
+### Reactivation and Price Changes
+For lapsed or churned users, and existing users at a price increase:
+- Reactivation: acknowledge the return, summarize what they built before, offer a low-friction path back
+- Price change: grandfather where fair, explain the change plainly, give a clear window to lock the old rate. Avoid surprise increases — they drive churn and support load.
+
+---
+
+## Paywall Screen Components
+
+1. **Headline** - Focus on what they get: "Unlock [Feature] to [Benefit]"
+2. **Value Demonstration** - Preview, before/after, "With Pro you could..."
+3. **Feature Comparison** - Highlight key differences, current plan marked
+4. **Pricing** - Clear, simple, annual vs. monthly options
+5. **Social Proof** - Customer quotes, "X teams use this"
+6. **CTA** - Specific and value-oriented: "Start Getting [Benefit]"
+7. **Escape Hatch** - Clear "Not now" or "Continue with Free"
+
+---
+
+## Specific Paywall Types
+
+### Feature Lock Paywall
+```
+[Lock Icon]
+This feature is available on Pro
+
+[Feature preview/screenshot]
+
+[Feature name] helps you [benefit]:
+• [Capability]
+• [Capability]
+
+[Upgrade to Pro - $X/mo]
+[Maybe Later]
+```
+
+### Usage Limit Paywall
+```
+You've reached your free limit
+
+[Progress bar at 100%]
+
+Free: 3 projects | Pro: Unlimited
+
+[Upgrade to Pro]  [Delete a project]
+```
+
+### Trial Expiration Paywall
+```
+Your trial ends in 3 days
+
+What you'll lose:
+• [Feature used]
+• [Data created]
+
+What you've accomplished:
+• Created X projects
+
+[Continue with Pro]
+[Remind me later]  [Downgrade]
+```
+
+---
+
+## Platform Constraints (mobile)
+
+Native mobile paywalls are not free-form web pages. Account for store rules:
+
+- **In-app purchase requirement** - Apple and Google generally require digital subscriptions to go through StoreKit / Play Billing, which caps copy, pricing display, and CTA behavior.
+- **External-link entitlements** - Post-litigation, some external-purchase links are allowed in some regions, but the rules are narrow and shifting. Do not assume a "just take them to the website" flow is compliant; verify against current store policy.
+- **Required elements** - Store review often requires visible price, billing period, terms, and a restore-purchases path. Omitting these can block release.
+- **Server-side entitlement** - Grant access based on validated receipts, not client state, so paid features unlock reliably across devices.
+
+When the platform is unknown, ask before giving mobile-specific pricing or CTA copy.
+
+---
+
+## Timing and Frequency
+
+### When to Show
+- After a value moment, before frustration
+- After activation / aha moment
+- When hitting genuine limits
+
+### When NOT to Show
+- During onboarding (too early)
+- When they are in a flow
+- Repeatedly after dismissal
+
+### Frequency Rules
+- Limit per session
+- Cool-down after dismiss (days, not hours)
+- Track annoyance signals
+
+---
+
+## Upgrade Flow Optimization
+
+### From Paywall to Payment
+- Minimize steps
+- Keep in-context if possible
+- Pre-fill known information
+
+### Post-Upgrade
+- Immediate access to features
+- Confirmation and receipt
+- Guide to new features
+
+---
+
+## A/B Testing
+
+### What to Test
+- Trigger timing
+- Headline / copy variations
+- Price presentation
+- Trial length
+- Feature emphasis
+- Design / layout
+
+### Metrics to Track
+- Paywall impression rate
+- Click-through to upgrade
+- Completion rate
+- Revenue per user
+- Churn rate post-upgrade
+
+**For comprehensive experiment ideas**: load [references/experiments.md](references/experiments.md) when the user wants a menu of tests to run or is scoping an experimentation roadmap.
+
+---
+
+## Anti-Patterns to Avoid
+
+### Dark Patterns
+- Hiding the close button
+- Confusing plan selection
+- Guilt-trip copy
+
+### Conversion Killers
+- Asking before value delivered
+- Too frequent prompts
+- Blocking critical flows
+- Complicated upgrade process
+
+---
+
+## Task-Specific Questions
+
+1. What is your current free → paid conversion rate?
+2. What triggers upgrade prompts today?
+3. What features are behind the paywall?
+4. What is your "aha moment" for users?
+5. What pricing model? (per seat, usage, flat)
+6. Mobile app, web app, or both?
+
+---
+
+## Share with your tribe
+
+After delivering a paywall design or optimization plan, offer (never auto-post, never send credentials): "Want me to share this paywall approach with your Luckiest tribe? Others working on freemium conversion can pick up where you left off." Only share if the user accepts. If they decline, stop.
+
+---
+
+## Related Skills
+
+- **luckiest-churn-prevention**: For cancel flows, save offers, and reducing churn post-upgrade
+- **luckiest-cro**: For public pricing page optimization
+- **luckiest-onboarding**: For driving to aha moment before upgrade
+- **luckiest-ab-testing**: For testing paywall variations

package/skills/luckiest-paywalls/evals/evals.json

@@ -0,0 +1,93 @@
+{
+  "skill_name": "luckiest-paywalls",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me design the upgrade paywall for our project management tool. Free users can have 3 projects, and we want to show an upgrade screen when they try to create a 4th project.",
+      "expected_output": "Should check for product-marketing.md first. Should identify this as a usage limit trigger point. Should apply the paywall screen components: headline (communicate the value of upgrading, not just the limit), value demonstration (show what they get with paid plan), plan comparison (free vs paid), social proof, CTA (specific and action-oriented), and escape hatch (option to go back). Should provide specific copy recommendations. Should address the emotional state of the user at this moment (frustrated by the limit). Should warn against anti-patterns.",
+      "assertions": [
+        "Checks for product-marketing.md",
+        "Identifies as usage limit trigger",
+        "Applies paywall screen components framework",
+        "Includes headline, value demo, comparison, social proof, CTA",
+        "Provides specific copy recommendations",
+        "Addresses user's emotional state at the limit",
+        "Includes escape hatch option",
+        "Warns against anti-patterns"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Our free trial expires in 14 days and users see a generic 'Your trial has expired' screen. Upgrade rate from this screen is only 2%. How do we improve it?",
+      "expected_output": "Should identify this as a trial expiration trigger. Should apply the trial expiration paywall type guidance. Should recommend: show what they've built/accomplished during the trial (endowment effect), highlight specific features they used, show the value they'd lose, provide clear plan options, include social proof from similar users who upgraded. Should diagnose why 2% is low: likely a weak value prop, no personalization, no urgency or loss framing. Should provide specific redesign recommendations.",
+      "assertions": [
+        "Identifies as trial expiration trigger",
+        "Applies trial expiration paywall guidance",
+        "Recommends showing user's accomplishments during trial",
+        "Uses loss framing (what they'd lose)",
+        "Provides clear plan options",
+        "Includes social proof",
+        "Diagnoses why current 2% rate is low",
+        "Provides specific redesign recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "when should we show upgrade prompts? we don't want to be annoying but we also need to convert free users to paid.",
+      "expected_output": "Should trigger on casual phrasing. Should apply the timing and frequency rules. Should recommend trigger points from the skill: feature gates (when they try a paid feature), usage limits (when they hit a threshold), value moments (when they've just experienced success), and natural transition points. Should address frequency capping to avoid being annoying. Should recommend the anti-patterns to avoid (blocking basic functionality, too frequent popups, dark patterns). Should provide a balanced approach that respects user experience while driving upgrades.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies timing and frequency rules",
+        "Recommends specific trigger points",
+        "Addresses frequency capping",
+        "Warns against anti-patterns",
+        "Balances user experience with conversion goals",
+        "Provides specific recommendations for each trigger type"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Design a feature gate paywall. When free users click on 'Advanced Analytics' in our dashboard, we want to show them an upgrade prompt.",
+      "expected_output": "Should identify this as a feature gate trigger. Should apply the feature lock paywall type guidance. Should recommend: show a preview or screenshot of the advanced analytics feature, explain the specific benefit (not just 'this is a paid feature'), include a plan comparison relevant to analytics, provide a clear CTA to upgrade, and include an escape hatch to go back to basic analytics. Should recommend showing what insights they're missing. Should provide copy recommendations for the paywall screen.",
+      "assertions": [
+        "Identifies as feature gate trigger",
+        "Applies feature lock paywall guidance",
+        "Recommends showing preview of the feature",
+        "Explains specific benefit of the feature",
+        "Includes relevant plan comparison",
+        "Provides clear CTA and escape hatch",
+        "Provides copy recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What are common mistakes to avoid with in-app paywalls? I don't want to be pushy or make users feel tricked.",
+      "expected_output": "Should apply the anti-patterns section. Should cover: dark patterns (making it hard to find the close button, confusing opt-out language), conversion killers (blocking basic functionality, showing paywalls too early before value is demonstrated, no escape hatch), frequency issues (too many prompts, showing the same paywall repeatedly). Should provide positive alternatives for each anti-pattern. Should emphasize that good paywalls feel helpful, not pushy.",
+      "assertions": [
+        "Applies anti-patterns section",
+        "Covers dark patterns to avoid",
+        "Covers conversion killers",
+        "Covers frequency issues",
+        "Provides positive alternatives for each",
+        "Emphasizes helpful over pushy approach"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you help me optimize our public pricing page? We want more visitors to choose the Pro plan over the Basic plan.",
+      "expected_output": "Should recognize this is a public pricing page optimization task, not an in-app paywall task. Should defer to or cross-reference the luckiest-cro skill for pricing page CRO. luckiest-paywalls specifically handles in-app upgrade prompts for existing users, not public-facing pricing pages.",
+      "assertions": [
+        "Recognizes this as public pricing page optimization",
+        "References or defers to luckiest-cro skill",
+        "Explains that luckiest-paywalls is for in-app upgrade prompts",
+        "Does not attempt public pricing page optimization"
+      ],
+      "files": []
+    }
+  ]
+}

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

@@ -0,0 +1,164 @@
+# Paywall Experiment Ideas
+
+Comprehensive list of A/B tests and experiments for paywall optimization.
+
+## Contents
+- Trigger & Timing Experiments (When to Show, Trigger Type)
+- Paywall Design Experiments (Layout & Format, Value Presentation, Visual Elements)
+- Pricing Presentation Experiments (Price Display, Plan Options, Discounts & Offers)
+- Copy & Messaging Experiments (Headlines, CTAs, Objection Handling)
+- Trial & Conversion Experiments (Trial Structure, Trial Expiration, Upgrade Path)
+- Personalization Experiments (Usage-Based, Segment-Specific)
+- Frequency & UX Experiments (Frequency Capping, Dismiss Behavior)
+
+## Trigger & Timing Experiments
+
+### When to Show
+- Test trigger timing: after aha moment vs. at feature attempt
+- Early trial reminder (7 days) vs. late reminder (1 day before)
+- Show after X actions completed vs. after X days
+- Test soft prompts at different engagement thresholds
+- Trigger based on usage patterns vs. time-based only
+
+### Trigger Type
+- Hard gate (can't proceed) vs. soft gate (preview + prompt)
+- Feature lock vs. usage limit as primary trigger
+- In-context modal vs. dedicated upgrade page
+- Banner reminder vs. modal prompt
+- Exit-intent on free plan pages
+
+---
+
+## Paywall Design Experiments
+
+### Layout & Format
+- Full-screen paywall vs. modal overlay
+- Minimal paywall (CTA-focused) vs. feature-rich paywall
+- Single plan display vs. plan comparison
+- Image/preview included vs. text-only
+- Vertical layout vs. horizontal layout on desktop
+
+### Value Presentation
+- Feature list vs. benefit statements
+- Show what they'll lose (loss aversion) vs. what they'll gain
+- Personalized value summary based on usage
+- Before/after demonstration
+- ROI calculator or value quantification
+
+### Visual Elements
+- Add product screenshots or previews
+- Include short demo video or GIF
+- Test illustration vs. product imagery
+- Animated vs. static paywall
+- Progress visualization (what they've accomplished)
+
+---
+
+## Pricing Presentation Experiments
+
+### Price Display
+- Show monthly vs. annual vs. both with toggle
+- Highlight savings for annual ($ amount vs. % off)
+- Price per day framing ("Less than a coffee")
+- Show price after trial vs. emphasize "Start Free"
+- Display price prominently vs. de-emphasize until click
+
+### Plan Options
+- Single recommended plan vs. multiple tiers
+- Add "Most Popular" badge to target plan
+- Test number of visible plans (2 vs. 3)
+- Show enterprise/custom tier vs. hide it
+- Include one-time purchase option alongside subscription
+
+### Discounts & Offers
+- First month/year discount for conversion
+- Limited-time upgrade offer with countdown
+- Loyalty discount based on free usage duration
+- Bundle discount for annual commitment
+- Referral discount for social proof
+
+---
+
+## Copy & Messaging Experiments
+
+### Headlines
+- Benefit-focused ("Unlock unlimited projects") vs. feature-focused ("Get Pro features")
+- Question format ("Ready to do more?") vs. statement format
+- Urgency-based ("Don't lose your work") vs. value-based
+- Personalized headline with user's name or usage data
+- Social proof headline ("Join 10,000+ Pro users")
+
+### CTAs
+- "Start Free Trial" vs. "Upgrade Now" vs. "Continue with Pro"
+- First person ("Start My Trial") vs. second person ("Start Your Trial")
+- Value-specific ("Unlock Unlimited") vs. generic ("Upgrade")
+- Add urgency ("Upgrade Today") vs. no pressure
+- Include price in CTA vs. separate price display
+
+### Objection Handling
+- Add money-back guarantee messaging
+- Show "Cancel anytime" prominently
+- Include FAQ on paywall
+- Address specific objections based on feature gated
+- Add chat/support option on paywall
+
+---
+
+## Trial & Conversion Experiments
+
+### Trial Structure
+- 7-day vs. 14-day vs. 30-day trial length
+- Credit card required vs. not required for trial
+- Full-access trial vs. limited feature trial
+- Trial extension offer for engaged users
+- Second trial offer for expired/churned users
+
+### Trial Expiration
+- Countdown timer visibility (always vs. near end)
+- Email reminders: frequency and timing
+- Grace period after expiration vs. immediate downgrade
+- "Last chance" offer with discount
+- Pause option vs. immediate cancellation
+
+### Upgrade Path
+- One-click upgrade from paywall vs. separate checkout
+- Pre-filled payment info for returning users
+- Multiple payment methods offered
+- Quarterly plan option alongside monthly/annual
+- Team invite flow for solo-to-team conversion
+
+---
+
+## Personalization Experiments
+
+### Usage-Based
+- Personalize paywall copy based on features used
+- Highlight most-used premium features
+- Show usage stats ("You've created 50 projects")
+- Recommend plan based on behavior patterns
+- Dynamic feature emphasis based on user segment
+
+### Segment-Specific
+- Different paywall for power users vs. casual users
+- B2B vs. B2C messaging variations
+- Industry-specific value propositions
+- Role-based feature highlighting
+- Traffic source-based messaging
+
+---
+
+## Frequency & UX Experiments
+
+### Frequency Capping
+- Test number of prompts per session
+- Cool-down period after dismiss (hours vs. days)
+- Escalating urgency over time vs. consistent messaging
+- Once per feature vs. consolidated prompts
+- Re-show rules after major engagement
+
+### Dismiss Behavior
+- "Maybe later" vs. "No thanks" vs. "Remind me tomorrow"
+- Ask reason for declining
+- Offer alternative (lower tier, annual discount)
+- Exit survey on dismiss
+- Friendly vs. neutral decline copy

package/skills/luckiest-popups/ATTRIBUTION.md

@@ -0,0 +1,35 @@
+# Attribution
+
+This skill, **luckiest-popups**, is a rebranded and modified ("Luckiest edition")
+derivative of the original skill **"popups"** from the **marketingskills** project
+(https://github.com/coreyhaines31/marketingskills) by **Corey Haines** (https://corey.co),
+distributed under the MIT License.
+
+The original copyright and license notice are reproduced verbatim below and are retained
+in full as required by the MIT License.
+
+---
+
+## Original License (verbatim)
+
+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-popups/CHANGELOG.md

@@ -0,0 +1,27 @@
+# Changelog — luckiest-popups
+
+## 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 popups (marketingskills, MIT).
+
+### Improve pass (/refract)
+- Added a hard mobile guardrail under Google Guidelines: never let a popup render before main content paints on mobile, since a blocking overlay both triggers Google's intrusive-interstitial penalty and harms Core Web Vitals (LCP and interaction responsiveness/INP). The source warned about intrusive interstitials generically but had no first-paint / Core Web Vitals rule.
+- Strengthened the Accessibility section: return focus to the triggering element on close (genuine a11y gap beyond the existing focus-trap), plus explicit `role="dialog"` / `aria-modal="true"` / labelled-heading guidance.
+- Added a consent-management (CMP) note under GDPR/Privacy: in consent-required regions, sequence the marketing popup behind the consent banner and wire opt-in state into the site's CMP rather than firing independently.
+- Added trigger phrases "my popups are annoying people" and "intrusive interstitial," and eval #7 covering the mobile-first-paint / Core Web Vitals edge case.
+
+### Network hook
+- Share-with-tribe: after a popup pattern proves itself (variant beats control, or complaints drop while conversion holds), the skill OFFERS to surface the sanitized winning pattern to the user's Luckiest tribe. Never auto-posts; strips raw traffic numbers, customer records, email addresses, discount codes, and anything resembling a credential or token.
+
+### Trend pass (/newsjack + /luckiest-trends)
+- Google's mobile intrusive-interstitial guidance remains an active ranking signal and interacts with Core Web Vitals; INP replaced FID as a Core Web Vital in March 2024, making blocking overlays a measurable responsiveness cost — Google Search Central "Intrusive interstitials and dialogs" + web.dev "INP" — 2026-07-01.
+- EEA/UK consent-mode expectations (Google Consent Mode v2, enforced 2024) reinforce sequencing marketing popups behind the consent banner and wiring opt-in into a CMP — Google "Consent Mode v2" — 2026-07-01.
+- Note: /luckiest-trends requires a full multi-source setup wizard outside this task's timebox; the signals above were gathered via host web knowledge and are dated/attributed. No fabricated live-feed data.