jovd83

Use when Codex needs to design, implement, run, document, or report Rest Assured API tests for REST services, contract-driven service tests, JUnit 5 automation, CI pipelines, or test-management integrations.

Use when Codex needs to derive Rest Assured test scenarios from OpenAPI or Swagger contracts, including endpoints, methods, schemas, auth rules, status codes, and error conditions.

Use when Codex needs to derive service-test scenarios from WSDL or SOAP contracts and translate them into HTTP and XML checks that can still be implemented with Rest Assured where appropriate.

Use when Codex needs to extract testable API behavior from epics, user stories, acceptance criteria, tickets, markdown docs, or other prose requirements before generating Rest Assured scenarios.

Use when Codex needs to scaffold, retrofit, or normalize a Java Rest Assured test module with JUnit 5, Maven or Gradle, shared specifications, and an initial runnable smoke test.

Use when Codex needs to configure or troubleshoot Rest Assured API tests in CI pipelines, including JUnit 5 execution, tags, Docker, containers, artifacts, quality gates, and provider-specific pipeline examples.

Use when Codex needs to implement, refactor, debug, or extend Rest Assured API tests with JUnit 5, reusable request and response specifications, authentication helpers, DTOs, contract checks, and service-test best practices.

Use when Codex needs to keep Rest Assured API coverage plans, requirements mappings, and test-case documentation synchronized as scenarios are added, removed, or renamed.

Use when you need a Cypress task handover that preserves status, session state, blockers, and exact resume steps for a human or later agent.

Flagship Cypress skill pack for planning, authoring, debugging, documenting, and operationalizing Cypress. Routes E2E, API, component, visual, accessibility, CI/CD, coverage, docs, CLI automation, and handoff workflows.

Requirements-analysis skill for Cypress planning and implementation. Use when Codex needs to extract testable behaviors, acceptance criteria, risks, dependencies, or open questions from tickets, specs, markdown docs, or other requirement sources before writing tests or coverage plans.

CI and delivery skill for Cypress automation. Use when Codex needs to design, debug, or optimize Cypress execution in GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, sharded pipelines, artifact workflows, or shared setup and teardown.

Battle-tested Cypress patterns for E2E, API, component, visual, accessibility, and security testing. Covers selectors, assertions, hooks, intercepts, auth flows, debugging, and framework recipes for React, Next.js, Vue, and Angular.

Coverage-maintenance skill for Cypress planning and documentation. Use when Codex needs to synchronize coverage plans, scenario IDs, traceability links, and summary counts after tests, requirements, or narrative test documents change.

Coverage-planning skill for Cypress work. Use when Codex needs to turn confirmed requirements into a structured, risk-aware Cypress coverage plan with scenarios, execution types, priorities, and traceability.

Coverage-plan review skill for Cypress work. Use when Codex needs to present a proposed coverage plan, surface assumptions and tradeoffs, collect user feedback, and secure explicit approval before large implementation or documentation work.

Flagship Playwright skill pack for planning, authoring, debugging, documenting, and operationalizing Playwright. Routes E2E, API, component, visual, accessibility, CI/CD, coverage, docs, CLI automation, and handoff workflows.

Requirements-analysis skill for Playwright planning and implementation. Use when Codex needs to extract testable behaviors, acceptance criteria, risks, dependencies, or open questions from tickets, specs, markdown docs, or other requirement sources before writing tests or coverage plans.

CI and delivery skill for Playwright automation. Use when Codex needs to design, debug, or optimize Playwright execution in GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, sharded pipelines, artifact workflows, or shared setup and teardown.

Core Playwright implementation skill for resilient test authoring and debugging. Use when Codex needs practical Playwright guidance for locators, assertions, fixtures, authentication, network behavior, API testing, component testing, debugging, framework-specific recipes, or broader test architecture decisions.

Coverage-maintenance skill for Playwright planning and documentation. Use when Codex needs to synchronize coverage plans, scenario IDs, traceability links, and summary counts after tests, requirements, or narrative test documents change.

Coverage-planning skill for Playwright work. Use when Codex needs to turn confirmed requirements into a structured, risk-aware Playwright coverage plan with scenarios, execution types, priorities, and traceability.

Coverage-plan review skill for Playwright work. Use when Codex needs to present a proposed coverage plan, surface assumptions and tradeoffs, collect user feedback, and secure explicit approval before large implementation or documentation work.

Use when Playwright work must be handed from one operator to another, including at task completion, during mid-task pauses, after a blocker, or before review. Create a structured handover that records what was completed, where execution stopped, what remains, validation status, blockers, and the exact steps to resume safely.

Use when Codex needs to create, run, evaluate, debug, correct, modernize, document, or route JUnit 5 tests and related workflows across component, integration, slice, repository, service, regression, smoke, and migration scenarios.

Use when Codex needs to derive JUnit 5 test scenarios from requirements, code, or existing test case definitions such as TDD, BDD, and plain-text specifications.

Use when Codex needs to shape or refactor JUnit 5 suite architecture, test package structure, naming, fixture ownership, reuse patterns, or boundaries between component, integration, and service tests.

Use when Codex needs to run JUnit 5 tests through Maven, Gradle, or the Console Launcher, configure CI pipelines, manage tags and reports, or debug environment-specific execution issues.

Use when Codex needs to create, run, debug, evaluate, refactor, or correct JUnit 5 tests across component, integration, slice, repository, service, smoke, or regression scenarios.

