CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-integration-testing

Use when the user requests integration testing, feature validation, or test plan execution

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-integration-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is a tight, actionable integration-testing playbook with concrete commands, an executable example, explicit validation checkpoints, and well-organized sections. Its only weakness is minor verbosity in a few explanatory passages that restate the obvious.

DimensionReasoningScore

Conciseness

Mostly efficient and well-organized, but the Overview sentence and some CRITICAL/Fix elaboration restate concepts Claude already knows (e.g., explaining that subagents must follow prerequisites); it could be tightened without losing clarity.

2 / 3

Actionability

Provides concrete file paths, shell commands (docker compose, npm run migrate, curl, sqlite3), an executable example spec, and a quick-reference table; guidance is copy-paste ready rather than abstract.

3 / 3

Workflow Clarity

A clearly numbered 5-step process with a Prerequisites gate, a Red Flags/STOP section as validation checkpoints, and an explicit failure-handling loop (fix -> re-run); checkpoints are explicit.

3 / 3

Progressive Disclosure

At 70 lines with no bundle files, the content is appropriately self-contained and organized into clear sections (Overview, Core Process, Quick Reference, Red Flags, Example); no nested references, so structure is one level deep and easy to navigate.

3 / 3

Total

11

/

12

Passed

Description

67%

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 has a clear trigger clause and a defined domain, but it under-specifies the concrete actions and omits the subagent/spec-centric workflow that distinguishes this skill. Trigger terms are relevant but limited in coverage.

Suggestions

List concrete actions (e.g., write verifiable test specs, dispatch subagents to execute them, collect pass/fail results) to lift specificity to 3.

Add common user phrasings like 'run integration tests' or 'verify a feature works end-to-end' for broader trigger coverage.

Mention subagent-based execution in the description to reduce overlap with general test-writing skills.

DimensionReasoningScore

Specificity

Names the domain (integration testing) and a few actions (test plan execution, feature validation), but does not enumerate multiple concrete actions like writing specs, spawning subagents, or fixing failures.

2 / 3

Completeness

Contains an explicit 'Use when...' clause ('Use when the user requests integration testing, feature validation, or test plan execution') that answers both what the skill does and when to use it.

3 / 3

Trigger Term Quality

Includes natural phrases a user might say ('integration testing', 'feature validation', 'test plan execution'), but misses common variations like 'run integration tests', 'verify a feature works', or 'execute test plan'.

2 / 3

Distinctiveness Conflict Risk

The integration-testing-with-subagents niche is fairly specific, but the description's trigger wording could overlap with generic test-writing skills since it does not mention subagent execution or test specs.

2 / 3

Total

9

/

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
av/harbor
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.