Use when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures, isolation and reset between tests, verification of calls, dynamic ports and base URLs, and avoiding flaky stubs — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Design or review WireMock stubs (JSON mappings or Java DSL); Improve request matching, isolation, or reset strategy for HTTP mocks; Add or fix verification of outbound HTTP calls to a WireMock server; Debug flaky tests involving WireMock or unmatched request journals. Part of Plinth Toolkit

Handles CRE (Chainlink Runtime Environment) Go and TypeScript workflows, the CRE CLI, simulate, and deploy. Sends CRE Connect watchers, gas-less Smart Accounts, and dta.v2 to chainlink-cre-connect-skill. Sends private-document LLM inference to chainlink-confidential-ai-attester-skill. Keeps enclave workflow logic with no document on this skill. It applies to CRON, HTTP, and EVM-log triggers, HTTP and EVM read/write, secrets, and monitoring, even when the user never says CRE.

Buy and sell NFTs through OpenSea on EVM chains and Solana. Fulfill listings, accept or create offers, cancel orders, make cross-chain purchases, and sweep listings. Requires wallet signing; for read-only queries use opensea-api instead.

Structured performance opportunity investigation for SpiderMonkey (the Firefox JavaScript engine). Use this skill when the user wants to investigate JS engine performance, profile SpiderMonkey, find optimization opportunities, write performance patches, or evaluate benchmark regressions. Trigger on mentions of: profiling JS, SpiderMonkey performance, JIT optimization, benchmark regression analysis, shell benchmarking, or any request to make JS workloads faster. The methodolgy is described mostly for the JS shell but can be adapted to browser investigation.

Improve, rewrite, edit, or review prose so it is clear, direct, useful, and natural without inventing facts or erasing the author's voice. Use when drafting or revising emails, documentation, reports, essays, messages, UI copy, explanations, or other prose; when the user asks to write better, humanize text, remove AI-sounding language, tighten wording, improve clarity or tone, or make an action easier to understand. Do not use for translation or factual research unless writing quality is also part of the request.

UiPath Vertical Solutions via `uip vss deploy` — guided deploy of an industry solution package such as FINS (Financial Services) Loan Setup (`fins.loan-setup`) or Lending QA/QC (`fins.qaqc-uipath`): fresh install, upgrade/downgrade, deploy job status/resume/cancel, Data Fabric seeding (`uip vss deploy seed`), setting up a deployed solution (such as the FINS role groups), and checking the deploying user's tenant and folder access. Diagnoses refused or paused deploy jobs. For packing/deploying your own `.uipx` with `uip solution`→uipath-solution; Orchestrator folders/queues/roles or Data Fabric records outside a deploy→uipath-platform; other Identity users/groups/external apps→uipath-admin; faulted runtime jobs→uipath-troubleshoot.

UiPath Activity Migrator — migrate Windows-Legacy RPA projects (`targetFramework: Legacy`, classic `ui:` activities) to the Windows framework and rewrite UiPath's own classic activities into their modern UiPath counterparts with the standalone `UiPath.Upgrade.exe`. Windows only. Third-party or custom packages are not rewritten, only version-moved. Acquires the tool, resolves the target UIAutomation line, runs analyze then upgrade into a sibling folder, verifies with `uip rpa build`, triages the SARIF. Classic UI Automation→modern UIA, Outlook classic→Microsoft 365, GSuite classic→modern, Microsoft.Activities.Extensions→Invoke Code. Also the post-migration fix for migrated projects whose expression-selector targets fail or silently report not-found. Authoring or editing Legacy `.xaml`→uipath-rpa. Migration-readiness review without running the tool→uipath-review. Post-migration failures with neither marker nor annotation→uipath-troubleshoot. Maestro `instance migrate`→the Maestro skills.

Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml. Use when asked to create or update a repository quality profile.

Proposes repository-specific quality policy for implementation and review and, after confirmation, creates or updates docs/project-context/quality.yaml. Use when asked to create or update a repository quality profile.

Defines integration/E2E skeleton annotations, lane and file contracts, and route-parity review criteria. Use when generating or consuming test skeletons or reviewing shared mutation routes.

Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.

Adds Dataverse tables to a Power Apps code app with generated TypeScript models and services. Can also create new Dataverse tables. Use when connecting to Dataverse, adding tables, creating schema, or querying Dataverse data.

Measure which platforms and touches actually drive conversions across channels, compare attribution views, and read assisted conversions and conversion paths. Use when a user asks what is really working, wants cross-platform attribution, or questions a single platform's self-reported numbers.

Build a full media plan — objective, channel mix, budget split, projected CPM/CPC/CPA, and a first test flight — before any campaign is built. Use when a user wants a media plan, a budget allocation across platforms, or a go-to-market for a launch.

Catch spend spikes, CTR or conversion-rate drops, budget runaway, and metric outliers across campaigns, and set sane alert thresholds. Use when a user asks why spend or performance changed suddenly, wants monitoring or alerts, or something looks off in the numbers.

Build C-suite and board ad reports — blended ROAS, month-over-month and year-over-year, pacing, and a plain-English narrative of what happened and what to do. Use when a user wants an executive summary, a board report, or a monthly performance review across platforms.

Build a full media plan — objective, channel mix, budget split, projected CPM/CPC/CPA, and a first test flight — before any campaign is built. Use when a user wants a media plan, a budget allocation across platforms, or a go-to-market for a launch.

Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.

Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.

Review code changes for concrete behavior, contract, security, test, maintainability, and documentation defects. Use when the user exactly asks you for a "code review" or to "review" code.