Update to PrePilot Lite

{
  "description": "Use when the user wants to improve landing pages, websites, forms, signup, checkout, onboarding, funnels, conversion paths, message match, trust, friction, or test priorities.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 233
    }
  ],
  "name": "cro-funnel",
  "skill_md_contents": "---\nname: cro-funnel\ndescription: Use when the user wants to improve landing pages, websites, forms, signup, checkout, onboarding, funnels, conversion paths, message match, trust, friction, or test priorities.\n---\n\n# CRO and Funnel\n\n## Use it for\n\n- Landing-page audits\n- Funnel diagnosis\n- Signup or checkout improvement\n- Form and CTA review\n- CRO experiment backlog\n\n## Operating rules\n\n- Use context already present in the conversation before asking for more input.\n- Separate known facts, reasonable assumptions, and unknowns. Do not present assumptions as evidence.\n- When the answer depends on current platform rules, market conditions, pricing, benchmarks, or competitors, verify them with current sources when tools are available.\n- Prefer concrete decisions, examples, and next actions over generic marketing advice.\n- Do not invent campaign performance, customer quotes, research findings, testimonials, rankings, or competitor claims.\n- Keep the requested market, language, funnel stage, audience awareness, budget, and channel constraints visible throughout the work.\n- Diagnose before prescribing.\n- Prioritize clarity, relevance, proof, friction, and risk over visual decoration.\n- Use analytics, recordings, research, or other behavior evidence when available.\n- Do not claim a conversion lift before a valid test.\n\n## Workflow\n\n1. Define page/funnel job, traffic source, audience, desired action, baseline, and known drop-off.\n2. Review value clarity, message match, information hierarchy, proof, objections, CTA, friction, trust, and device context.\n3. Locate the highest-leverage uncertainty or bottleneck.\n4. Propose changes as hypotheses with rationale and evidence.\n5. Prioritize tests by expected impact, confidence, effort, and dependency.\n6. Define instrumentation and decision criteria.\n\n## Output contract\n\n- CRO diagnosis\n- Quick fixes versus testable hypotheses\n- Prioritized experiment backlog\n- Copy or structure recommendations\n- Measurement requirements\n\n## Quality gate\n\n- Recommendations are tied to a specific friction or uncertainty\n- No decorative-only changes presented as CRO\n- High-risk changes require testing\n- Measurement is defined\n\n## Handoff\n\nIf the task is part of a larger marketing request, return the completed deliverable plus the evidence or decisions the next PrePilot skill needs. Do not repeat upstream analysis unless it changes the result.\n"
}