cubetiq/qa
foundry/modules/qa/SKILL.md
Consolidated QA capability with three modes: harness, web, and mobile.
$ install --global
skillsauthnpx skillsauth add cubetiq/cubis-foundry qaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 9:51 AM64.0s3 files scanned
SKILL.md
- name:
- qa
- description:
- Consolidated QA capability with three modes: harness, web, and mobile.
- license:
- MIT
- author:
- cubis-foundry
- version:
- 1.0
- compatibility:
- Claude Code, Codex, GitHub Copilot, Gemini CLI, Antigravity
QA
Purpose
Provide one capability for repeatable Foundry QA work across UI harness evaluation, live web-browser validation, and Flutter mobile testing. This consolidates the prior ui-testing-harness, playwright-web-qa, and flutter-mobile-qa skills into one routing surface with explicit operating modes.
Modes
- harness: Build or review the Foundry-owned UI evaluation harness, scenarios, scorecards, and anti-slop gap reports.
- web: Run charter-driven browser QA with deterministic Playwright evidence.
- mobile: Run Flutter-focused Android QA with structured screenshot, UI-tree, and log evidence.
When to Use
- Foundry needs repeatable UI-quality benchmarks instead of one-off screenshots.
- A real web flow must be checked with deterministic browser artifacts.
- A Flutter app needs smoke, regression, or crash triage on an emulator or device.
Instructions
- Choose the mode up front because harness planning, browser QA, and mobile QA have different evidence paths and success criteria.
- Use
harnessfor system-level UI quality work including style atlases, benchmark scenarios, and Foundry gap reporting. - Use
webfor runtime browser validation when the task needs a charter, explicit URL state, and report-ready artifacts. - Use
mobilefor Flutter and Android execution with readiness checks, baseline captures, and controlled retries. - Tie every verdict to evidence such as screenshots, DOM snapshots, UI trees, or logs rather than impressions.
- Keep artifacts local and deterministic so failures can be reviewed and rerun without ambiguity.
- Escalate from runtime QA to harness work only when repeated failures show a system gap rather than a one-off bug.
Output Format
Deliver:
- Chosen mode
- Charter or scenario summary
- Execution log
- Assertions and evidence paths
- Risks and recommended fixes
References
| File | Load when |
| --- | --- |
| ../web-testing/SKILL.md | Running a live charter against a web app with Playwright evidence. |
| ../android-emulator-testing/SKILL.md | Running Android QA with screenshots, UI trees, and log capture. |
| ../ios-simulator-testing/SKILL.md | Running iOS simulator QA with equivalent mobile evidence. |
Related Skills
cubetiq/deep-research
tools
VerifiedTrustedCommunity
Use when investigating latest vendor behavior, comparing tools or platforms, verifying claims beyond the repo, or gathering external evidence before implementation.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/database-design
documentation
VerifiedTrustedCommunity
Use when designing database schemas, normalization strategies, indexing plans, query optimization, and migration workflows for relational, document, or hybrid data stores.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/csharp-best-practices
development
VerifiedTrustedCommunity
Use when writing, reviewing, or refactoring modern C#/.NET code, including minimal APIs, records, async streams, pattern matching, DI lifetimes, and memory-efficient performance tuning.
1SKILL.mdUpdated Apr 4, 2026
cubetiq/code-review
development
VerifiedTrustedCommunity
Use when conducting code reviews, building review checklists, calibrating review depth, providing structured feedback, or establishing team review practices. Covers review methodology, feedback patterns, automated checks, and batch review strategies.
1SKILL.mdUpdated Apr 4, 2026