jest-test-generator
Jest Test Generator - Auto-activating skill for Test Automation. Triggers on: jest test generator, jest test generator Part of the Test Automation skill category.
36
3%
Does it follow best practices?
Impact
96%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/jest-test-generator/SKILL.mdQuality
Discovery
7%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 description is essentially a title and category label with no substantive content. It fails to describe any concrete actions the skill performs, lacks natural trigger terms users would use, and provides no guidance on when Claude should select this skill. It reads like auto-generated boilerplate rather than a useful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Jest test files with describe/it blocks, creates mock implementations, writes assertions for functions and components, and sets up test fixtures.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to write Jest tests, create unit tests, generate test cases, add test coverage, or work with .test.js/.spec.js files.'
Remove the duplicated trigger term and replace with diverse natural language variations users would actually say, such as 'unit tests', 'test file', 'test coverage', 'mock', 'describe block', 'expect assertions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Jest Test Generator') but provides no concrete actions. It doesn't describe what the skill actually does—no mention of generating test files, writing assertions, mocking dependencies, or any specific capabilities. | 1 / 3 |
Completeness | The 'what' is extremely weak (just a name, no actions described) and the 'when' is missing entirely—there is no 'Use when...' clause or equivalent explicit trigger guidance. The description fails to answer either question meaningfully. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'jest test generator' repeated twice. Missing natural variations users would say like 'write tests', 'unit tests', 'test cases', 'jest', '.test.js', 'testing', 'describe block', 'test coverage', etc. | 1 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Jest' specifically does narrow the scope to a particular testing framework, which provides some distinctiveness. However, the lack of detail about what it does versus other test-related skills means it could still overlap with general testing or code generation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially an empty shell—a meta-description of what a Jest test generator skill would do, without any actual instructional content. It contains no code examples, no Jest-specific patterns, no test generation workflows, and no actionable guidance. It fails on every dimension because it describes rather than instructs.
Suggestions
Add concrete, executable Jest test examples showing common patterns (unit test, mock, async test) with copy-paste ready code blocks
Define a clear workflow for test generation: analyze source → identify test cases → write tests → run and validate → iterate on failures
Include Jest-specific configuration snippets (jest.config.js), common matchers, mocking patterns (jest.mock, jest.spyOn), and assertion examples
Remove all meta-description sections (Purpose, When to Use, Example Triggers, Capabilities) and replace with actual technical content that teaches Jest test generation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section describes rather than instructs, wasting tokens on information Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no commands, no Jest configuration, no test patterns, no executable content whatsoever. The skill describes itself rather than teaching Claude how to generate Jest tests. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for generating tests, no validation checkpoints, and no process for creating, running, or verifying Jest tests. The 'step-by-step guidance' mentioned in Capabilities is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic description with no meaningful structure. Sections like 'When to Use' and 'Example Triggers' contain redundant trigger phrases rather than useful content. No references to detailed materials or examples exist. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- 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.