CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-add-integration-tests

Add integration/E2E tests to existing codebase using Design Docs

60

Quality

71%

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 ./skills/recipe-add-integration-tests/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 content is a well-structured orchestration recipe with highly actionable, concrete subagent invocations and an exceptionally clear validated workflow including feedback loops. It is token-efficient and avoids over-explanation, with only slight room to tighten repeated gating language.

DimensionReasoningScore

Conciseness

The body is dense, procedural, and assumes Claude's competence without re-explaining basic concepts, though the repeated gating language (Local authority gate, Review Resolution Gate, response gates) could be tightened slightly.

4 / 5

Actionability

Concrete guidance is strong: exact subagent_type values, field-by-field prompt construction, literal prompt templates, and a commit message format, though some fields remain placeholders like '[confirmed changed integration/E2E test paths]'.

4 / 5

Workflow Clarity

A clear 7-step sequence carries explicit validation checkpoints (response gates, quality-fixer statuses) and feedback loops (Step 5 re-review, Step 6 stub_detected returning to Step 3), matching the top anchor for error recovery and checklists.

5 / 5

Progressive Disclosure

The body is well-organized into headed sections and ordered steps with one-level cross-skill pointers (references/review-resolution.md), and no bundle files exist to require splitting; only minor inlining of detailed prompt construction keeps it from a 5.

4 / 5

Total

17

/

20

Passed

Description

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

The description is specific and distinguishable but incomplete: it states a clear capability tied to Design Docs yet omits any explicit 'when to use' trigger guidance. Trigger-term coverage is good but could add common synonyms.

Suggestions

Append a 'Use when...' clause naming concrete triggers, e.g. 'Use when the user asks to add integration or end-to-end tests to an existing backend, frontend, or fullstack implementation that has Design Docs.'

Add natural synonyms such as 'end-to-end tests' or 'test coverage' alongside 'integration/E2E tests' to broaden trigger matching.

Optionally enumerate the concrete actions (skeleton generation, implementation, review, quality checks) so specificity moves toward comprehensive coverage.

DimensionReasoningScore

Specificity

The phrase 'Add integration/E2E tests to existing codebase using Design Docs' names the domain and one concrete action (adding tests) with its input source, but coverage is limited to a single action rather than a comprehensive set.

3 / 5

Completeness

It clearly states what the skill does but offers no 'Use when...' trigger clause, which per the rubric caps completeness at 3 with only a weakly implied 'when'.

3 / 5

Trigger Term Quality

'integration/E2E tests' and 'Design Docs' are natural terms a user would say, though synonyms like 'end-to-end tests' or 'test coverage' are absent, leaving a few common variations missing.

4 / 5

Distinctiveness Conflict Risk

The combination of integration/E2E test generation driven specifically by Design Docs carves a clear niche with mostly distinct triggers, with only minor overlap risk against generic test-generation skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

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.