Test design, vulnerability assessment, and quality assurance (13K skills)
Add or extend Paperclip end-to-end evaluations that exercise real browser workflows across the server, database, and runner. Define expected outcomes, check independent evidence, and connect results to the existing reporting pipeline for local or Daytona execution.
Add or extend Paperclip Runner evaluations that test real sessions against a mock control service. Define observable pass conditions, validate cases and run selections, and retain source revisions, evidence, and costs for authorized live runs.
Coordinate Paperclip vulnerability response from confidential report review and private fixes to local testing, CVE identifier requests, advisory publication, and immediate security releases, with human assistance for reporter communication.
Run a project's configured build and test commands, including type checks that detect inconsistent data types. Save pass or fail results, failure details, and logs so an automated editing loop can decide whether verification is complete.
Test community plugin imports in OpenDesign from folders, zip archives, GitHub subpaths, or marketplace entries. Produce a compact receipt showing the plugin name, source type, detected files, and user notes for inspection.
Use a minimal community plugin example to validate OpenDesign marketplace workflows. It serves as a small test case for registry search, installation, and provenance checks that establish where a plugin comes from.
Audit a cloned or rebuilt website before handoff or deployment. Check visual differences, tracking scripts, leftover branding, unintended languages, placeholders, and external dependencies, then report evidence, severity, recommended fixes, and deployment readiness.
Create an employee training deck about recognizing phishing and responding in the first 60 seconds. The HTML slides use a Windows 95-inspired design, with editable content and an adjustable slide count that preserves the template’s visual style.
Review interface animation code for timing, natural movement, responsiveness, rendering performance, and accessibility. Receive a table of specific problems, suggested changes, and reasons, followed by a clear decision on whether the motion meets the review standards.
Inspect and test web pages through a browser automation command-line tool. Navigate, click, enter text, capture screenshots, and extract page details, with a focus on checking local OpenDesign previews and reviewing web app quality.
Review Ant Design tests to decide whether they should be kept, rewritten, or removed. Examine documented behavior and existing coverage to identify duplicate checks or assertions that merely repeat implementation details, with concise reasons for each conclusion.
Verify RuView pipeline output against a reference hash, package evidence for others to check, and review accuracy statements. The skill distinguishes measured, claimed, and synthetic results and requires real device logs for hardware validation.
Review Homecore plugins by distinguishing built-in native code from external Wasm packages. Check signatures, publisher identity, paths, resource limits, and host permissions, then use the documented verification command to assess the plugin’s trust boundaries.
Review and strengthen security in claude-flow v3 by addressing dependency risks, password hashing, credential generation, input validation, file paths, and command execution. It also guides threat modeling and tests for security-critical code.
Review Home Assistant migration behavior for input validation, configuration preservation, and output that does not overwrite existing files. Check storage schema versions, keep secrets out of diagnostics, and identify incomplete automation or integration behavior.
Run the smallest relevant Homecore test profile against a specified repository checkout. Choose core, Wasmtime, HAP, or full tests to validate the selected software paths, while keeping the limits of passing results clear.
Verify RuView changes with Rust and Python tests, output hashes that detect processing changes, and firmware hash records. Packages test logs and audit evidence into a witness bundle that recipients can check with a single command.
Check code and agent outputs, track reliability scores, and roll back changes that fail a chosen threshold. Includes quality reports, live monitoring, and integration with automated build and deployment workflows.
Control a running iOS Simulator on macOS from Orca’s live device pane. Perform taps, gestures, typing, button presses, and rotation, and inspect the interface element hierarchy to check app changes in the simulator.
Control an Android phone or emulator through Orca using adb, the Android device connection tool. View the device live, perform touch and keyboard actions, install and launch apps, inspect interface structure, and read logs.
Build features or fix bugs by writing a small test first, checking that it fails for the expected reason, and making the smallest code change needed. Run related tests and review the changes for unintended effects.
Organize GitHub issues and pull requests found during quality assurance testing. Apply release tracking labels, classify bugs by four severity levels, and label multiple findings while keeping documentation issues and feature requests outside the severity scheme.
Measure Storybook startup from launching the process to displaying the first story. Separate server readiness from browser rendering, summarize repeated runs, and compare versions or feature flags to investigate slower startup.
Retrieve current cyber threat data, including malware indicators, addresses of attacker control servers, and vulnerabilities known to be exploited. Filter by threat type, source, severity, and date to identify relevant threats for review and reporting.