Use when implementing any feature or bugfix, before writing implementation code
68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.00xAgent success when using this skill
Validation for skill structure
TDD Red-Green-Refactor cycle
RED before GREEN evidence
100%
100%
Correct failure reason
100%
100%
GREEN verification shown
100%
100%
REFACTOR step present
100%
100%
Minimal implementation
100%
100%
Single behavior per test
100%
100%
Descriptive test names
100%
100%
No mocks in tests
100%
100%
Multiple TDD cycles
100%
100%
Pristine output
100%
100%
Without context: $1.0544 · 4m 9s · 52 turns · 59 in / 12,669 out tokens
With context: $1.0884 · 3m 20s · 46 turns · 295 in / 10,353 out tokens
Bug fix with test-first
Failing test before fix
100%
100%
Test reproduces the bug
100%
100%
Failure is assertion not crash
100%
100%
Minimal fix applied
100%
100%
All tests pass after fix
100%
100%
Descriptive test name
100%
100%
No pre-emptive implementation
100%
100%
Discount calculation tested
100%
100%
Single behavior per test
100%
100%
No test-only methods in production
100%
100%
Without context: $0.6643 · 2m 42s · 32 turns · 38 in / 9,079 out tokens
With context: $0.7644 · 2m 21s · 37 turns · 72 in / 6,873 out tokens
Testing anti-patterns and mocking
No test-only methods in production
100%
100%
Mock response includes ok property
100%
100%
Mock response includes status property
100%
100%
Mock response includes json method
100%
100%
fetch is mocked, not service methods
100%
100%
Tests assert on return values
100%
100%
Error behavior tested with throws
100%
100%
No mock-existence assertions
100%
100%
Test cleanup outside production class
100%
100%
Both service methods tested
100%
100%
Without context: $0.4725 · 2m 7s · 26 turns · 32 in / 6,981 out tokens
With context: $0.5888 · 1m 58s · 28 turns · 31 in / 6,344 out tokens
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.