CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-testing

Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

This is a well-structured, highly actionable testing skill with strong workflow clarity including explicit validation loops and incremental processing. Its main weakness is moderate verbosity—it explains some concepts Claude already knows (AAA pattern, black-box testing basics) and the 'When to Apply' section is overly detailed. The progressive disclosure structure references supporting files but none were provided in the bundle, and the main file carries substantial detail that could be offloaded.

Suggestions

Remove or drastically shorten explanations of concepts Claude already knows (AAA pattern definition, black-box testing rationale, single-behavior-per-test justification) and keep only the project-specific conventions.

Move the 'Required Test Scenarios' conditional table and 'Coverage Goals' section into a reference file (e.g., references/checklist.md) to keep the main skill leaner as an overview.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some unnecessary verbosity—e.g., the 'When to Apply This Skill' section with 7 bullet points of trigger conditions and 3 'Do NOT apply' bullets is more than Claude needs. The core principles section explains AAA pattern and black-box testing concepts Claude already knows. However, the project-specific conventions and patterns earn their place.

2 / 3

Actionability

The skill provides fully executable code templates, specific bash commands, concrete file naming conventions, and copy-paste ready test structure templates. The mocking patterns, query preferences, and assertion examples are all specific and directly usable.

3 / 3

Workflow Clarity

The incremental testing workflow is clearly sequenced with an explicit write→run→verify feedback loop, a visual flowchart, complexity-based ordering, and clear validation checkpoints ('NEVER generate all test files at once', 'Do NOT continue to next file until current passes'). Error recovery is explicitly addressed.

3 / 3

Progressive Disclosure

The skill references 6 files under `references/` (workflow.md, mocking.md, async-testing.md, etc.) and codebase examples, which is good structure. However, no bundle files were provided, so we cannot verify these references exist. The main file itself is quite long (~200+ lines) and some content (like the full required test scenarios table and coverage goals) could potentially be in reference files to keep the overview leaner.

2 / 3

Total

10

/

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.

This is a strong skill description that concisely covers what the skill does, when to use it, and includes a comprehensive set of natural trigger terms. It uses proper third-person voice, names specific technologies and targets, and is clearly distinguishable from other skills due to its well-defined scope around Dify frontend testing with Vitest and RTL.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: generating tests for 'components, hooks, and utilities' using specific frameworks 'Vitest + React Testing Library'. The scope is well-defined with concrete targets.

3 / 3

Completeness

Clearly answers both 'what' (generate Vitest + RTL tests for Dify frontend components, hooks, and utilities) and 'when' (triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms: 'testing', 'spec files', 'coverage', 'Vitest', 'RTL', 'unit tests', 'integration tests', 'write/review test requests'. These are terms users would naturally use when requesting test-related work.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: Dify frontend testing with specific frameworks (Vitest + React Testing Library). The combination of project scope (Dify), technology stack, and task type makes it very unlikely to conflict with other skills.

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.

Validation11 / 11 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.