CtrlK
BlogDocsLog inGet started
Tessl Logo

web-testing

Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.

75

Quality

93%

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

87%

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

A well-structured, lean overview with executable commands and excellent progressive disclosure via a verified, categorized reference index. The only gap is workflow clarity: the CI/CD pipeline has gating but no explicit error-recovery feedback loops.

Suggestions

Add error-recovery feedback loops to the CI/CD pipeline, e.g., 'If the E2E gate fails, reproduce locally with `npx playwright test --ui`, fix, then re-run the gate' to reach full workflow clarity.

Inline a short explicit validation checkpoint for the release flow (e.g., a 'Verify before merge' step) rather than relying solely on the pre-release-checklist reference.

Tighten conciseness further by deduplicating the testing-type list between the intro line, the pyramid table, and the 'When to Use' section.

DimensionReasoningScore

Conciseness

The body is lean — compact tables, copy-paste code blocks, and a one-line-per-entry reference index — with no explanations of concepts Claude already knows; minor repetition of testing types across sections is organizational rather than padding.

3 / 3

Actionability

Quick Start and CI/CD sections provide fully executable, copy-paste-ready commands (e.g., 'npx vitest run', 'k6 run load-test.js', 'npx @axe-core/cli https://example.com') rather than vague direction.

3 / 3

Workflow Clarity

The CI/CD pipeline is sequenced with explicit gating checkpoints (Gate 1: Fast fail, Gate 2: After unit pass), but it lacks error-recovery feedback loops describing what to do when a gate fails, so it does not reach the anchor-3 bar.

2 / 3

Progressive Disclosure

A clear overview points to 19 verified, one-level-deep reference files organized under eight categorized subheadings with one-line descriptions, giving easy navigation and no nested-reference chains.

3 / 3

Total

11

/

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 concisely covers a comprehensive set of web-testing capabilities with named tools and an explicit 'Use for...' trigger clause. It answers both what and when with natural, distinctive trigger terms.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities across seven testing modalities (E2E/unit/integration/load/security/visual/a11y) plus three named tools (Playwright, Vitest, k6), exceeding the 'names domain and some actions' anchor.

3 / 3

Completeness

States what it does (web testing across listed modalities/tools) and provides an explicit 'Use for...' trigger clause answering when to invoke it, satisfying both what and when.

3 / 3

Trigger Term Quality

Includes natural terms users actually say — 'E2E', 'unit', 'load testing', 'flakiness', 'Core Web Vitals', 'mobile gestures', 'cross-browser' — giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The web-testing niche with tool-specific and modality-specific triggers (Playwright, k6, Core Web Vitals, cross-browser) is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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
mrgoonie/claudekit-skills
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.