tessl-labs/testing-library-patterns
Testing Library patterns for React component testing — queries, user events,
99
99%
Does it follow best practices?
Impact
100%
1.03xAverage score across 8 eval scenarios
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 well-crafted skill description that excels across all dimensions. It provides specific capabilities (queries, user events, async assertions), includes natural trigger terms users would actually say, explicitly states when to use it with multiple scenarios, and carves out a distinct niche around Testing Library for React that won't conflict with other testing-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'queries, user events, async assertions, and accessibility-first testing' clearly describes what capabilities this skill provides. | 3 / 3 |
Completeness | Clearly answers both what ('Testing Library patterns for React component testing — queries, user events, async assertions, and accessibility-first testing') AND when ('Use when testing React components, when writing component tests that avoid implementation details, or when migrating from Enzyme'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'React component testing', 'component tests', 'implementation details', 'Enzyme', 'Testing Library' - covers both the tool name and common migration scenario. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Testing Library specifically for React, with distinct triggers like 'Enzyme migration' and 'accessibility-first testing' that differentiate it from generic testing skills or other testing frameworks. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates Testing Library best practices with maximum efficiency. It uses the RIGHT/WRONG pattern effectively to contrast good and bad approaches, provides fully executable code examples, and includes a comprehensive checklist for validation. The content respects Claude's intelligence by avoiding explanations of basic concepts while providing precise, actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No explanation of what Testing Library is or why testing matters—jumps straight to actionable patterns. Comments are terse and informative. | 3 / 3 |
Actionability | All code examples are fully executable TypeScript/JavaScript with proper imports. RIGHT/WRONG patterns make correct usage immediately clear. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Section 8 demonstrates clear sequencing (loading → data → loading gone) with explicit steps. The checklist provides validation checkpoints. Query variant cheatsheet clarifies when to use each approach. | 3 / 3 |
Progressive Disclosure | Well-organized with numbered sections, clear headings, and a summary checklist. References section points to external docs for deeper dives. Setup is appropriately brief and placed near the end. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents