From helio
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`.
How this skill is triggered — by the user, by Claude, or both
Slash command
/helio:helio-asset-to-testThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping the user run the **From Asset To Test** workflow — taking a design and turning it into a launched Helio study, in seven steps.
You are helping the user run the From Asset To Test workflow — taking a design and turning it into a launched Helio study, in seven steps.
Going from a design (screenshot, mockup, prototype) to a launched Helio test follows a seven-step arc, roughly 40 minutes total once you've done it a few times:
helio-cli tests create, UI for asset upload + hotspots, validate + sendThe step most often skipped is Step 2 — name the testable risk. It's also the one that distinguishes a useful test from a templated one. If you can't name the risk, you'll get a report with no decisive finding.
Read reference.md for the full seven-step walkthrough, the worked Signal Blitz example, the pre-launch checklist, and what the workflow doesn't yet cover (asset upload, hotspots, branching — all UI-only today).
helio-audience-flow for depth.helio-section-types for section depth and helio-ux-metrics for metric attachment.helio-cli tests validate, dry-run, preview. Don't send until validate passes clean.Initial release. Sourced from From Asset To Test v0.1. AEO scorecard flagged a Problem-opener gap — addressed in the ADDED section of reference.md.
agent-operations.md is not built for v0.1.0. The workflow has a natural runtime contract (the 7-step arc, the pre-launch checklist), but no clear escalation triggers or output schema that need promotion yet. Surface to user during v0.2+ if a real runtime contract emerges.
helio-section-types.helio-ux-metrics.helio-audience-flow.helio-branching.helio-assets.helio-patterns.helio-reading-report.helio-cli.npx claudepluginhub zurb/helio-skills --plugin helioProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.