User Research
Choose a research method from the decision it must inform; recruit relevant experience and preserve evidence through synthesis.
Observe people completing meaningful tasks; use neutral instructions and record assistance consistently.
---
name: knoveya-usability-testing
description: "Observe people completing meaningful tasks; use neutral instructions and record assistance consistently. Use for matching product work."
---
# Usability Testing
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Observe people completing meaningful tasks; use neutral instructions and record assistance consistently.
Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.
## Acceptance check
Task outcomes distinguish unaided success, assisted success, and failure.
## Example task
Test whether someone finds the export control without hints.
## Report
State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.Copy the full block, including its frontmatter, into a new folder named knoveya-usability-testing as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-usability-testing/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.
This is an independent Knoveya skill. No files are installed by this website.
Test whether someone finds the export control without hints.
Task outcomes distinguish unaided success, assisted success, and failure.
Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.
The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.