Test design, vulnerability assessment, and quality assurance (13K skills)
Test mastracode’s terminal interface in Konsole, covering model setup, conversation switching, task state isolation, and display issues. The guide combines interactive checks with scripted rendering tests and troubleshooting steps for common build and configuration problems.
Run smoke tests, or basic operational checks, for Mastra projects locally or in staging and production. Verify Studio screens, agents, tools, workflows, traces, and memory, then report results, blockers, and skipped checks.
Review code for security vulnerabilities using a checklist covering unsafe input, authentication, access permissions, secrets, and data exposure. Classify findings into four severity levels to distinguish exploitable flaws, issues needing investigation, and smaller improvements.
Create Vitest tests for Mastra playground features using MSW to simulate network responses. Exercise the real client SDK, React Query cache, and components with typed sample data to check loading, access conditions, redirects, and errors.
Reproduce Mastra Code bugs with a real model and compare timestamped logs across network, streaming, execution, and terminal interface layers. Use the evidence to locate timing problems, incorrect token rates, flicker, or stuck status displays.
Write integration tests for core error processors by simulating API failures with a mock model. Check retry attempts, changes to conversation messages, and streamed responses, with guidance on test setup and diagnosing empty output.
Explore an existing Vitest 3.2 JSON test report to count results, search failed tests, and inspect file errors. Review original diagnostic details and keep tentative explanations separate from evidence, without launching tests.
Classify outstanding pull request CI failures, automated checks run on code changes, using logs and changed files. Produce JSON decisions recommending a rerun, a comment, or no action, and identify specific nondeterministic tests when evidence supports it.
Verify a qwen-code pull request in an isolated environment by comparing its behavior with a control build and running focused tests. Produce a report and machine-readable verdict that distinguish measured results from areas left untested.
Automate terminal interactions and capture screenshots before and after commands run. Define scenarios in TypeScript to review CLI appearance, document command flows, or record changing output such as progress bars, with optional animated GIFs.
Test Qwen Code CLI behavior from model requests through tool execution. Reproduce bugs, check terminal interactions and MCP tool connections, and inspect API logs using real models or mock servers for controlled scenarios.
Stabilize a test that fails and then passes on the same commit. Apply a minimal fix to timing, randomness, clock behavior, or shared resources while preserving assertions, then verify it through repeated runs.
Compare a feature implemented in Qwen Code with Codex or Claude Code under the same scenario. Capture communication and terminal records, inspect tool definitions and outputs, and guide fixes toward matching observable behavior.
Test Qwen Code through realistic keyboard interactions in tmux, a terminal session tool. Capture readable screen snapshots at each step and produce a report documenting dialogs, commands, outcomes, and observed side effects.
Verify a bug with a test that fails before the fix, passes afterward, and fails again when the fix is temporarily removed. Record actual results to show that the test detects the defect and the change addresses it.
Compare repeated agent evaluations before and after a change to distinguish performance drops from random variation. Scripts check tool calls, identify inconsistent cases, and provide a CI gate that blocks merging when specified regression conditions are met.
Set up Playwright browser tests, generate cases from specifications or URLs, and review coverage gaps. Diagnose tests that fail inconsistently, migrate Cypress or Selenium suites, and optionally connect TestRail and BrowserStack for results and browser testing.
Prepare SaaS teams for SOC 2 audits by mapping evaluation criteria to controls, the measures used to manage risk. Build control matrices, track supporting evidence, identify gaps, and assess readiness for Type I or Type II.
Plan ISO 27001 information security audits, review evidence that security controls work, and document findings. The skill also helps classify failures, track corrective actions, and prepare documentation for certification audits.
Diagnose failing or intermittent Playwright tests by reproducing errors and examining execution traces. Classify the cause, apply a targeted fix, and run the test ten times to check stability, with recommendations to prevent recurrence.
Support information security management for healthcare and medical technology companies. Structure an ISO 27001 management system, assess risks, review security controls, and prepare audit evidence, gap reports, and incident response procedures.
Create Playwright tests from a user story, page URL, component path, or feature description. The skill follows existing project conventions, covers expected behavior and error cases, creates supporting files when needed, and runs the tests to check results.
Review Playwright browser tests against 20 quality checks to find unreliable patterns and missing coverage. Get scores for each file, prioritized findings, and corrected code for critical issues.
Summarize Playwright test results in a Markdown report with failures, timings, and tests that pass only after retries. Use configured reporting destinations and compare earlier reports when historical results are available.