click-test-plan — Claude Code skill: plan click and findability tests
Turns a findability question into a test plan: where users click first and whether they locate items in your navigation. Useful when a design is ready but untested.
npx skills add Owl-Listener/designer-skills --skill click-test-plan -a claude-codeWhat click-test-plan does
The skill structures four kinds of checks: first-click, full click path, navigation, and five-second recall. Each one comes back as a plan with an objective, stimuli, tasks, success criteria and participant count.
Tasks are written without UI hints, and click target areas get defined before testing starts. For quantitative runs the skill suggests 20 to 50 participants, and treats a first-click success rate above 65% as a sign of good findability. That number is a benchmark, not a gate — if your results land well under it, the navigation likely needs work.
A separate test-scenario skill in the same repository covers full task-based observation; this one stays on clicks. Install runs through npx skills add, so Node.js is required.
What it helps with
- plan a first-click test around a screen design
- check whether users find a section through the nav
- compare two design variants on identical tasks
- set success criteria before running the test
- spot where users hesitate before clicking
Example prompts for the agent
- draft a click test plan for the new settings page
- test whether users find the email change option — first-click only
- compare two navigation variants using the same tasks
How to install click-test-plan
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill click-test-plan -a claude-code2Manually: put the files in place
~/.claude/skills/click-test-plan/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/click-test-plan/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill click-test-plan -a codex2Manually: put the files in place
.agents/skills/click-test-plan/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill click-test-plan -a cursor2Manually: put the files in place
.cursor/skills/click-test-plan/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Owl-Listener/designer-skills click-test-plan2Manually: put the files in place
.github/skills/click-test-plan/SKILL.md1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill click-test-plan -a gemini-cli2Platform CLI
gemini skills install https://github.com/Owl-Listener/designer-skills --path prototyping-testing/skills/click-test-planManually: put the files in place
.devin/skills/click-test-plan/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill click-test-plan -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about click-test-plan
How do I install click-test-plan in Claude?
Run npx skills add Owl-Listener/designer-skills --skill click-test-plan -a claude-code. The skill lands at ~/.claude/skills/click-test-plan/SKILL.md.
What does click-test-plan do?
It designs first-click, click-path, navigation and five-second tests. Each plan includes an objective, stimuli, tasks, success criteria and participant requirements.
How is it different from test-scenario?
click-test-plan covers clicks and element findability only. For full task-based observation, use test-scenario.
Source text
SKILL.md · MIT
--- name: click-test-plan description: Design first-click and click tests for findability and navigation. Use when testing whether people can locate something. For full task-based observation, use `test-scenario`. --- # Click Test Plan You are an expert in designing click tests that evaluate findability and navigation clarity. ## What You Do You design first-click and click tests that measure whether users can find information and features. ## Test Types - **First-click test**: Where do users click first for a given task? - **Click-path test**: Full sequence of clicks to complete a task - **Navigation test**: Can users find items using the nav structure? - **Five-second test**: What do users remember after 5 seconds? ## Test Plan Structure ### 1. Objective What navigation or findability question are you answering? ### 2. Stimuli Screen designs or prototypes to test. Identify which pages/states to show. ### 3. Tasks Clear, goal-oriented tasks without UI hints. Example: 'Where would you click to change your email address?' ### 4. Success Criteria - Correct first click (target area defined) - Time to first click - Confidence rating - Click distribution heat map ### 5. Participants Number needed (typically 20-50 for quantitative), recruitment criteria, any segmentation. ## Analysis - First-click success rate (above 65% generally indicates good findability) - Click distribution patterns - Time analysis (hesitation indicates confusion) - Confidence correlation with accuracy ## Best Practices - Test one task per screen - Define click target areas before testing - Use realistic content, not lorem ipsum - Don't give hints in task wording - Compare alternative designs with same tasks
© Owl-Listener · MIT · Owl-Listener/designer-skills