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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill jest-test-generator36
Quality
3%
Does it follow best practices?
Impact
96%
1.00xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/jest-test-generator/SKILL.mdDiscovery
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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing useful trigger guidance. It lacks concrete actions, natural user keywords, and explicit usage scenarios. The redundant trigger terms and boilerplate category mention add no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Jest test files with describe/it blocks, creates mocks and spies, writes assertions for JavaScript/TypeScript functions'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks to write tests, create unit tests, add test coverage, or mentions Jest, .test.js, or spec files'
Remove redundant trigger terms and add variations users would naturally say: 'unit tests', 'test file', 'testing', 'write tests for', 'add tests'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Jest Test Generator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of generating test files, writing assertions, mocking, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a circular reference to the skill name. There's no explicit 'Use when...' clause with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are redundant ('jest test generator' repeated twice) and overly specific. Missing natural variations users would say like 'write tests', 'unit tests', 'test coverage', 'testing', '.test.js', or 'spec files'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Jest' is a specific testing framework which provides some distinctiveness, the lack of detail about what actions it performs could cause confusion with other testing-related skills or general 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 content is a generic template with no Jest-specific substance. It contains no executable code, no concrete test generation patterns, no mocking examples, and no actual guidance for creating Jest tests. The entire content could apply to any skill by swapping the name, making it effectively useless for its stated purpose.
Suggestions
Add concrete Jest test examples showing actual test generation patterns (describe/it blocks, expect assertions, beforeEach setup)
Include specific mocking guidance with executable code for jest.mock(), jest.fn(), and module mocking
Provide a clear workflow: analyze source file → identify test cases → generate test structure → add assertions → validate coverage
Replace generic capability descriptions with actual Jest configuration snippets and common testing patterns (async tests, snapshot testing, etc.)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Jest test generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already knows and add no value. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no Jest-specific commands, no actual test patterns. The content describes what the skill does abstractly rather than providing executable instructions for generating Jest tests. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for how to actually generate Jest tests, no validation checkpoints, and no sequence of operations. The 'Capabilities' section lists vague promises without any process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, no links to examples, and no structured navigation to Jest-specific documentation or patterns. | 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 | |
- 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.