Use when Codex needs to analyze a failing JUnit 5 test run, identify the most likely root cause, and produce a developer-focused diagnosis with concrete next fixes.

Use when Codex needs to document JUnit 5 automation code with clear scenario intent, suite purpose, traceability, or maintainable human-readable explanations.

Use when Codex needs to create, review, or debug JUnit 5 extensions, custom annotations, lifecycle callbacks, parameter resolvers, or reusable execution hooks.

Turn requirements, user stories, acceptance criteria, business rules, use cases, or state models into structured test artifacts. Selects the best black-box test design technique and routes work to the matching subskill. For format-only work, prefer test-artifact-export-skill.

Use this skill when Codex needs to convert user stories or acceptance criteria into traceable behavior-focused scenarios or structured test cases.

Use this skill when a requirement contains ordered values such as ranges, lengths, dates, counts, or sequence limits and Codex needs boundary-focused test scenarios.

Use this skill when Codex needs to model interacting parameters and generate reduced pairwise or n-wise combinations instead of an impractical full Cartesian set.

Use this skill when requirements describe discrete business rules, multiple conditions, or outcome logic that should be modeled as a rule table.

Use this skill when Codex needs to derive representative tests from input classes that should behave the same within each valid or invalid partition.

Use this skill when a system has discrete states, events, guards, or lifecycle phases and Codex needs transition-focused test design.

Use this skill when Codex needs to choose the best black-box test design technique for a requirement, user story, rule set, workflow, or state model before generating tests.

Audit and reduce YAML frontmatter bloat in SKILL.md files. Trigger to: scan skill directories, identify oversized frontmatter, propose deduplication/flattening/migration optimizations, and apply approved changes. Requires user approval before writing.

Skill with horizontal rules in body.

A clean skill under the limit. Trigger for: demo, testing.

This is an extremely long description that goes on and on about all the things this skill can do including scanning repositories for issues and analyzing code quality and checking for vulnerabilities and generating reports and sending notifications and much more functionality that nobody needs in a description field.

Security & trust vetting for an AgentSkill (folder, SKILL.md, zip, or single script) before it is installed or approved. Runs a mandatory open-source scanner gate (Cisco skill-scanner, NVIDIA SkillSpector, Snyk Agent Scan, sentry/skill-scanner), then static heuristics, and produces a draft review report — file inventory, executable surface, findings by severity, an OWASP Agentic Skills Top 10 (AST01-AST10) coverage map, a red-flag checklist, a suggested review tier (0-3), and reviewer sign-off blocks. Use this whenever someone asks "is this skill safe", "vet/review/scan this skill or SKILL.md or script", "run the vetting on skill X", "should I install this skill", or when a skill must pass the AgentSkills review flow. Also use it to re-vet an updated skill and diff the reports. It assists review and never approves anything on its own.

Example fixture skill bundled with skill-vetting-reporter. It fetches a public weather forecast for a city and returns a one-line summary. It exists only to demonstrate what a vetting report looks like — including a deliberate false positive — and is not meant to be installed or used for real work.

Plan, execute, and analyze performance testing for APIs, web apps, and distributed systems. Trigger for load, stress, spike, endurance tests, scalability, latency/throughput, and SLO verification. Use for capacity planning and bottleneck analysis. Do NOT use for destructive DoS or unauthorized production saturation.

Use when a working Angular, React, Vue, or static web app must look hand-sketched (Balsamiq wireframe, Sharpie marker, pencil, doodle, or blueprint) for a client demo, so clients read it as a draft and understand it is not production. Applies a reversible, non-destructive visual skin with an adjustable sketchiness level (0-100%) without touching components, markup, routing, state, or any logic.

Enrich and compile an existing travel itinerary into a premium travel guide or roadbook. Trigger this skill whenever a user shares or pastes a travel plan, trip schedule, or itinerary — in any format (Word .docx, Excel .xlsx, PDF, markdown, or plain text) — and wants to: fill gaps (empty meals, bare URLs, missing activity descriptions), add restaurant recommendations, produce a styled output document, or choose a publication style (Michelin Green roadbook, Rick Steves opinionated, Boutique minimalist, DK Eyewitness visual, Lonely Planet backpacker, or Blue Guides scholarly). Also trigger for phrases like 'make this itinerary nicer', 'enrich my travel plan', 'turn my trip notes into a proper guide', 'I have a holiday itinerary and want a roadbook', or any time an itinerary file is uploaded and the user wants it improved or styled. This skill orchestrates structure and completeness — it delegates prose writing to the travelguide-copywriter companion skill.

Use when writing high-quality travel guides, roadbooks, or itineraries. Sourced inputs can include coordinates, links, or place names. It supports personalization based on traveler ages, interests, and dietary needs, and uses live-verified TripAdvisor or Google reviews for restaurant recommendations.

Use when the user wants end-to-end testing for a change — running a requirement, feature, webapp, UI, batch job, API, or release through the full 13-phase lifecycle (intake → HITL design → analysis → strategy → design → quality gate → data prep → export → automation + manual track in parallel → execution → functional review → heal loop → final report). Dispatches to phase-specific skills and pauses at HITL gates for approval. Use whenever the user asks to "test this end-to-end", "plan and execute testing", "run the test chain", or "deliver a verified, documented test pass". Do not use for one-off planning (use test-strategy-skill) or one-off case design (use test-design-orchestrator).