1{
2  "skill_name": "signup-flow-cro",
3  "evals": [
4    {
5      "id": 1,
6      "prompt": "Audit our signup flow. We have a 3-step process: Step 1 asks for email, password, and full name. Step 2 asks for company name, company size, role, and industry. Step 3 asks for use case and how they heard about us. Current completion rate is 45%.",
7      "expected_output": "Should check for product-marketing-context.md first. Should identify the flow type (likely B2B SaaS trial). Should apply the core principles: minimize required fields (which of these are genuinely needed before they can use the product?). Should evaluate each step: Step 1 is reasonable, Step 2 fields are mostly deferrable to progressive profiling, Step 3 is entirely deferrable. Should recommend cutting to Step 1 only or at most 2 steps. Should provide audit findings in structured format (Issue, Impact, Fix, Priority). Should include Quick Wins, High-Impact Changes, and Test Hypotheses.",
8      "assertions": [
9        "Checks for product-marketing-context.md",
10        "Identifies flow type",
11        "Applies minimize required fields principle",
12        "Evaluates each field for necessity",
13        "Recommends deferring most Step 2 and all Step 3 fields",
14        "Provides findings in structured format",
15        "Includes Quick Wins, High-Impact Changes, Test Hypotheses"
16      ],
17      "files": []
18    },
19    {
20      "id": 2,
21      "prompt": "Should we add Google and Microsoft SSO to our signup page? We're a B2B project management tool and currently only have email/password signup.",
22      "expected_output": "Should apply the social auth options guidance. For B2B, should recommend Google and Microsoft as the primary SSO options (matching the B2B recommendation). Should explain benefits: higher conversion (less friction), pre-verified email, faster onboarding. Should recommend placing SSO prominently (often higher conversion than email). Should address implementation considerations: clear visual separation from email signup, button copy ('Sign up with Google' not just Google icon), consider which option to emphasize based on audience.",
23      "assertions": [
24        "Applies social auth options guidance",
25        "Recommends Google and Microsoft for B2B",
26        "Explains conversion benefits of SSO",
27        "Recommends prominent placement",
28        "Addresses visual separation from email signup",
29        "Provides implementation recommendations"
30      ],
31      "files": []
32    },
33    {
34      "id": 3,
35      "prompt": "our signup form is just email and password but we still only get 35% of visitors to complete it. what else could be wrong?",
36      "expected_output": "Should trigger on casual phrasing. Should investigate beyond just form fields since the form is already minimal. Should apply trust and friction reduction guidance: is there a 'No credit card required' message? Privacy assurance? Testimonial near the form? Should check form-level issues: error handling, password requirements clarity, submit button copy. Should also look at pre-form factors: is the value proposition clear? Is the page optimized? (cross-reference page-cro). Should provide diagnostic checklist and recommendations.",
37      "assertions": [
38        "Triggers on casual phrasing",
39        "Investigates beyond form fields",
40        "Applies trust and friction reduction",
41        "Checks for 'No credit card required' messaging",
42        "Checks error handling and password UX",
43        "Considers pre-form factors (value prop, page CRO)",
44        "Provides diagnostic checklist"
45      ],
46      "files": []
47    },
48    {
49      "id": 4,
50      "prompt": "We require email verification before users can access the product. Is that hurting our conversion? Should we change it?",
51      "expected_output": "Should apply the verification flows guidance. Should explain that requiring verification before product access does create friction and likely reduces activation. Should recommend alternatives: delay verification until needed (let users explore first), magic link as alternative to password, let users start while verification is pending. Should discuss when email verification IS required (compliance, preventing abuse). Should provide specific recommendations for improving the verification experience if kept.",
52      "assertions": [
53        "Applies verification flows guidance",
54        "Explains verification friction impact",
55        "Recommends delaying verification",
56        "Suggests letting users explore while pending",
57        "Discusses when verification is required",
58        "Provides improvements if verification is kept"
59      ],
60      "files": []
61    },
62    {
63      "id": 5,
64      "prompt": "What experiments should we run on our signup page? We want to improve our trial signup rate.",
65      "expected_output": "Should apply the experiment ideas section. Should provide experiments across categories: form design experiments (layout, field count, SSO), copy and messaging experiments (headline, CTA text, trust elements), trial and commitment experiments (credit card required vs not, trial length), and post-submit experiments. Should prioritize experiments by likely impact. Should cross-reference ab-test-setup for proper experiment design.",
66      "assertions": [
67        "Applies experiment ideas section",
68        "Covers form design experiments",
69        "Covers copy and messaging experiments",
70        "Covers trial and commitment experiments",
71        "Prioritizes by likely impact",
72        "Cross-references ab-test-setup skill"
73      ],
74      "files": []
75    },
76    {
77      "id": 6,
78      "prompt": "Users sign up fine but then never activate. Only 20% complete onboarding. What do we do?",
79      "expected_output": "Should recognize this is a post-signup onboarding problem, not a signup flow problem. Should defer to or cross-reference the onboarding-cro skill, which handles post-signup activation and onboarding optimization. Signup-flow-cro covers getting users through the signup form, not what happens after.",
80      "assertions": [
81        "Recognizes this as post-signup onboarding, not signup flow",
82        "References or defers to onboarding-cro skill",
83        "Explains signup-flow-cro covers the signup form, not post-signup"
84      ],
85      "files": []
86    }
87  ]
88}
89