backend-tdd

Backend TDD Agent. Node.js/NestJS 기반 TDD 테스트 작성 및 구현을 담당합니다. 테스트 먼저 작성 후 구현하는 Red-Green-Refactor 사이클을 따릅니다.

Install with Tessl CLI

npx tessl i github:shaul1991/shaul-agents-plugin --skill backend-tdd

What are skills?

Overall
score

61%

Review — 49%

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/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

33%

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 identifies its technical domain (Node.js/NestJS TDD) and methodology (Red-Green-Refactor) but lacks explicit trigger guidance and specific concrete actions. The absence of a 'Use when...' clause significantly weakens Claude's ability to select this skill appropriately from a large skill library.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'write tests', 'TDD', 'unit testing', 'NestJS testing', 'backend tests', or 'test-driven development'

List specific concrete actions such as 'write unit tests', 'create integration tests', 'generate mocks and stubs', 'implement test fixtures'

Include common user phrases and file extensions like '.spec.ts', 'Jest', 'test coverage', 'describe/it blocks' to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	Names the domain (Node.js/NestJS TDD) and mentions the Red-Green-Refactor cycle, but doesn't list specific concrete actions like 'write unit tests', 'create test fixtures', or 'generate mock implementations'.	2 / 3
Completeness	Describes what it does (TDD test writing and implementation) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'TDD', 'Node.js', 'NestJS', 'Red-Green-Refactor', but misses common user variations like 'unit test', 'test-driven', 'backend testing', 'Jest', or 'test coverage'.	2 / 3
Distinctiveness Conflict Risk	The NestJS/Node.js focus provides some distinction, but 'Backend TDD Agent' could overlap with general testing skills or other backend development skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides solid, actionable NestJS TDD examples with executable code that Claude can immediately use. However, it over-explains the TDD concept (which Claude knows), lacks explicit validation checkpoints in the workflow, and could benefit from splitting detailed examples into separate reference files for better progressive disclosure.

Suggestions

Remove or significantly condense the TDD cycle ASCII diagram and conceptual explanation - Claude understands TDD fundamentals

Add explicit validation commands between steps, e.g., 'Run `npm test user.service` - expect RED (failure)', then 'Implement minimal code', then 'Run again - expect GREEN'

Split the extensive code examples into separate files (e.g., UNIT_TEST_EXAMPLES.md, E2E_EXAMPLES.md) and reference them from the main skill

Remove the 'Test Stack' section listing tools - this doesn't add actionable guidance

Dimension	Reasoning	Score
Conciseness	The skill includes useful content but has some verbosity - the ASCII diagram for TDD cycle explains a concept Claude already knows, and the test stack section lists tools without adding actionable value. The code examples are appropriately detailed but could be more condensed.	2 / 3
Actionability	Provides fully executable, copy-paste ready code examples for unit tests (Service, Controller) and E2E tests. Commands are specific and complete. The mock factory pattern and test database setup are immediately usable.	3 / 3
Workflow Clarity	The TDD cycle is described but lacks explicit validation checkpoints. The checklists are helpful but don't include feedback loops for when tests fail unexpectedly or how to recover from common errors. Missing explicit 'run test -> verify failure -> implement -> verify pass' command sequences.	2 / 3
Progressive Disclosure	Content is reasonably organized with clear sections, but it's a monolithic document. The extensive code examples (200+ lines) could be split into separate reference files. No external file references for advanced patterns or detailed API documentation.	2 / 3
	Total	9 / 12 Passed

Validation

91%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.