Test design, vulnerability assessment, and quality assurance (13.1K skills)
Check password-manager warnings for exposed passwords and prepare official reset pages for affected accounts. The user enters and submits each replacement, while the skill tracks password changes, authorized saves, and fresh sign-in checks separately.
Review pending code changes for newly introduced security vulnerabilities with clear exploitation paths. Focus on concrete, significant risks and filter likely false alarms, then report affected files, line numbers, severity, attack scenarios, and recommended fixes in Markdown.
Check whether a code change works by running the app and using its real interface. Exercise the intended flow and nearby error cases, capture outputs or screenshots, and report observed behavior with a clear verdict.
Test a changed website or desktop app by operating it directly. Use browser and desktop control tools to compare states before and after actions, checking visible results such as text, input values, selections, and status indicators.
Plan and write tests for changes to agent behavior, favoring integration tests that check components together. Identify key logic changes and user-visible behavior to cover, reuse existing helpers, and keep unit tests in dedicated files.
Test changes interactively in Codex's terminal interface. The skill explains how to launch it, save detailed logs for debugging, and send test messages programmatically with text and Enter submitted separately.
Test agent features across local and remote execution environments using integration tests, which check components working together. Covers Docker and Wine setups, test helpers, and configuration-specific skips for the app-server and exec-server split.
Investigate a video that is not working by downloading it, setting it as the source in a sample component, and running a Remotion render with verbose logs to examine the behavior.
Maintain visual snapshot tests, which compare rendered images, for Remotion’s web renderer. Update existing tests after implementation changes, or add explicitly requested tests with sample components, preview registration, and documentation updates for supported properties.
Guide test writing, updates, and reviews in Remotion by checking observable user outcomes. Choose integration, unit, visual, or end-to-end tests that detect broken workflows, and verify that bug fixes address the original regression.
Investigate intermittent Remotion CI failures, record their error patterns in a tracking issue, and increment counts for repeated failures. Find failed checks even without a supplied pull request, then rerun affected GitHub Actions jobs.
Create integration tests for syncable metadata entities in Twenty itself. Cover invalid inputs, validation errors, and successful data operations, using reusable GraphQL request helpers, error snapshots, and cleanup routines to organize the test suite.
Check a Twenty pull request through real browser scenarios derived from its changes. Verify database effects and server logs alongside visible results, then produce screenshots, a structured verdict, and a report of any failures or uncertainty.
Manage WireMock from the command line to create mock HTTP responses, inspect and count received requests, change scenario states, and record real backend traffic. These operations support integration tests with controlled responses.
Evaluate 3D point clouds and movement trajectories against reference data with CloudAnalyzer. Prepare inputs, measure differences, apply quality thresholds, inspect results visually, and track baseline history for mapping, localization, and perception workflows.
Design evaluation tasks that check whether agents actually complete work. Define requests, simulated user behavior, starting conditions, and verifiable success criteria, then plan difficulty levels, training-data leakage checks, and ongoing maintenance.
Evaluate BMad skills using your agent's configured runner. Compare results with the model alone or another version, grade outputs against criteria, and test whether descriptions trigger correctly, preserving transcripts and evidence for each run.
Add end-to-end tests, which check complete usage flows, and API tests for features that already work. Follow the project's existing test setup to extend automated coverage without introducing a separate testing approach.
Review an Anthropic Cookbook notebook for clear explanations, code quality, technical accuracy, and practical usefulness. It combines automated checks, including exposed credential detection, with a scored report and specific recommendations tied to sections and lines.
Plan and document studies that assess whether an analytical procedure suits its intended use. Select the governing framework, evaluate calibration, accuracy, precision, and detection limits, and compare methods using acceptance criteria defined before data collection.
Turn a Cherry Studio support conversation into an editable draft for a bug report, usability issue, or feature request. The user reviews the wording, chooses any diagnostic data, and submits the report themselves.
Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.
Audit a Python pytest suite for missed faults, uncovered code, slow tests, and unstable results. Deeper checks deliberately alter code to measure detection, while proposed test removals receive separate validation. The skill reports findings without changing tests.
Check whether tests detect faults in changed Python code by deliberately modifying the changed lines. Add tests for missed behavior, confirm which tests fail against the previous code, and report measured evidence alongside any remaining gaps.