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.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill jest-test-generatorActivation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It lacks concrete actions, natural trigger terms, and explicit usage guidance. The only distinguishing element is the mention of 'Jest' which provides minimal differentiation.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Jest unit tests, creates mock functions, writes test suites with describe/it blocks, and sets up test fixtures'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user asks to write tests, create unit tests, test JavaScript/TypeScript code, or mentions Jest, .test.js, or test coverage'
Remove the duplicate trigger term and expand with variations users would naturally say: 'unit tests', 'test file', 'write tests for', 'testing', 'test cases'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Jest Test Generator') and category ('Test Automation') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of generating tests, writing assertions, mocking, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both what and when are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'jest test generator' repeated twice. Missing natural variations users would say like 'write tests', 'unit tests', 'test cases', 'testing', '.test.js', or 'create jest tests'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Jest' specifically provides some distinctiveness from other testing frameworks, but 'Test Automation' is generic enough to potentially conflict with other testing-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%This skill is a generic template with no actual Jest-specific content. It describes capabilities abstractly without providing any executable code, concrete examples, or actionable guidance for generating Jest tests. The content fails to teach Claude anything it doesn't already know about Jest testing.
Suggestions
Add executable Jest test generation examples showing input code and expected test output
Include concrete patterns for common Jest scenarios: mocking modules, testing async code, snapshot testing
Provide a clear workflow: analyze source file → identify testable units → generate test structure → add assertions → validate coverage
Remove generic boilerplate sections (Purpose, Capabilities, Example Triggers) and replace with actual Jest-specific guidance
| 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 doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The entire skill describes what it does abstractly without showing how to actually generate Jest tests. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with clear headers, but there are no references to detailed materials, examples, or advanced documentation. The structure exists but contains no substantive content to disclose. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.