unit-testing-test-generate

Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/unit-testing-test-generate/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly code-driven and actionable, with concrete generators for several languages, but it is held back by an undefined-helper gap, a complete absence of validation for the batch generation workflow, and a monolithic single-file structure with no progressive disclosure. Tightening redundancy and adding a verify step would materially improve it.

Suggestions

Add a validation/verification step to the workflow (e.g., 'After generating, run the suite and ensure every test passes; fix failures before finalizing') to lift workflow clarity past the batch cap.

Define or remove the undefined helper methods (_generate_mock_args, _generate_empty_args, _generate_invalid_args, _calculate_complexity, create_targeted_test) so the code is fully copy-paste ready.

Move the per-language generator reference and coverage tooling into separate reference files (e.g., references/python-generator.md, references/coverage.md) and link them from SKILL.md to improve progressive disclosure and conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly code with limited concept padding, but the opening paragraph and 'Context' section restate the description, and several near-duplicate generator patterns could be tightened; it is efficient in places but carries unnecessary redundancy.	3 / 5
Actionability	Six sections of concrete, mostly executable code (pytest/jest/React generation, coverage analysis, mocks) cover the common cases, but several referenced helpers (_generate_mock_args, _generate_empty_args, _generate_invalid_args, _calculate_complexity, create_targeted_test) are undefined, leaving minor gaps below fully copy-paste ready.	4 / 5
Workflow Clarity	Steps are numbered 1-6 as a sequence, but this is a batch test-generation operation with no validation or verification that generated tests actually run or pass; the destructive/batch cap holds workflow clarity at 3.	3 / 5
Progressive Disclosure	The body has clear section headers and structure, but at ~320 lines all per-language generators and coverage tooling are inlined in one file with no external references or bundle files, so content that could be split out is inline.	3 / 5
	Total	13 / 20 Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description states a clear purpose but lacks any explicit 'when to use' trigger guidance, capping completeness at 3, and offers only one concrete action with moderate keyword coverage. It is reasonably distinct but would benefit from trigger phrasing and more specific actions.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when the user asks for unit tests, wants to improve coverage, or needs mocks/fixtures for existing code').

List a few more specific concrete actions (e.g., 'analyze untested code, generate pytest/jest suites, detect coverage gaps') to raise specificity.

Include natural synonyms and framework names (pytest, jest, junit, mocks, fixtures) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ('Generate comprehensive, maintainable unit tests') with quality attributes ('across languages', 'strong coverage', 'edge case focus'), but does not list multiple distinct concrete actions as the anchor-4/5 examples do.	3 / 5
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance; per the judging guidelines, a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Contains natural terms a user would say ('unit tests', 'coverage', 'edge case') but omits common variations and synonyms such as specific frameworks (pytest/jest), 'mocking', or 'test suite', so it sits at the 'some relevant keywords' anchor rather than comprehensive coverage.	3 / 5
Distinctiveness Conflict Risk	'Generate unit tests across languages' is a fairly distinct niche with minimal conflict risk, though 'across languages' leaves some overlap with language-specific testing skills, keeping it just below a clear-niche 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/unit-testing-test-generate/SKILL.md
Commit: 3eff4af

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

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.