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 explicit 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.'
Add an explicit 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user asks to write tests, create unit tests, generate Jest test cases, add test coverage, or mentions .test.js/.spec.js files.'
Include natural keyword variations users would say: 'unit tests', 'test cases', 'write tests', 'test file', 'describe block', 'expect', 'mock', '.test.ts', 'test coverage', 'Jest'.
| 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 vague (just the name 'Jest Test Generator') and the 'when' is essentially absent—listing 'Triggers on: jest test generator' is not meaningful guidance. There is no explicit 'Use when...' clause with real trigger scenarios. | 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 | The mention of '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 testing-related skills means it could still overlap with general test-writing or other test framework 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 an empty shell with no substantive content. It consists entirely of auto-generated boilerplate that describes what a Jest test generator skill would do without actually providing any instructions, code examples, patterns, or workflows for generating Jest tests. It fails on every dimension because there is no real content to evaluate.
Suggestions
Add concrete, executable Jest test examples showing common patterns (unit tests, mocking, async testing) with copy-paste ready code blocks
Define a clear workflow: analyze source file → identify testable functions → generate test structure → add assertions → run and validate tests
Include specific Jest configuration snippets (jest.config.js), common matchers, and mocking patterns (jest.mock, jest.spyOn) rather than abstract descriptions
Replace all meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') with actual technical content like test templates, naming conventions, and coverage strategies
| 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 has section headers but they contain only boilerplate meta-descriptions. There are no references to detailed files, no actual content to organize, and no meaningful structure beyond self-referential placeholder text. | 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
3e83543
- 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.