CtrlK
BlogDocsLog inGet started
Tessl Logo

ac-test-generator

Generate tests for features using TDD approach. Use when creating test files, generating test cases, implementing RED phase of TDD, or scaffolding test infrastructure.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/ac-test-generator/SKILL.md

The canonical home for this skill is ac-test-generator in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 body is well-structured and actionable with a clear workflow and a genuine one-level reference to the generator script. It is held back by restating basic testing/TDD concepts Claude already knows and by a vague validation step without an error-recovery loop.

Suggestions

Remove or compress the 'Test Types' bullet lists and the 'RED → GREEN → REFACTOR' explainer, since these are concepts Claude already knows; keep only skill-specific guidance.

Strengthen the 'Validate' workflow step with a concrete command or check (e.g. 'run pytest and confirm every generated test fails before implementation') and add a fix-and-retry feedback loop.

Replace the 'pass'-stubbed example tests with one fully realized failing test so the generated structure is copy-paste ready, or move the bulk example into scripts/test_generator.py and summarize inline.

DimensionReasoningScore

Conciseness

The 'Test Types' bullets ('Mock dependencies', 'Browser automation', 'Real environment') and the 'RED → GREEN → REFACTOR' cycle restate basic testing and TDD concepts Claude already knows, adding padding that could be trimmed.

3 / 5

Actionability

The Quick Start gives executable code and the generated-test example is concrete pytest, but example tests contain 'pass' stubs with comment-only bodies, leaving minor gaps in copy-paste readiness.

4 / 5

Workflow Clarity

The Analyze→Scaffold→Generate→Validate→Report sequence is clear and includes a validation checkpoint ('Validate: Ensure tests fail (RED)'), but the checkpoint is vague and lacks an explicit error-recovery feedback loop.

4 / 5

Progressive Disclosure

Sections are well organized and the 'See scripts/test_generator.py for full implementation' reference is real and one level deep (verified the file exists), though some inline content like the full test example could arguably live in the referenced script.

4 / 5

Total

15

/

20

Passed

Description

83%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.

A strong description that clearly states the skill's purpose and trigger conditions with concrete, mostly natural language. The TDD-specific framing gives it a recognizable niche, though a few common synonyms would round out the trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('creating test files, generating test cases, implementing RED phase of TDD, scaffolding test infrastructure') but stops short of comprehensive coverage of test-generation capabilities.

4 / 5

Completeness

It explicitly answers both what ('Generate tests for features using TDD approach') and when ('Use when creating test files, generating test cases, implementing RED phase of TDD, or scaffolding test infrastructure') with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes natural terms users would say ('test files', 'test cases', 'TDD') but omits common synonyms such as 'unit tests', 'write tests', or 'pytest'.

4 / 5

Distinctiveness Conflict Risk

The TDD/RED-phase framing carves a clear niche, though generic triggers like 'creating test files' and 'generating test cases' could overlap with broader test-writing skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/Skrillz
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.