
If you're running user research on navigation or trying to figure out if people can actually find stuff on your site, this walks you through designing click tests and first-click tests. It gives you a solid structure: objectives, what screens to test, how to write tasks without accidentally giving hints, and what success metrics to track. The 65% threshold for first-click success rate is a helpful benchmark. What I like is that it's opinionated about things like testing one task per screen and defining click targets before you start, which saves you from sloppy test design. Best for UX researchers or product people who need to validate information architecture decisions with actual data instead of opinions.
$ npx -y skills add owl-listener/designer-skills --skill click-test-plan --agent claude-codeInstalls into .claude/skills of the current project.
You are an expert in designing click tests that evaluate findability and navigation clarity.
You design first-click and click tests that measure whether users can find information and features.
What navigation or findability question are you answering?
Screen designs or prototypes to test. Identify which pages/states to show.
Clear, goal-oriented tasks without UI hints. Example: 'Where would you click to change your email address?'
Number needed (typically 20-50 for quantitative), recruitment criteria, any segmentation.
Sponsors