opencode-skills-collection 3.1.12 → 3.1.13

package/bundled-skills/offers/references/scarcity-urgency.md

@@ -0,0 +1,175 @@
+# Scarcity & Urgency
+
+The reason to buy now, not later.
+
+This is the most misused offer lever in the industry. Done right, it's a meaningful conversion lift and a respect-the-buyer's-time gesture. Done wrong (fake countdown timers, lies about inventory), it converts once and torches trust permanently.
+
+The repo voice: **only ship real scarcity.** If the scarcity is fake, take it off the page.
+
+## Scarcity vs urgency
+
+| | What it limits | Examples |
+|---|---|---|
+| **Scarcity** | Quantity | Cohort size, seats, inventory, batch, capacity |
+| **Urgency** | Time | Cohort deadline, season, bonus expiry, price increase |
+
+Both work via the same mechanism — they convert "I'll think about it" into "decide now." The difference is what enforces the decision: a limit on how many, or a limit on when.
+
+---
+
+## Honest scarcity formats
+
+The bar: **the constraint has to be real.** Here are the formats that work without lying.
+
+### Capacity-based scarcity
+
+You can only deliver to N customers at a time. The next slot opens when one finishes.
+
+> "We take 2 fractional CMO engagements per quarter. Next slot opens September 15."
+
+Works for: services, agencies, coaching, consulting, anything labor-bound.
+
+### Cohort scarcity
+
+The class starts on a date. After the date, the door closes until the next cohort.
+
+> "Cohort 7 starts October 1. Doors close September 28. Next cohort: January."
+
+Works for: courses, programs, group coaching, anything synchronous.
+
+### Founding-member pricing
+
+The first N buyers get a different price. After that, the price goes up.
+
+> "Founding pricing — $497/mo for the first 50 members. After we hit 50, the price moves to $797/mo."
+
+Works for: SaaS, communities, memberships. Critical: actually raise the price when you hit 50. Otherwise it was a lie.
+
+### Inventory-based scarcity
+
+You have N units. When they're gone, they're gone.
+
+> "We're only producing 100 of the print edition. Sold out, no reprints."
+
+Works for: physical products, limited-run digital, bespoke services.
+
+### Seasonal scarcity
+
+Demand or capacity is seasonal.
+
+> "Tax-prep service for Q1 2026 closes January 15. After that, we focus on existing clients only until April."
+
+Works for: tax, retail Q4, events, education enrollment, anything calendar-bound.
+
+### Bonus expiry
+
+A bonus is available only until X date. The core offer stays the same; the *added value* expires.
+
+> "Order by Friday and the 1:1 onboarding session is included. After Friday, the offer is the same but onboarding is +$497."
+
+Works for: anything with a launch window. Critical: actually remove the bonus when the date hits.
+
+### Price-increase scheduling
+
+The price goes up on a date. Communicate it transparently.
+
+> "On November 1, the program moves from $1,997 to $2,497. Anyone enrolled before November 1 keeps the $1,997 price for life."
+
+Works for: courses, SaaS, communities. Builds credibility because the buyer can verify it later.
+
+---
+
+## Fake scarcity to avoid
+
+Pattern-match and rip these off your page:
+
+### Countdown timers that reset
+
+The timer hits 0:00 and refreshes. The buyer comes back tomorrow, same timer, same urgency. Every buyer who notices loses trust.
+
+If you use a countdown, it ends on a real date. After that date, the discount or bonus actually ends — verifiably.
+
+### "Only 3 spots left"
+
+Especially on digital products where there's no capacity constraint. Especially when the number stays at "3" for weeks.
+
+Use this only when the constraint is real (cohort, capacity, inventory) AND when the number reflects reality.
+
+### Manufactured FOMO
+
+"127 people are looking at this page right now."
+
+These can be honest on some platforms (Booking.com etc.) when they reflect actual traffic. They're dishonest when fabricated. Buyers increasingly assume fabrication.
+
+### Bonus "stacking" that's always available
+
+"This bonus expires at midnight!" — but every page on the site says the same thing at midnight every night.
+
+The bonus has to actually expire, or the line is a lie.
+
+### "Last chance" emails for things that aren't actually last chance
+
+Repeated "FINAL HOURS" emails that send weekly. Every recipient who notices unsubscribes or stops opening.
+
+Use "last chance" once. If you use it multiple times, you've taught your list that "last chance" is meaningless.
+
+---
+
+## Why fake scarcity is uniquely costly
+
+Buyers compare notes. The internet is small.
+
+- One Reddit post about a fake countdown becomes the top Google result for your brand
+- One screenshot of "only 3 left" staying at 3 for a month becomes a viral thread
+- One "last chance" email that wasn't goes into a "marketing fails" newsletter
+
+Real scarcity converts ~the same as fake scarcity at the moment of purchase. The difference shows up at month 6, when fake-scarcity offers are facing trust collapse and real-scarcity offers are still compounding.
+
+If you have to fake it, you don't have an offer-design problem — you have a value-equation problem. Go back to [value-equation.md](value-equation.md).
+
+---
+
+## When scarcity isn't needed
+
+Some offers don't need scarcity:
+
+- **Subscription products** that customers can cancel anytime — the natural friction is low enough
+- **Low-priced impulse products** ($5–30) — the deliberation is short; scarcity feels forced
+- **Premium / luxury brands** — scarcity is implicit in the positioning; explicit scarcity reads as low-status
+- **High-trust audiences** who already know they'll buy — scarcity is unnecessary friction
+
+Don't force scarcity into offers that don't need it. The forced version is worse than no scarcity.
+
+---
+
+## The diagnostic
+
+For an existing offer with weak or no scarcity:
+
+1. **Is there a real constraint?** Capacity, cohort, inventory, season, batch. Find the real one.
+2. **What's the honest version of that constraint?** Write it in plain English.
+3. **Can the buyer verify it?** If you say "founding pricing for the first 50 members," can the buyer see the count?
+4. **Are you willing to actually enforce it?** When the constraint hits, do you have the discipline to actually close the door / raise the price / remove the bonus?
+5. **Where on the page does the scarcity appear?** It should be next to the buy button, not buried.
+
+If you can't find a real constraint, don't ship scarcity. The "trick" of fake scarcity is one of the most expensive shortcuts in marketing. The honest version is usually cheaper than people think — every business has *some* real constraint (capacity, calendar, batch, attention).
+
+---
+
+## Pairing with the rest of the offer
+
+Scarcity is the final lever. It only works if the rest of the offer is strong.
+
+- Strong offer + real scarcity = the buyer decides now
+- Weak offer + scarcity = the buyer decides not to buy, faster
+
+If conversions are bad, scarcity is rarely the first thing to fix. Run the diagnostic from [value-equation.md](value-equation.md) first.
+
+The order is:
+1. Strong dream outcome
+2. Specific perceived likelihood (proof + methodology + guarantee)
+3. Compressed time delay
+4. Reduced effort & sacrifice
+5. *Then* scarcity to get the decision now
+
+Scarcity is the close, not the offer.

