qa-detect-ux-pagination

Detects pagination usability defects in web data tables and list views.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-ux-pagination
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-detect-ux-pagination
Source: https://github.com/Luqman-Ud-Din/blackbox-qa-agent/tree/main/skills/qa-detect-ux-pagination
Command: npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-ux-pagination

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill detects common pagination usability defects that make large tables frustrating to navigate, such as missing page-size controls, missing total counts, overcrowded page buttons, and unclear active-page styling.

Core Features & Use Cases

  • Large dataset pagination checks: Flags tables with many rows that lack a rows-per-page selector, so users cannot increase the visible page size.
  • Pagination clarity checks: Identifies paginators that do not show total counts, first/last controls, or an obvious active page indicator.
  • Layout and overflow checks: Catches page-number controls that spill beyond their container or show too many buttons at once instead of a compact pattern.
  • Use case: A product team reviewing a Students table with hundreds of records can quickly spot why users can only see 10 rows at a time and no longer understand how to navigate the dataset efficiently.

Quick Start

Use the qa-detect-ux-pagination skill to inspect the current page for broken or incomplete pagination UI and report any usability gaps you find.

Frequently Asked Questions about qa-detect-ux-pagination

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

FAQPage Schema
How do I check data table pagination for usability issues?

To check data table pagination for usability issues, inspect visible paginator elements to validate that total-count cues, page-size selectors, and active-page indicators are present and functioning correctly.

What causes confusing pagination UX in large dataset tables?

Confusing pagination UX in large dataset tables is caused by missing rows-per-page selectors, absent total record counts, overcrowded page buttons, and unclear active-page styling that prevents efficient navigation.

How do I fix page navigation controls overflowing their container?

To fix page navigation controls overflowing their container, detect layout overflow caused by displaying too many page-number buttons at once and replace them with a compact pagination pattern.

Can I detect missing rows-per-page selectors in web application list views?

Yes, you can detect missing rows-per-page selectors in web application list views by inspecting paginated records to flag large tables that lack page-size controls for adjusting visible rows.

Does pagination usability inspection work without visible first and last page controls?

Pagination usability inspection requires visible paginator elements to function properly, meaning pages lacking first and last controls or active-page indicators will be flagged as having usability gaps.