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
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 excellent trigger terms. It uses proper third-person voice, names specific technologies and artifact types, and has a clear niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: generating tests for 'components, hooks, and utilities' using specific frameworks 'Vitest + React Testing Library'. It names the domain (Dify frontend) and the types of artifacts it produces. | 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 | Includes a strong set of natural trigger terms users would say: 'testing', 'spec files', 'coverage', 'Vitest', 'RTL', 'unit tests', 'integration tests', 'write/review test requests'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of Dify frontend, Vitest, and React Testing Library. This is unlikely to conflict with other skills given the narrow technology stack and project scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 excellent workflow clarity including explicit validation loops and incremental processing. Its main weakness is verbosity — it explains testing fundamentals (AAA pattern, single behavior per test, semantic naming) that Claude already knows, and the main file could be trimmed by moving detailed guidance into the referenced files. The progressive disclosure structure is reasonable but cannot be fully validated without bundle files.
Suggestions
Move 'Core Principles' (AAA pattern, single behavior per test, semantic naming) to a reference file — Claude already knows these testing fundamentals and they consume significant tokens.
Trim the 'When to Apply This Skill' section; the positive triggers list is largely redundant with the skill description and frontmatter triggers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary explanation (e.g., the 'When to Apply This Skill' section with obvious triggers, the 'Core Principles' section explaining AAA pattern and single-behavior-per-test which Claude already knows). The coverage goals and required test scenarios tables add value but could be more compact. | 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 nuqs testing guidance are all specific and actionable. | 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 addressed with the fix-then-continue pattern. | 3 / 3 |
Progressive Disclosure | The skill references six detailed guides in `references/` and cites authoritative sources like `web/docs/test.md`, which is good structure. However, no bundle files were provided, so we cannot verify these references exist. The main SKILL.md itself is quite long (~250 lines) and some sections (Core Principles, Required Test Scenarios table) could be offloaded to reference files to keep the overview leaner. | 2 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- langgenius/dify
- Commit
9cdeffd
- 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.