CtrlK
BlogDocsLog inGet started
Tessl Logo

tdd-workflow

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

64

Quality

78%

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 ./skills/tdd-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 content delivers a clear, well-validated TDD workflow with strong actionability and feedback loops, but is lengthy and monolithic with redundant sections. Splitting reference material into separate files and removing overlap would improve token efficiency and navigation.

Suggestions

Consolidate redundant sections: merge 'Best Practices' into 'Core Principles' and fold 'Test Coverage Verification' into Step 7 to reduce repetition.

Move the Testing Patterns, Mocking External Services, and CI/CD Integration blocks into separate reference files referenced one level deep from SKILL.md.

Fill in placeholder code bodies ('// Implementation here', '// Test edge case') in the Step 2 and Step 4 examples so the core workflow examples are fully executable.

DimensionReasoningScore

Conciseness

At ~575 lines the body is noticeably verbose, with redundant sections ('Best Practices' overlaps 'Core Principles', 'Common Testing Mistakes' overlaps 'Testing Patterns', and coverage is covered both in Step 7 and a separate 'Test Coverage Verification' section) that could be trimmed.

3 / 5

Actionability

Provides mostly executable guidance — a real package-manager detector command, a runner command matrix, and concrete Jest/Vitest/Bun/Playwright code patterns — with only minor gaps like placeholder bodies ('// Implementation here', '// Test edge case').

4 / 5

Workflow Clarity

The 8-step TDD workflow is clearly sequenced with explicit RED and GREEN validation gates, multiple documented RED-state paths, checkpoint commits with verification, and a coverage checkpoint, providing strong feedback loops for error recovery.

5 / 5

Progressive Disclosure

The skill is a single monolithic file with no bundle references; internal section structure is good, but substantial blocks (testing patterns, mocking recipes, CI integration) are inlined that could be split into one-level-deep reference files for easier navigation.

3 / 5

Total

15

/

20

Passed

Description

87%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 is strong: it states concrete capabilities, uses third person, and provides an explicit 'Use when...' trigger covering the main development scenarios. Minor room to add synonyms (TDD, test coverage) for richer trigger terms.

DimensionReasoningScore

Specificity

Lists several concrete actions ('writing new features, fixing bugs, or refactoring code') and a specific enforcement ('Enforces test-driven development with 80%+ coverage'), but actions stay fairly high-level without naming tools or exact outputs.

4 / 5

Completeness

Explicitly answers both 'what' (enforces TDD with 80%+ coverage across unit/integration/E2E) and 'when' via a clear 'Use this skill when...' trigger, using third person voice.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('writing new features', 'fixing bugs', 'refactoring code') with good coverage, but misses common synonyms like 'TDD', 'unit tests', or 'test coverage' as standalone triggers.

4 / 5

Distinctiveness Conflict Risk

Targets a clear TDD-specific niche with distinct triggers ('test-driven development', '80%+ coverage'), making conflict with other skills minimal.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (584 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository
affaan-m/ECC
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.