verify-quality-tournament-wizard-ui

Verifies the quality-tournament wizard UI end-to-end in a browser against the local dev stack.

7|12|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/OpenRouterTeam/docs --skill verify-quality-tournament-wizard-ui-openrouterteam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-quality-tournament-wizard-ui
Source: https://github.com/OpenRouterTeam/docs/tree/main/.agents/skills/verify-quality-tournament-wizard-ui
Command: npx skills add https://github.com/OpenRouterTeam/docs --skill verify-quality-tournament-wizard-ui-openrouterteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After every code push to the quality-tournament wizard, engineers need browser-level proof that the UI still works, but manual verification across many surfaces is slow and easy to skip. This Skill sequences the verification phases and routes each one to the sub-skill that owns it, producing screenshots and recordings as PR evidence. ## Core Features & Use Cases - Phase orchestration: Sequences environment setup, data seeding, per-ticket feature checklists, and cross-cutting scenarios, delegating each to its dedicated sub-skill. - Evidence capture: Collects screenshots at every checkpoint plus ffmpeg recordings for flow-level changes, ready to attach to the PR description. - Use Case: After modifying the quality-tournament configure step, run this Skill to walk the wizard in a real browser with agent-browser, verify the ECO-1043 checklist items, and attach the captured evidence before marking the PR ready. ## Quick Start Verify the quality-tournament wizard UI end-to-end on my local dev stack and capture screenshots for my PR.

Frequently Asked Questions about verify-quality-tournament-wizard-ui

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

FAQPage Schema
How do I verify the quality-tournament wizard UI before submitting a PR?▼

Invoke this Skill after pushing changes to the quality-tournament directory. It sequences environment setup, data seeding, feature checklists, and scenarios, delegating each phase to a sub-skill and producing screenshots and recordings for the PR description.

What tools are needed for browser-based UI verification of the wizard?▼

Verification uses agent-browser to drive a real browser against the local dev stack, dev Clerk login with an admin gate grant, and ffmpeg for recording flow-level changes. The local dev stack must be running first.

Can I run a real tournament locally with mock data?▼

Yes, the run-quality-tournament-locally sub-skill handles actual tournament runs with mock transaction and prompt-hydration injection, or real API calls on cheap models. All mock injection code is local-only and must be reverted before committing.

Does this Skill replace e2e or unit tests?▼

No, it performs browser-level verification on top of existing e2e and unit tests. It only verifies the UI and captures evidence; it does not implement or fix quality-tournament product code.

How do I add checks for a new quality-tournament surface?▼

Extend the checklist in the verify-quality-tournament-features sub-skill, or add a scenario to verify-quality-tournament-scenarios, in the same PR that introduces the new surface.