picky-tester

Simulate diverse user personas to generate structured friction logs with screenshots.

5|Updated Jan 28, 2026

Search Tags:#automation #testing #qa #ui-testing #chrome-devtools-mcp #friction-logs

Ready to run

npx skills add https://github.com/kiruna-labs/picky-skills --skill picky-tester

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: picky-tester
Source: https://github.com/kiruna-labs/picky-skills/tree/main/picky-tester
Command: npx skills add https://github.com/kiruna-labs/picky-skills --skill picky-tester

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ultra-thorough QA testing from a real-user perspective, exposing edge cases, confusing flows, and accessibility gaps before release.

Core Features & Use Cases

Simulates 13 diverse user personas to exercise forms, navigation, and interactive elements.
Generates structured friction logs with severity, file:line references, and screenshots for easy triage.
Triggers include "test this app", "QA testing", "test as a real user", and "picky tester" to start tests.

Quick Start

Invoke the picky-tester against your app using the trigger phrases provided earlier to start a friction-log QA run.

Frequently Asked Questions about picky-tester

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate end-to-end black-box QA testing for web apps?▼

Automate end-to-end QA testing by simulating 13 diverse user personas to exercise multi-step flows, forms, and dynamic UI, which generates structured friction logs with screenshots for actionable remediation.

What is a friction log and how does it help with UI testing?▼

A friction log is a structured QA report detailing navigation issues, accessibility gaps, and edge cases with severity levels and file:line references, helping teams triage and fix confusing UI flows before release.

How do I test web app accessibility and navigation using diverse user personas?▼

Test web app accessibility and navigation by simulating diverse user personas that interact with forms and dynamic UI, systematically surfacing friction and accessibility gaps across different user contexts.

Can I generate structured QA reports with screenshots and file references?▼

Yes, you can generate structured QA friction logs that include severity ratings, file:line references, and screenshots, providing exhaustive coverage and actionable findings suitable for developer hand-off.

Does this QA testing approach work with dynamic UI and multi-step forms?▼

Yes, this QA testing approach is designed for web apps with dynamic UI and multi-step flows, applying deterministic test steps to ensure exhaustive coverage of interactive elements and forms.

When should I use black-box QA testing instead of unit tests?▼

Use black-box QA testing when you need to expose edge cases, confusing flows, and accessibility gaps from a real-user perspective before release, whereas unit tests only validate individual code components.