CtrlK
BlogDocsLog inGet started
Tessl Logo

test-implement

Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.

73

1.06x
Quality

77%

Does it follow best practices?

Impact

99%

1.06x

2 of 3 eval scenarios. Add 1 more for a full score.

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./dev-skills/skills/test-implement/SKILL.md

The canonical home for this skill is test-implement in shinpr/claude-code-workflows

SKILL.md
Quality
Evals
Security

Quality

Content

51%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 body is well-structured as a router with excellent progressive disclosure and a concrete selection table, but it carries some over-explained testing fundamentals, lacks executable code in the body, and does not sequence an implementation workflow with validation checkpoints.

Suggestions

Trim or remove the 'Common Principles' section (AAA, Test Independence, Naming) — these are testing fundamentals Claude already applies; keep only anything repo-specific that is not in the references.

Add a short, explicit implementation workflow (e.g., resolve toolchain → write test following the selected reference → run the configured runner → verify the expected observable behavior) so the body sequences the process rather than only routing to references.

Inline one minimal concrete executable anchor (such as the runner command or a one-line import pattern) so the body has at least one copy-paste-ready action before delegating to references.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the 'Common Principles' section re-explains Arrange-Act-Assert, test independence, and naming — basic testing concepts Claude already knows — which could be trimmed.

3 / 5

Actionability

The Reference Selection table gives concrete, file-path-level routing with explicit 'When to Use' conditions, but the body itself contains no executable code or commands — all implementation detail lives one hop away in the references.

3 / 5

Workflow Clarity

The body presents a routing decision and principles rather than a sequenced multi-step process; there is no explicit workflow sequence and no validation/verification checkpoints in the body.

2 / 5

Progressive Disclosure

A clean overview with a well-signaled reference table pointing to two one-level-deep references (frontend.md, e2e.md, both real files), with content appropriately split between overview and detail.

5 / 5

Total

13

/

20

Passed

Description

92%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 strong, specific description that names concrete test types and tooling, and pairs a clear capability statement with an explicit 'Use when' trigger. The only minor gap is the absence of file-extension synonyms in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness' — giving comprehensive coverage of the test types and tooling concerns.

5 / 5

Completeness

Explicitly answers both what ('Implements React/TypeScript unit, integration, and browser E2E tests...') and when ('Use when creating or completing frontend tests and generated test skeletons') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('frontend tests', 'test skeletons', 'unit/integration/E2E tests') that users would say, but omits file-extension synonyms like .test.tsx or .spec.ts, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Carves a clear frontend-test-implementation niche with distinct triggers (frontend tests, generated test skeletons), giving minimal overlap risk with adjacent skills.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shinpr/claude-code-workflows
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.