Results for “test”

Design and execute a social engineering penetration test including phishing, vishing, smishing, and physical pretexting campaigns to measure human security resilience and identify training gaps.

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday.

Walks a running app across routes, states, and interactions to find real bugs, then root-causes, fixes, adds regression tests, and verifies each fix before committing.

Recommends treating central hypothyroidism before performing GH stimulation testing because CH may impair accurate diagnosis of GHD. Use when preparing for GH stimulation testing; triggers include patient requiring GH stimulation test with possible CH.

Recommends against performing dynamic GnRH stimulation testing in the evaluation of hypogonadism, as it provides no additional diagnostic information beyond baseline gonadotropins and sex steroids. Consider this recommendation when evaluating hypogonadism and contemplating GnRH testing.

Pressure-test an idea through persona-driven interrogation until it hardens, proves out, or dies cheaply. Use when the user says 'forge an idea', 'pressure-test this idea', 'stress-test my thinking', or 'harden this idea'.

Use when the team needs a testing plan covering unit, integration, end-to-end, contract, and security-adjacent checks for a product or feature. Trigger on requests to design practical testing strategy before or during implementation.

Write code through a disciplined, BDD-framed Test-Driven Development loop: build a behavior test list, then drive each behavior through red-green-refactor with an enforced observed-failure gate. Use when the user wants to implement, build, or write code test-first, "do TDD", follow "red-green-refactor", drive code from tests, choose the next test by the Transformation Priority Premise (TPP) or ZOMBIES ordering, or grow a feature behavior-by-behavior with tests leading. This skill writes and changes code; it does not produce a test plan document (use automated-test-planning, or manual-test-planning for a plan a person runs by hand), review or audit existing code (use code-review), restructure existing code outside a TDD loop (use refactor), specify what a feature should do (use plan-a-feature), or find the root cause of a bug (use investigate). Runs its loop to completion without pausing for review; to review each behavior as it lands, use pairing.

Writes Behavior-Driven Development scenarios using Gherkin syntax to create executable specifications and test behavior.

Provides guidance and best practices for working with Cypress, covering setup, development, deployment, and troubleshooting.

Strict test-first gate only when explicitly requested or required by repository policy. Do not use for ordinary practical testing.

Choose, run, rerun, or debug MarketingClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.

Master Test Architect and Quality Advisor. Use when the user asks to talk to Murat or requests the Test Architect.

Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP), updating project files, CLI arguments, and CI/CD pipelines for MSTest, NUnit, and xUnit.net.

Identify sensitive data exposure vulnerabilities including API key leakage, PII in responses, insecure storage, and unprotected data transmission during security assessments.

Tests Android inter-process communication (IPC) through intents for vulnerabilities including intent injection, unauthorized component access, broadcast sniffing, pending intent hijacking, and content provider data leakage.

Assess the security of WiFi infrastructure through authorized penetration testing, including weak encryption detection, handshake capture, evil twin attacks, and network segmentation validation.

Systematically assess REST and GraphQL API endpoints against the OWASP API Security Top 10 risks using automated and manual testing techniques.

Test web applications for XML injection vulnerabilities including XXE, XPath injection, and XML entity attacks to identify data exposure and server-side request forgery risks.

Safely change and test untested codebases using techniques from Feathers' 'Working Effectively with Legacy Code': seams, characterization tests, sprout/wrap, and dependency-breaking.

Maps external dependencies and I/O boundaries, generates chaos tests for failure modes like timeouts and connection errors, runs them, and reports resilience gaps with fixes.

Impersonate a user in Apex tests with System.runAs to verify sharing, profile, and permission-set behavior, and to work around mixed-DML errors in test setup.

Orchestrates a multi-agent build session, acting as manager to cut goals into units, spawn implementer and tester subagents, and run test-and-review loops with anti-thrash guardrails.

When the user wants to implement consumer-driven contract testing between microservices using Pact. Also use when the user mentions "pact," "contract testing," "consumer-driven contracts," "CDC testing," "provider verification," or "Pact Broker." For API mocking, see mockoon or wiremock.

Guides users through the specification-driven development workflow, from requirements gathering through specification, test derivation, implementation, and validation.

Use when designing or implementing tests for TypeScript behavior, public types, compiler failures, filesystem or process boundaries, or package-consumer compatibility.

Readability Review

Validates, tests, and scores the quality of skills within a claude-skills ecosystem using Python scripts that check structure, syntax, runtime, and multi-dimensional quality metrics.

Scaffolds an xUnit integration test project for validating Oracle-to-PostgreSQL database migration behavior in .NET solutions, including transaction-rollback base class and seed data manager.

Write the context brief a first-time tester gets before testing an app, tool, codebase, or product — it explains WHAT the thing is and why it exists, while deliberately withholding HOW anything works. The companion to the fresh-eyes skill; the brief it produces is the "starting information" handed to a fresh-eyes tester. Use this whenever the user is preparing a fresh-eyes or first-time-user test and needs the setup material, or says things like "describe my app without giving anything away", "write the context card for the tester", "explain what it is but not how to use it", "set up the newcomer test", "what would the tester be told going in?", or wants a spoiler-free description of their product. Also use it when someone asks for the briefing/intro that a new tester, new hire, or evaluator should receive before first contact with the thing being tested.

Find root causes of bugs, test failures, or unexpected behavior before proposing any fixes.

Review pull requests following Sentry engineering practices, covering security, performance, testing, and design.

Automate Classmarker quiz and test management tasks through Composio's toolkit via Rube MCP.

Executes Binance Spot API requests, including authenticated order management, with support for testnet and mainnet.

Automates browser interactions for web testing, form filling, screenshots, and data extraction.

Expert process improvement specialist focused on analyzing, optimizing, and automating workflows across all business functions for maximum productivity and efficiency