helio

Use this skill when the user is asking about Helio at the platform level — what Helio is, what it does, what plans cost, how to choose a plan, capability tour, or how Helio fits the Glare workflow. Triggers — "what is Helio," "how does Helio work," "Helio pricing," "Helio plans," "Pilot vs Scale vs On Demand vs Business," "what can Helio do," "how do I get started with Helio," "build → recruit → read," "Helio capabilities," "where does Helio fit," "Helio panel," "Helio + Glare." Do NOT use when the user wants section type depth (use `helio-section-types`), audience details (use `helio-audience-flow`), UX metric specifics (use `helio-ux-metrics`), the AI heuristic evaluator (use `helio-design-analysis`), or the CLI/MCP surfaces (use `helio-cli` / `helio-mcp`). For test design, use `helio-asset-to-test`. For synthesis, use `helio-reading-report`.

Use this skill when the user is going from a design (screenshot, mockup, prototype) to a launched Helio test — building the test, validating it, and sending it. Triggers — "how do I build a test," "from asset to test," "set up a Helio test," "what test should I run," "test build workflow," "validate before launch," "dry-run a test," "how do I structure my questions," "Signal Blitz worked example," "pre-launch checklist," "naming the risk," "picking a template," "audience for my test," "questions JSON," "send test." Do NOT use when the user wants section type depth (use `helio-section-types`), metric attachment specifics (use `helio-ux-metrics`), audience setup specifics (use `helio-audience-flow`), or branching configuration (use `helio-branching`). For reading the resulting report, use `helio-reading-report`. For recognizing test shapes by pattern, use `helio-patterns`.

Use this skill when the user is working with assets in Helio — uploading images, video, audio, linking Figma prototypes, managing the media library, or troubleshooting asset delivery. Triggers — "Helio assets," "upload image," "upload video," "upload audio," "image variants," "signed URLs," "Figma integration," "Figma prototype URL," "Figma OAuth," "Figma sync," "media library," "asset library," "asset expired," "asset broken," "alt text," "video bitrates," "audio transcoding," "asset delivery." Do NOT use when the user wants section type spec (use `helio-section-types`), test build workflow (use `helio-asset-to-test`), or licensing/billing (use `helio-licensing`).

Use this skill when the user is configuring how Helio recruits participants for a study — picking an audience type, setting demographics or segments, uploading customer lists, configuring intercept, or running an API audience. Triggers — "audience for my test," "Helio panel," "targeted demographics," "advanced segments," "customer list upload," "intercept survey," "API audience," "AI audience," "AI personas," "how do I send a test," "send test flow," "launch validation," "panelist availability," "audience fanout," "Order More Customer Lists," "audience cost." Do NOT use when the user wants test design (use `helio-asset-to-test`), section types (use `helio-section-types`), filtering the report after launch (use `helio-report-filtering`), or licensing/billing (use `helio-licensing`).

Use this skill when the user is configuring conditional routing in a Helio study — branching participants based on their answers, screening / disqualifying, redirecting at end-of-test, or troubleshooting why a branch isn't firing. Triggers — "Helio branching," "conditional routing," "screener," "disqualify participants," "jump to section," "end test with custom message," "redirect URL after test," "branching from a choice," "branching on best/worst answer," "hotspot branching," "Branching and quotas," "Branching and UX metrics," "Branching and Conditional Follow-ups," "Why is my branch not firing," "multi-select branching." Do NOT use when the user wants conditional follow-ups inline (those live in `helio-section-types`), section type details (use `helio-section-types`), or test build workflow (use `helio-asset-to-test`).