CtrlK
BlogDocsLog inGet started
Tessl Logo

playground-msw-tests

REQUIRED and PRIMARY testing approach for packages/playground and packages/playground-ui. Triggers on: adding or modifying hooks, pages, route components, data-fetching code, React Query interactions, or any test work in these packages. Generates Vitest tests that drive the real @mastra/client-js + React Query stack through MSW handlers and typed fixtures derived from @mastra/client-js response types. This is the #1 way to test the playground packages — ABOVE Playwright E2E. Use Playwright only for cross-page user journeys that MSW cannot model.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable testing-strategy skill: executable skeletons and recipes, an explicit priority ordering, and a verification checklist with real validation gates. It avoids concept re-explanation and keeps references shallow and well-signaled.

DimensionReasoningScore

Conciseness

The body is dense with directive do/don't bullets and executable templates that each earn their place; it assumes Claude's competence and avoids re-explaining concepts like what MSW or React Query is. The only mild redundancy is restating the Playwright boundary in both the Priority Order and the closing section.

3 / 3

Actionability

Provides a fully executable Vitest test skeleton, a typed fixture file, and concrete recipes (promise-gate loading state, vi.fn endpoint-gating, query-string variation) plus a runnable typecheck command, all copy-paste ready.

3 / 3

Workflow Clarity

Sequences the work clearly via a numbered Priority Order and 'What TO do' list, then closes with a checkbox Verification Checklist containing explicit validation checkpoints (typecheck passing, isolation run without onUnhandledRequest failures).

3 / 3

Progressive Disclosure

Content is organized into single-level, clearly labeled sections with no nested file references; the only external pointers (the e2e-tests-studio skill and the MSW site link) are one level deep and clearly signaled.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly names its capabilities, scope, and explicit triggers, and proactively disambiguates itself from the sibling Playwright E2E skill. It satisfies all four dimensions with concrete, non-vague language.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Generates Vitest tests that drive the real @mastra/client-js + React Query stack through MSW handlers and typed fixtures derived from @mastra/client-js response types' — rather than vague claims.

3 / 3

Completeness

Explicitly states both what it does ('REQUIRED and PRIMARY testing approach ... Generates Vitest tests ...') and when to use it via an explicit 'Triggers on:' clause.

3 / 3

Trigger Term Quality

'Triggers on: adding or modifying hooks, pages, route components, data-fetching code, React Query interactions, or any test work' covers natural terms a developer would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to packages/playground and packages/playground-ui and explicitly distinguished from Playwright E2E ('Use Playwright only for cross-page user journeys that MSW cannot model'), giving it a clear niche unlikely to conflict.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mastra-ai/mastra
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.