CtrlK
BlogDocsLog inGet started
Tessl Logo

tdd-workflow

新機能の作成、バグ修正、コードのリファクタリング時にこのスキルを使用します。ユニット、統合、E2Eテストを含む80%以上のカバレッジでテスト駆動開発を強制します。

62

Quality

73%

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

Quality

Content

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

A highly actionable TDD skill with strong executable examples and a clear sequenced workflow including validation checkpoints. Its main weaknesses are verbosity (restate-the-obvious lists and large inlined reference blocks) and a monolithic single-file structure that underuses progressive disclosure.

Suggestions

Trim the 'ベストプラクティス' (best practices) and '成功指標' (success metrics) lists, which restate TDD fundamentals Claude already knows, to recover context budget.

Move the full mock-example blocks (Supabase/Redis/OpenAI) and the lengthy Playwright E2E specs into a separate references file linked from the body, keeping only one concise example inline.

Add an explicit error-recovery feedback loop to step 6 (refactor) and step 7 (coverage) — e.g., 'if coverage < 80%, identify untested paths and add tests before re-running' — to strengthen validation checkpoints.

DimensionReasoningScore

Conciseness

Noticeably verbose at ~400 lines: the 10-item 'best practices' list, success-metrics list, and restated core principles restate TDD concepts Claude already knows, and the three large mock examples plus full E2E specs pad the context considerably.

2 / 5

Actionability

Provides copy-paste ready executable examples throughout: concrete Jest/Vitest unit tests, API integration tests, full Playwright E2E specs, mock setups, and exact bash commands (npm test, npm run test:coverage).

5 / 5

Workflow Clarity

The 7-step TDD workflow is clearly sequenced with validation checkpoints (run tests expecting failure, re-run expecting success, verify 80% coverage), but error-recovery feedback loops are only lightly sketched rather than explicit.

4 / 5

Progressive Disclosure

Content is well-sectioned but entirely monolithic in a single file with no bundle files; large reference-style blocks (mock patterns, full E2E specs, coverage config) are inlined where a one-level reference would reduce load, and no external navigation is signaled.

3 / 5

Total

14

/

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 clear, trigger-explicit description that answers both what (TDD enforcement with 80%+ coverage) and when (feature/bug/refactor work). It is concise and mostly free of fluff, with minor room to sharpen the action list and reduce overlap with generic coding triggers.

DimensionReasoningScore

Specificity

Names the domain (TDD with 80% coverage) and lists several concrete actions (unit, integration, E2E tests; enforcing coverage), but framing ('enforces TDD') is more of a guarantee than a distinct enumerated action list.

4 / 5

Completeness

Explicitly answers both 'what' (enforces TDD with 80%+ coverage across unit/integration/E2E) and 'when' (when creating features, fixing bugs, refactoring) with concrete trigger phrases via the 'このスキルを使用します' clause.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('creating new features', 'fixing bugs', 'refactoring code') plus test-type keywords, though it omits common synonyms like 'writing tests' or 'coverage'.

4 / 5

Distinctiveness Conflict Risk

The TDD/coverage-enforcement niche is fairly distinct from other skills, but 'feature creation / bug fixing / refactoring' triggers are broad and could overlap with general coding 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
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.