CtrlK
BlogDocsLog inGet started
Tessl Logo

e2e-tests-studio

REQUIRED when modifying any file in packages/playground-ui or packages/playground. Triggers on: React component creation/modification/refactoring, UI changes, new playground features, bug fixes affecting studio UI. Generates Playwright E2E tests that validate PRODUCT BEHAVIOR, not just UI states.

66

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/e2e-tests-studio/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

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

The body is a well-structured, highly actionable guide with a clear validated workflow and feedback loops, well-organized into navigable sections. Its main weakness is conciseness, driven by repeated scaffolding and a don't/do table that duplicates the opening lists.

Suggestions

Collapse the Anti-Patterns table into the opening What NOT/TO test lists (or vice versa) to remove the duplicated guidance and trim ~12 lines.

Show the ARRANGE/ACT/ASSERT pattern once in the template and have the six behavior patterns reference it, instead of repeating the inline comment scaffolding in every code block.

Either define the selectFixture helper inline or note where it lives, and flag which testIds are illustrative placeholders versus real selectors, to lift actionability to fully executable.

DimensionReasoningScore

Conciseness

Mostly efficient and free of generic-concept padding, but ~449 lines with notable duplication: the Anti-Patterns table restates the opening What NOT/TO test lists, and the ARRANGE/ACT/ASSERT scaffolding is repeated across the template, six patterns, and the refactoring example.

3 / 5

Actionability

Provides concrete commands and six full executable code patterns plus a copy-paste template and mapping table, but some testIds are illustrative rather than verified-real and the selectFixture helper is referenced without definition, leaving minor gaps.

4 / 5

Workflow Clarity

A clear numbered 7-step sequence is backed by explicit checkpoints (verify server at localhost:4111), a Test Quality Checklist, and a Pattern 6 error->fix->retry feedback loop, satisfying the validation/feedback-loop expectation.

5 / 5

Progressive Disclosure

No bundle files exist and the skill needs none; the single SKILL.md is well-organized into clear sections with a Quick Reference table, which meets the bar for a no-external-reference skill.

5 / 5

Total

17

/

20

Passed

Description

82%Weight 40%Scale 1-5

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

The description is strong: it explicitly states both what the skill does and precisely when to use it, scoped to concrete package paths with natural trigger terms. Its only weakness is specificity, where it names the primary action but does not enumerate multiple distinct capabilities.

DimensionReasoningScore

Specificity

Names the domain and one concrete primary action ("Generates Playwright E2E tests that validate PRODUCT BEHAVIOR"), but does not enumerate multiple distinct actions, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Explicitly answers both what ("Generates Playwright E2E tests that validate PRODUCT BEHAVIOR") and when ("REQUIRED when modifying any file in packages/playground-ui or packages/playground. Triggers on: ...") with concrete trigger phrases and paths.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("React component creation/modification/refactoring", "UI changes", "new playground features", "bug fixes affecting studio UI") that a developer would actually say, missing only some synonyms and file extensions.

4 / 5

Distinctiveness Conflict Risk

Scoped to specific package paths (packages/playground-ui, packages/playground) and the Playwright/studio-UI niche, giving it a clear distinct trigger set with minimal overlap risk.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.