setup-quality-tournament-env

Configures local dev stack, admin access, and evidence capture for quality-tournament verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a local environment to verify the quality-tournament wizard UI requires many manual steps: starting the dev stack, signing in with a dev Clerk session, granting admin rights in local Postgres, connecting a browser automation agent, and capturing screenshots and screen recordings as evidence. This Skill walks through that entire setup so verification can begin without guesswork. ## Core Features & Use Cases - Dev stack startup: Starts the Tilt-based local environment and waits for the api, api-kv-cron, and frontend-api resources to become ready. - Admin gate grant: Grants is_admin to the signed-in Clerk user in local Postgres via bun run db:test-user, then verifies the /labs/quality-tournament page stays accessible after the 60-second cache expires. - Evidence capture: Takes agent-browser snapshots and screenshots, and records the X display with ffmpeg through a FIFO for a graceful, seekable MP4 (avoiding agent-browser record, which drops the Clerk session). - Use Case: Before running UI verification of the quality-tournament wizard, use this Skill to get an authenticated admin session in agent-browser and produce screenshots plus a screen recording to embed in a PR description. ## Quick Start Set up the local quality-tournament verification environment with an admin-signed-in browser session and start capturing screenshot and video evidence.

Frequently Asked Questions about setup-quality-tournament-env

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

FAQPage Schema
How do I set up local environment for quality-tournament UI verification?▼

Start the dev stack with `bun run dev:up`, wait for the api, api-kv-cron, and frontend-api Tilt resources to be ready, sign in with a dev Clerk session, grant admin in local Postgres, and connect agent-browser on port 29229.

How to grant admin access to a Clerk user in local Postgres?▼

Run `bun run db:test-user --user-id <clerk_user_id> --admin true` against the already-synced local user. The `is-admin-v2` cache lasts 60 seconds, so wait over a minute before reloading `/labs/quality-tournament` to confirm access.

Why does agent-browser record lose the Clerk session?▼

The `agent-browser record` command spins up a fresh browser context that drops the Clerk session, so recordings show the signed-out redirect to `/`. Screen-record the X display with ffmpeg instead while driving the authenticated context.

How do I stop ffmpeg screen recording without corrupting the video?▼

Stop ffmpeg gracefully by writing `q` through a FIFO held open on a file descriptor. Sending SIGINT or SIGTERM leaves a VP9 webm with `duration=N/A` and scrambled timestamps, while the FIFO quit produces a finalized, seekable MP4.

Where are quality-tournament runs stored locally?▼

Tournament runs are stored in the browser via zustand persisted to IndexedDB under the key `or-quality-tournament-v1`. Switching browsers or clearing site storage loses the run history.