running-integration-tests
This skill enables Claude to run and manage integration test suites. It automates environment setup, database seeding, service orchestration, and cleanup. Use this skill when the user asks to "run integration tests", "execute integration tests", or any command that implies running integration tests for a project, including specifying particular test suites or options like code coverage. It is triggered by phrases such as "/run-integration", "/rit", or requests mentioning "integration tests". The plugin handles database creation, migrations, seeding, and dependent service management.
67
53%
Does it follow best practices?
Impact
73%
1.08xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-batch-20251204-000554/plugins/testing/integration-test-runner/skills/integration-test-runner/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly articulates what the skill does (run integration test suites with environment setup, database management, and service orchestration) and when to use it (with explicit trigger phrases and natural language patterns). It uses third person voice consistently and provides enough specificity to distinguish it from other testing-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'automates environment setup, database seeding, service orchestration, and cleanup' and further details 'database creation, migrations, seeding, and dependent service management'. | 3 / 3 |
Completeness | Clearly answers both 'what' (run/manage integration test suites, automate environment setup, database seeding, service orchestration, cleanup) and 'when' (explicit 'Use this skill when...' clause with specific trigger phrases and scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'run integration tests', 'execute integration tests', '/run-integration', '/rit', 'integration tests', 'test suites', 'code coverage'. Good coverage of both natural language and command-style triggers. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to integration tests specifically, with distinct triggers like '/run-integration' and '/rit'. The focus on database seeding, service orchestration, and environment setup distinguishes it from unit test or general testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is almost entirely abstract and descriptive, lacking any concrete commands, code examples, configuration templates, or executable guidance. It reads more like a marketing description of what the skill does rather than actionable instructions Claude can follow. The absence of specific tools, scripts, database commands, or validation steps makes it essentially non-functional as a skill definition.
Suggestions
Replace abstract descriptions with concrete, executable commands for each workflow step (e.g., specific database creation commands, migration scripts, test runner invocations with actual CLI syntax).
Add a concrete configuration example showing the expected format of `test/integration/config.json` or `.env.test` so Claude knows what to look for and how to set it up.
Include explicit validation checkpoints with specific commands (e.g., 'Verify database is seeded: `psql -c "SELECT count(*) FROM test_table"`') and error recovery steps for when setup or tests fail.
Remove the 'Overview', 'How It Works', and 'Integration' sections which provide no actionable information, and replace them with a quick-start section containing actual runnable commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what integration tests are, what cleanup means, what environment preparation involves). Phrases like 'ensuring seamless interactions between various system components' and 'This skill empowers Claude to execute comprehensive integration tests' are filler. The 'How It Works' and 'When to Use' sections largely restate the description without adding actionable value. | 1 / 3 |
Actionability | There are no concrete commands, executable code, configuration examples, or specific tool invocations. The examples describe what the skill 'will do' in abstract terms but never show actual commands, scripts, database setup steps, or configuration file formats. Nothing is copy-paste ready. | 1 / 3 |
Workflow Clarity | The workflow steps are vague abstractions ('Prepare the test environment', 'Execute all integration test suites') with no specific commands, validation checkpoints, or error recovery steps. For a skill involving database creation, migrations, and service orchestration—all potentially destructive operations—there are no validation or feedback loops. | 1 / 3 |
Progressive Disclosure | The content has some structural organization with headers and sections, but there are no references to supporting files, no bundle files exist, and content that could be split (e.g., configuration details, specific test runner commands) is neither inline nor referenced. The sections are organized but contain mostly filler rather than useful layered content. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
b8c7056
- 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.