Test Naming Enforcer - Auto-activating skill for Test Automation. Triggers on: test naming enforcer, test naming enforcer Part of the Test Automation skill category.
36
Quality
7%
Does it follow best practices?
Impact
87%
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/test-naming-enforcer/SKILL.mdJest test naming conventions
describe block present
100%
100%
it/test string format
100%
100%
No implementation detail in names
100%
90%
State and outcome expressed
100%
91%
Nested describe for grouping
0%
0%
All tests renamed
100%
100%
Production-ready syntax
100%
100%
Validation summary produced
100%
100%
Consistent naming style
100%
100%
Step-by-step approach documented
100%
87%
Without context: $0.3352 · 1m 18s · 19 turns · 20 in / 4,855 out tokens
With context: $0.4884 · 1m 40s · 27 turns · 60 in / 6,066 out tokens
Pytest naming enforcement tooling
test_ prefix enforcement
100%
100%
snake_case enforcement
90%
100%
Descriptive name check
100%
100%
State and outcome pattern
70%
70%
Unit vs integration distinction
0%
0%
Actionable violation output
100%
100%
Exit code convention
100%
100%
Production-ready script
100%
100%
Demo run output
100%
100%
Step-by-step explanation
87%
100%
Without context: $0.5425 · 2m 26s · 26 turns · 26 in / 8,729 out tokens
With context: $0.7370 · 3m · 32 turns · 67 in / 10,172 out tokens
Test framework setup with mocking naming
Unit/integration separation
100%
100%
describe/it structure
100%
100%
Behaviour-focused test names
100%
100%
Mock variable naming
70%
80%
Mock file naming
50%
50%
Jest config produced
100%
100%
TDD naming discipline
62%
62%
Production-ready config
100%
100%
Naming convention documented
100%
100%
Consistent mock describe grouping
33%
33%
Without context: $0.5995 · 2m 33s · 30 turns · 31 in / 9,738 out tokens
With context: $0.9829 · 3m 41s · 45 turns · 79 in / 13,634 out tokens
60433a6
Table of Contents
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.