luna/marketingskills
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
30f9b9a729bbbe3da562fc1108c31f3a35afcca1
marketingskills/skills/onboarding/references/experiments.md
T
Corey Haines 30f9b9a729 feat: v2.0 skill renames and CRO consolidation (#291) 
* feat: v2.0 skill renames and CRO consolidation

BREAKING CHANGE: Users must reinstall skills after this update.

## Skill Renames (16)
- ab-test-setup → ab-testing
- analytics-tracking → analytics
- aso-audit → aso
- competitor-alternatives → competitors
- email-sequence → emails
- free-tool-strategy → free-tools
- launch-strategy → launch
- onboarding-cro → onboarding
- paywall-upgrade-cro → paywalls
- popup-cro → popups
- pricing-strategy → pricing
- product-marketing-context → product-marketing
- referral-program → referrals
- schema-markup → schema
- signup-flow-cro → signup
- social-content → social

## Consolidations (1)
- page-cro + form-cro → cro (form content in references/form.md)

## Why 2.0?
- Shorter, cleaner skill names
- Consistent naming (no -strategy, -setup, -cro suffixes)
- All cross-references updated across 100+ files

Total skills: 40

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* fix(v2.0): update evals for renamed skills, fix validate script, clear warnings

- Update 32 evals.json files to reference new skill names (page-cro → cro,
  product-marketing-context → product-marketing, etc.) — these were missed
  in the initial v2.0 rename pass since only SKILL.md and marketplace.json
  were updated.
- Fix validate-skills.sh: replace GNU-only `head -n -1` with portable awk
  so frontmatter extraction works on macOS.
- Move Copy Editing Checklist (56 lines) to references/checklist.md to
  bring copy-editing SKILL.md under the 500-line limit (508 → 457).
- Add "see X" pointers to marketing-psychology description for skill
  discovery (cro, pricing, copywriting).
- Update skill-request.yml issue template placeholder (page-cro → cro).

All 40 skills now pass validation with zero warnings.

* fix(v2.0): add evals for 8 missing skills, strip stale frontmatter from cro/form.md

Adds 48 new eval cases (6 per skill) for skills that previously had no evals:
aso, co-marketing, community-marketing, competitor-profiling, directory-submissions,
image, lead-magnets, video. All 40 skills now have eval coverage (251 total cases).

Strips leftover frontmatter from skills/cro/references/form.md — it was inherited
from the old form-cro SKILL.md before consolidation. Reference files don't need
frontmatter.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): rename paid-ads → ads

One more v2.0 simplification — drops the redundant 'paid-' qualifier. Updates
the skill directory, SKILL.md frontmatter, evals.json, README skill table, the
v2.0 rename table in VERSIONS.md (now 17 renames), and all cross-references in
related skills (ad-creative, aso, competitor-profiling, customer-research,
lead-magnets, marketing-ideas) plus the tools/integrations guides.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): bump SKILL.md frontmatter version to 2.0.0 for all 40 skills

VERSIONS.md was already updated to 2.0.0 but the metadata.version field inside
each SKILL.md was still on 1.x. That mismatch would have caused the update-check
flow to perpetually report 'update available' since it compares VERSIONS.md
against local SKILL.md metadata versions.

Caught by codex review (P1).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): add legacy product-marketing-context.md filename fallback

Before this fix, users upgrading from v1.x who had a `product-marketing-context.md`
file would lose automatic context loading — every skill only checked the new
`product-marketing.md` filename. Now all 40 skills also accept the legacy
filename (in either `.agents/` or `.claude/`), and the README migration command
covers both legacy and current filenames.

Caught by codex review (P1 + P2).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): re-sort README skills table alphabetically, fix ads box width

The skills table had a few entries out of alphabetical order from the renames
(co-marketing was after cold-email, ads was at the renamed position).
Re-sorted alphabetically per sync-skills.js. Also padded the 'ads' cell in the
ASCII flow diagram to keep the box width consistent.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* fix(v2.0): document folder cleanup on upgrade, stop sync-skills from re-adding skills array

README upgrade guide now includes:
- A clear cleanup step for stale v1.x skill folders (renamed + consolidated) so
  users don't end up with both old and new folders side-by-side after upgrading
- The full v1 to v2 rename map for reference
- Existing product-marketing-context.md migration steps (preserved)

sync-skills.js no longer (re-)introduces a `skills` array on marketplace.json --
Claude Code's plugin schema discovers skills via the `skills/` directory, and the
explicit array was failing validation. The script now refreshes the description
count and strips the stale array if present.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-05-13 22:05:15 -07:00

7.6 KiB
Raw Blame History

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
Reference in New Issue View Git Blame Copy Permalink