CtrlK
BlogDocsLog inGet started
Tessl Logo

integration-e2e-testing

Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria. Use when designing integration tests, E2E tests, or reviewing test quality.

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The content is well-organized and specific, providing concrete ROI formulas, budget rules, and skeleton annotation patterns. It leans verbose and prescriptive rather than executable, with no explicit validation checkpoint in the design workflow and most detail kept inline despite an available reference.

Suggestions

Add an explicit validation/review checkpoint (e.g., 'After selecting candidates: verify each maps to an AC, re-check budget per lane, then emit skeletons') to give the workflow a concrete feedback loop.

Trim or move the ROI calculation examples and repeated lane/budget restatements into the existing reference file, keeping the body as a concise overview with one-level-deep links.

Include at least one fully executable test skeleton (with wrapped comment annotations in a real language) so the skeleton spec becomes copy-paste ready rather than purely prescriptive.

DimensionReasoningScore

Conciseness

The body is dense and largely assumes Claude's competence, but the multi-step journey definition, classification tables, and repeated budget/ROI restatements add length that could be tightened without losing clarity.

2 / 3

Actionability

It gives concrete skeleton/comment patterns and ROI formulas, but the bulk is specification (rules and tables) rather than copy-paste executable test code, and lane-selection guidance is prose rather than a worked example.

2 / 3

Workflow Clarity

Selection criteria, lanes, and budgets are well sequenced, but there is no explicit validate/review checkpoint or feedback loop for the test-design workflow, so checkpoints are implicit rather than enforced.

2 / 3

Progressive Disclosure

The single references/e2e-design.md link is real and one-level deep, but the body itself is a long monolithic specification with most material inline; the lane and ROI tables could be split or summarized behind clearer signposting.

2 / 3

Total

8

/

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 concise, specific, and follows the recommended pattern of stating capabilities then an explicit 'Use when' trigger clause. It uses correct third-person voice and avoids fluff, overlapping only with adjacent testing skills in a well-bounded way.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Integration and E2E test design principles, ROI calculation, test skeleton specification, and review criteria' — matching the level-3 anchor of naming several specific operations.

3 / 3

Completeness

Explicitly answers both what it does (design principles, ROI, skeletons, review) and when to use it via the 'Use when designing integration tests, E2E tests, or reviewing test quality' clause, matching the level-3 anchor.

3 / 3

Trigger Term Quality

Covers natural terms a user would actually say — 'designing integration tests, E2E tests, or reviewing test quality' — with good variation matching the level-3 anchor.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche — integration/E2E test design and review — with distinct triggers unlikely to overlap with unrelated skills.

3 / 3

Total

12

/

12

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