brikko-studio-qa-testing

What problem does it solve?

Manually running, monitoring, and debugging QA test suites for Brikko Studio's qa-lab and qa-channel is time-consuming and prone to human error, especially when working across multiple test lanes, LLM models, and live test environments.

Core Features & Use Cases

• End-to-end test execution: Run full qa-lab test suites across mock and live OpenAI lanes, with support for OpenTelemetry smoke tests and configurable matrix profiles for different testing scopes.
• Scenario debugging and extension: Debug failing test scenarios, extend the QA suite with new end-to-end test cases, and run character/persona evaluations across multiple LLM backends to validate response consistency and style.
• Secure credential management: Handle QA secrets for Telegram and Convex live test environments via integrated 1Password workflows, eliminating the need to manually manage sensitive test credentials. Use case: A QA engineer working on Brikko Studio can use this skill to run a full live QA suite, debug a failing E2E messaging scenario, and validate character consistency across 8 different LLM providers without manually constructing test commands or handling sensitive credentials.

Quick Start

Use the brikko-studio-qa-testing skill to run the full live QA suite for the current branch and share the pass/fail counts and test artifact paths with me.