SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Testing · Frontend · Research / AGENT SKILL
click-test-plan
0
Design first-click and click tests to assess findability and navigation.
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`.
Understand the trade-offs.
SKILL QUALITY
Not yet assessed
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
The full skill.
Original instructions from the publisher’s SKILL.md
# 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