package/bundled-skills/offers/references/value-equation.md

@@ -0,0 +1,134 @@
+# The Value Equation
+
+The single most useful frame for offer design. Originated in Alex Hormozi's *$100M Offers*; the underlying idea (multiply benefits, divide costs) is much older — direct-response copywriters have been doing it for a century.
+
+## The formula
+
+```
+              Dream Outcome  ×  Perceived Likelihood of Achievement
+  Value  =  ─────────────────────────────────────────────────────────
+              Time Delay     ×   Effort & Sacrifice
+```
+
+The customer compares the *Value* score to the *Price*. If Value > Price, they buy. If not, they don't, no matter how good the copy is.
+
+**Price is the comparison, not the value.** Most "lower the price" requests are actually "raise the numerator or lower the denominator" requests.
+
+---
+
+## Lever 1: Dream Outcome (numerator)
+
+What the customer *actually* wants — usually one or two levels above the surface ask.
+
+### Surface ask → dream outcome
+
+| Surface ask | Dream outcome |
+|-------------|---------------|
+| "I want a website" | "I want more qualified leads I can close" |
+| "I want to learn copywriting" | "I want to write copy clients pay me $5K+ per project for" |
+| "I want a meal plan" | "I want to feel confident in a swimsuit on a beach in 12 weeks" |
+| "I want fitness coaching" | "I want my back pain gone so I can pick up my kids without thinking about it" |
+| "I want a Notion template" | "I want to feel in control of my work for the first time in years" |
+| "I want to lower CAC" | "I want a marketing engine I can step away from for two weeks without things breaking" |
+
+### How to increase
+
+- **Name it specifically.** "Feel confident in a swimsuit" beats "lose weight." The specific name is the offer.
+- **Connect to the bigger goal.** The dream outcome behind the surface ask is almost always emotional or identity-based.
+- **Show the future state in concrete sensory terms.** What does the morning of day one *after they have it* actually look like?
+
+### Common mistake
+
+Pitching the surface ask. ("Get a website" instead of "get a website that brings you 5 qualified leads a week.") The bigger the buyer's pain, the more important this is — they're not buying a deliverable, they're buying a future.
+
+---
+
+## Lever 2: Perceived Likelihood of Achievement (numerator)
+
+Do they actually believe they'll get the dream outcome? This is the single most underweighted lever — most offers are perfectly fine on the dream outcome side but the buyer just doesn't think it'll work *for them*.
+
+### How to increase
+
+- **Proof** — case studies with names, numbers, before/after metrics, photos. Specific > glossy.
+- **Methodology specificity** — name your process. "The 5-step VAULT framework" beats "our proprietary system." Even if the substance is the same, naming it raises perceived likelihood.
+- **Guarantees** — risk reversal directly raises perceived likelihood (more in [guarantee-design.md](guarantee-design.md)).
+- **Reduce sample-of-one objection** — show people *like them* who got results. "Other people get results but I'm different" is the universal objection.
+- **Pre-empt the failure path** — explicitly address what could go wrong and how you handle it. Builds trust faster than hiding the risk.
+
+### Common mistake
+
+Stacking more features ("we also include X, Y, Z") instead of stacking more proof. Features address dream outcome. Proof addresses likelihood. Most stuck offers need proof, not features.
+
+---
+
+## Lever 3: Time Delay (denominator)
+
+How long from purchase to result. The denominator is doing a lot of work here — slow results don't just feel slow, they erode perceived likelihood (the longer it takes, the less the buyer believes it'll work).
+
+### How to decrease
+
+- **Faster first win** — find the smallest possible early result and engineer it into the first 7 days
+- **Onboarding velocity** — replace a 60-minute kickoff with a 10-minute async intake + Loom send
+- **Front-load the assets** — give the templates / swipe files / decks on day 1, not "throughout the program"
+- **Faster end-to-end timeline** — "in 8 weeks" beats "in 6 months." If you can credibly compress, do.
+- **Quick-start path** — explicit "first thing to do today" so they don't lose momentum
+
+### Common mistake
+
+Promising a faster timeline than you can deliver. The first time you miss it, perceived likelihood for every future buyer drops permanently as the failure story spreads.
+
+---
+
+## Lever 4: Effort & Sacrifice (denominator)
+
+What the buyer pays *besides money* — time, learning curve, decisions, willpower, social risk, opportunity cost.
+
+### How to decrease
+
+- **Done-for-you over do-it-yourself** — DFY tiers move the effort to you. Charge accordingly.
+- **Fewer decisions** — every decision the buyer makes is friction. Bundle, default, recommend.
+- **Lower learning curve** — pre-built templates, examples, defaults. "We did the thinking, you do the executing."
+- **Removed risk** — emotional risk (am I dumb if this doesn't work?), social risk (what will my team think?), opportunity cost (what am I not doing while I do this?). Address all three explicitly.
+- **Async over live** — for many buyers (founders, executives), removing synchronous commitments is huge value
+- **Less willpower required** — automation, accountability, environmental design
+
+### Common mistake
+
+Overestimating how much your buyer *enjoys* the work. They want the outcome, not the process. (Exception: identity-buyers — fitness, learning, mastery. For those, the process *is* part of the dream outcome. Read your buyer.)
+
+---
+
+## Diagnostic: scoring the levers
+
+When an offer is stuck, score each lever 1–10 honestly. The lowest is the binding constraint.
+
+### Quick scoring prompts
+
+- **Dream outcome (1–10)**: Can the buyer picture, in concrete sensory terms, the day after this works? Is the outcome named specifically enough that they can repeat it back to a friend?
+- **Perceived likelihood (1–10)**: Do they have at least three named, comparable proof points? Is the methodology specific enough to repeat? Have you addressed the "but my situation is different" objection?
+- **Time delay (1–10)**: What's the first concrete win, and how soon do they get it? What's the end-to-end timeline? Are there any "delay surfaces" (onboarding lag, asset drip, week-1 friction)?
+- **Effort & sacrifice (1–10)**: How much work does the buyer do? How many decisions? How much learning curve? How much synchronous time? How much emotional/social/opportunity-cost risk?
+
+### Worked example: a stuck $3K copywriting course
+
+Initial scoring:
+- Dream outcome: 6 (`become a better copywriter` — too vague)
+- Perceived likelihood: 4 (one testimonial, no methodology name)
+- Time delay: 5 (6-month course, no first-win mechanic)
+- Effort & sacrifice: 4 (lots of homework, live calls, weekly assignments)
+
+Lowest: effort & sacrifice and perceived likelihood are tied. Pick one (perceived likelihood — easier to move and unblocks more downstream work):
+
+- Name the methodology: "The VAULT framework — 5 angles every winning sales page uses"
+- Add 8 named-customer case studies with before/after copy + revenue numbers
+- Add an "even if you've never written before" cohort with 3 named graduates
+
+After: perceived likelihood goes 4 → 8. Course converts at ~3x baseline. Two months later, attack effort & sacrifice (replace weekly live calls with async + 1 live Q&A).
+
+---
+
+## Key idea to internalize
+
+**The price-vs-value comparison happens in the buyer's head, not yours.** You only know it's working when the buyer can articulate the dream outcome back to you in their own words, and when they don't need to ask "but does this actually work?"
+
+If they're asking either of those questions, you have a value equation problem, not a copy problem.

package/bundled-skills/onboarding/SKILL.md

@@ -0,0 +1,235 @@
+---
+name: onboarding
+description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new...
+risk: unknown
+source: https://github.com/coreyhaines31/marketingskills/tree/main/skills/onboarding
+source_repo: coreyhaines31/marketingskills
+source_type: community
+date_added: 2026-07-01
+license: MIT
+license_source: https://github.com/coreyhaines31/marketingskills/blob/main/LICENSE
+---
+
+# Onboarding CRO
+## When to Use
+
+Use this skill when you need when the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new...
+
+
+You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.
+
+## 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
+
+### 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**: See [references/experiments.md](references/experiments.md)
+
+---
+
+## 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?
+
+---
+
+## Related Skills
+
+- **signup**: For optimizing the signup before onboarding
+- **emails**: For onboarding email series
+- **paywalls**: For converting to paid during/after onboarding
+- **ab-testing**: For testing onboarding changes
+
+## Limitations
+
+- Use this skill only when the task clearly matches its upstream source and local project context.
+- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
+- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

package/bundled-skills/onboarding/evals/evals.json

@@ -0,0 +1,92 @@
+{
+  "skill_name": "onboarding",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me optimize our onboarding flow. We have a project management tool and only 30% of trial users create their first project within the first week. We need to get them to value faster.",
+      "expected_output": "Should check for product-marketing.md first. Should start by defining the activation/aha moment — in this case, creating a first project. Should evaluate the current time-to-value and identify friction points. Should recommend an onboarding flow approach (product-first, guided setup, or value-first). Should apply the checklist pattern (3-7 items for onboarding completion). Should address empty states as opportunities to guide users. Should provide experiment ideas for testing improvements. Should include measurement metrics.",
+      "assertions": [
+        "Checks for product-marketing.md",
+        "Defines the activation/aha moment",
+        "Evaluates time-to-value",
+        "Recommends onboarding flow approach",
+        "Applies checklist pattern with 3-7 items",
+        "Addresses empty states as opportunities",
+        "Provides experiment ideas",
+        "Includes measurement metrics"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "What should our onboarding checklist include? We're a design collaboration tool. Users need to upload a design, invite a team member, and leave a comment to get full value.",
+      "expected_output": "Should apply the checklist pattern. Should include the 3 stated activation actions (upload design, invite team, leave comment). Should recommend 3-7 total items ordered by increasing commitment. Should suggest starting with the quickest win to build momentum. Should recommend progress indicators and completion rewards. Should address what happens when users skip items. Should provide specific UX recommendations for the checklist implementation.",
+      "assertions": [
+        "Applies checklist pattern",
+        "Includes the 3 stated activation actions",
+        "Limits to 3-7 total items",
+        "Orders by increasing commitment",
+        "Starts with quickest win",
+        "Recommends progress indicators",
+        "Addresses skipped items",
+        "Provides UX recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our users sign up but then never come back. like 50% don't even log in a second time. what do we do?",
+      "expected_output": "Should trigger on casual phrasing. Should address this as a stalled users problem. Should apply the handling stalled users framework: identify drop-off points, re-engagement triggers, multi-channel outreach (email, in-app, push). Should investigate root causes: is the first-run experience too complex? Is value not immediately apparent? Is the setup too long? Should recommend immediate improvements to the first session experience. Should suggest multi-channel onboarding (email sequences to bring them back). Should cross-reference emails for re-engagement emails.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies stalled users framework",
+        "Identifies potential root causes for drop-off",
+        "Recommends first-session experience improvements",
+        "Suggests multi-channel onboarding",
+        "Cross-references emails for re-engagement",
+        "Provides specific re-engagement triggers"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "How do we handle the empty state when a new user first logs in? Right now they just see a blank dashboard.",
+      "expected_output": "Should apply the empty states as opportunities guidance. Should recommend turning the blank dashboard into a guided experience: sample data to show what the product looks like populated, a clear first action CTA, contextual tips, or a quick-start wizard. Should provide specific recommendations for empty state design: what to show, what action to prompt, how to reduce the 'blank canvas paralysis.' Should reference patterns by product type if applicable.",
+      "assertions": [
+        "Applies empty states as opportunities guidance",
+        "Recommends alternatives to blank dashboard",
+        "Suggests sample data or templates",
+        "Provides clear first action CTA",
+        "Addresses blank canvas paralysis",
+        "Provides specific empty state design recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Should we use tooltips, a product tour, or a setup wizard for onboarding? What works best?",
+      "expected_output": "Should apply the tooltips/guided tours guidance. Should compare the approaches: tooltips (contextual, on-demand, less intrusive), product tours (guided walkthrough, can overwhelm), setup wizards (structured, ensures key setup steps). Should recommend based on product complexity and onboarding goals. Should note that the best approach often combines elements. Should provide best practices for each: tooltip fatigue avoidance, tour length limits, wizard step count. Should recommend testing different approaches.",
+      "assertions": [
+        "Compares tooltips, product tours, and setup wizards",
+        "Explains when each works best",
+        "Notes that combination approaches often work",
+        "Provides best practices for each",
+        "Addresses tooltip fatigue and tour length",
+        "Recommends testing different approaches"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Our signup form has 8 fields and people keep dropping off. Can you help us fix the signup flow?",
+      "expected_output": "Should recognize this is a signup flow optimization task, not post-signup onboarding. Should defer to or cross-reference the signup skill, which handles signup form optimization, field reduction, and registration flow design. Onboarding-cro covers what happens after signup. Should make this distinction clear.",
+      "assertions": [
+        "Recognizes this as signup flow optimization, not onboarding",
+        "References or defers to signup skill",
+        "Explains that onboarding covers post-signup",
+        "Does not attempt signup form redesign using onboarding patterns"
+      ],
+      "files": []
+    }
+  ]
+}