CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-testing

Use when writing or changing Vitest or React Testing Library tests under `web/` or `packages/dify-ui/`, or when the user explicitly requests frontend test strategy, including evaluation of an existing strategy. Do not use for frontend code-review-only requests, general testability discussion, Python tests, or Cucumber/Playwright E2E.

71

Quality

86%

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

86%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.

An exceptionally lean, well-structured instruction-only skill that delegates detail to owner docs and includes validation plus a reporting checkpoint. Its only weakness is that the actual validation commands live in referenced files rather than inline.

DimensionReasoningScore

Conciseness

Lean and efficient (~9 lines); assumes Claude's competence, never explains what Vitest or testing libraries are, and every line earns its place.

5 / 5

Actionability

Concrete file references and specific behavioral guidance ('follow... validation commands', 'recommend deleting low-value tests', 'report the contract verified and any material verification gap'); stops short of 5 because the executable commands are delegated to referenced owner docs rather than given inline.

4 / 5

Workflow Clarity

A clear implied sequence (identify owner, read policy, follow incl. validation, report contract + gaps) with a reporting checkpoint and validation referenced; not 5 because no explicit validate->fix->retry loop or checklist is spelled out.

4 / 5

Progressive Disclosure

A clear overview pointing to two well-signaled one-level-deep owner docs, with 'This skill adds no parallel policy' reinforcing that details live one level deep; easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

87%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.

A precise, well-bounded description with explicit triggers and exclusions. It clearly communicates what the skill does, when to use it, and where it does not apply.

DimensionReasoningScore

Specificity

Lists several concrete, well-scoped actions ('writing or changing Vitest or React Testing Library tests', 'evaluation of an existing strategy') with named tools and paths; falls short of 5 because the action list is not long/comprehensive.

4 / 5

Completeness

Explicitly answers both what (write/change/evaluate frontend tests) and when ('Use when...', plus a 'Do not use for...' boundary) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keywords users would say ('Vitest', 'React Testing Library', 'frontend test strategy', 'Cucumber/Playwright E2E'); not 5 because synonyms like 'unit/component tests' and extensions like '.test.tsx' are absent.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (Vitest/RTL frontend tests under specific paths) and explicitly excludes overlapping areas (Python tests, Cucumber/Playwright E2E, code-review-only), minimizing conflict risk.

5 / 5

Total

18

/

20

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
langgenius/dify
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.