CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/test-driven-development

Master Test-Driven Development with deterministic red-green-refactor workflows, test-first feature delivery, bug reproduction through failing tests, behavior-focused assertions, and refactoring safety; use when implementing new functions, changing APIs, fixing regressions, or restructuring code under test.

71

Quality

89%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

77%

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

The body is actionable and clearly sequenced with executable examples and an explicit validation checkpoint, and it is organized as a navigation hub. It is slightly padded by a redundant language variant, and the references it points to are not present in the bundle.

Suggestions

Drop the Elixir variant of the trivial add example (or replace it with a non-trivial example) to remove redundant tokens for a concept Claude already understands.

Ensure the referenced files under references/ (cycle-write-test-first.md, design-aaa-pattern.md, etc.) actually exist in the bundle so the References table navigates to real content.

Tighten the Quick Commands section by consolidating the four bash blocks into a single block with comments, reducing structural repetition.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured, but the full Elixir variant of the trivial `add` example duplicates the TypeScript red-green-refactor walkthrough for a concept Claude already knows, which is padding that could be tightened.

2 / 3

Actionability

Provides fully executable TypeScript/Elixir code and copy-paste-ready commands ("bun test", "bun test --watch", "mix test") with concrete BAD/GOOD examples, matching the score-3 anchor for copy-paste-ready guidance.

3 / 3

Workflow Clarity

The 5-step workflow is clearly sequenced with an explicit validation checkpoint ("Run tests and verify failure is for the expected reason") and a green-suite guard during refactor; this is an iterative non-destructive dev loop, so the destructive/batch cap does not apply, placing it at score 3 rather than 2.

3 / 3

Progressive Disclosure

The body is a well-signaled navigation hub with a one-level-deep References table, but the referenced bundle files (e.g. references/cycle-write-test-first.md) are not present in the bundle, so navigation cannot be completed — structure is good but the linked references are missing, capping this below 3.

2 / 3

Total

10

/

12

Passed

Description

100%

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 specific, written in third person, and clearly states both capabilities and explicit use-when triggers with natural phrasings a user would say. It is concise while covering what and when comprehensively.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "red-green-refactor workflows", "test-first feature delivery", "bug reproduction through failing tests", "behavior-focused assertions", and "refactoring safety" — matching the score-3 anchor that lists several specific actions.

3 / 3

Completeness

Explicitly answers both what (the TDD workflows/behaviors listed) and when ("Use when writing unit tests... especially when a user says 'write tests first'..."), matching the score-3 anchor that has both with explicit triggers; it is above score 2 because the 'when' is stated, not merely implied.

3 / 3

Trigger Term Quality

Covers natural user phrasings users would actually say ("write tests first", "TDD", "test before code") alongside task terms (unit tests, regressions, refactoring); not just technical jargon, so it is above the score-2 'missing common variations' anchor.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (TDD specifically) with distinct triggers unlikely to fire for unrelated skills; it is not the generic 'helps with code' score-1 case nor the still-overlapping score-2 case.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 missing

Warning

referenced_paths_exist

Referenced path issues: 12 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents