msw
Assists with intercepting network requests for API mocking using Mock Service Worker (MSW). Use when mocking REST or GraphQL APIs for unit tests, integration tests, or local development without modifying application code or running mock servers. Trigger words: msw, mock service worker, api mocking, test mocking, request handlers, setupServer.
What this skill does
# MSW (Mock Service Worker)
## Overview
MSW intercepts network requests at the service worker level (browser) or in-memory (Node.js) to mock REST and GraphQL APIs for tests and local development. It uses the same handlers for both environments, keeping mocks consistent, and works transparently with any HTTP client (fetch, axios, Apollo) without modifying application code.
## Instructions
- When setting up handlers, define REST handlers with `http.get()`, `http.post()`, etc. and GraphQL handlers with `graphql.query()` and `graphql.mutation()`, returning responses via `HttpResponse.json()`.
- When testing in Node.js, use `setupServer(...handlers)` with `server.listen()` before tests, `server.resetHandlers()` between tests, and `server.close()` after all tests.
- When developing in the browser, use `setupWorker(...handlers)` and run `npx msw init ./public` to generate the service worker file, which intercepts requests visible in DevTools.
- When overriding per test, use `server.use()` to add temporary handlers for error states or edge cases, which scope to the current test and reset afterward.
- When simulating network issues, use `delay(ms)` for latency, `HttpResponse.error()` for failures, and custom status codes for error responses.
- When organizing handlers, keep shared handlers in `src/mocks/handlers.ts` for reuse across test files and the dev server, with per-test overrides via `server.use()`.
## Examples
### Example 1: Mock a REST API for component tests
**User request:** "Set up MSW to mock my user API for React Testing Library tests"
**Actions:**
1. Define handlers in `src/mocks/handlers.ts` for GET `/api/users`, POST `/api/users`, and GET `/api/users/:id`
2. Set up `setupServer(...handlers)` in the test setup file with beforeAll/afterEach/afterAll hooks
3. Write component tests that render with data from the mock API
4. Add per-test error overrides with `server.use(http.get("/api/users", () => HttpResponse.json(null, { status: 500 })))`
**Output:** Component tests with realistic API mocking, including happy path and error state coverage.
### Example 2: Mock a GraphQL API for development
**User request:** "Set up MSW to mock my GraphQL API during local development"
**Actions:**
1. Define GraphQL handlers for queries (`GetPosts`, `GetUser`) and mutations (`CreatePost`)
2. Set up `setupWorker(...handlers)` in the browser entry point with conditional activation
3. Add `delay(300)` to simulate realistic network latency
4. Run `npx msw init ./public` and start the dev server
**Output:** A development environment with mocked GraphQL API visible in browser DevTools, with realistic latency.
## Guidelines
- Use MSW in both tests and development with the same handlers to keep mocks consistent.
- Define handlers in a shared `src/mocks/handlers.ts` file for reuse across test files and the dev server.
- Use `server.use()` for per-test overrides; keep the default happy path in shared handlers.
- Always mock error states in tests to verify error handling works correctly.
- Use `delay()` in development mocks to simulate real latency and catch loading state bugs.
- Reset handlers after each test with `afterEach(() => server.resetHandlers())` to prevent test pollution.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.