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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill running-integration-tests69
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 73%
↑ 1.07xAgent success when using this skill
Validation for skill structure
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 excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would say, explicitly answers both what and when, and has a clear distinctive niche. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'automates environment setup, database seeding, service orchestration, and cleanup' and 'handles database creation, migrations, seeding, and dependent service management'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (run/manage integration test suites, automate environment setup, database seeding, etc.) AND when ('Use this skill when the user asks to...', 'triggered by phrases such as...'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'run integration tests', 'execute integration tests', '/run-integration', '/rit', 'integration tests', 'test suites', 'code coverage'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on integration tests with distinct triggers like '/run-integration', '/rit'. Unlikely to conflict with unit testing or other test-related skills due to explicit 'integration' focus and specific command triggers. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%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 too abstract and descriptive rather than instructive. It explains what integration testing is and what the skill conceptually does, but provides no executable commands, actual configuration examples, or specific tool invocations. Claude needs concrete guidance on how to actually run these tests, not descriptions of the process.
Suggestions
Replace abstract descriptions with actual executable commands (e.g., 'pytest test/integration/ --cov=src' or 'docker-compose -f docker-compose.test.yml up -d')
Add a concrete configuration example showing what test/integration/config.json should contain
Include validation checkpoints with specific error handling (e.g., 'If database connection fails, check .env.test for DB_HOST')
Remove explanatory filler text like 'This skill empowers Claude' and 'ensuring seamless interactions' - start directly with actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what integration tests are, what cleanup means). Phrases like 'empowers Claude' and 'ensuring seamless interactions' are filler that add no actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The examples describe what 'the skill will' do abstractly rather than showing actual commands, scripts, or configuration examples Claude should use. | 1 / 3 |
Workflow Clarity | Steps are listed (prepare, execute, cleanup) but lack specific validation checkpoints, error handling, or feedback loops. No guidance on what to do if database setup fails or tests hang. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with sections, but references to config files (test/integration/config.json, .env.test) are mentioned without linking to examples or detailed documentation. No external file references for advanced usage. | 2 / 3 |
Total | 6 / 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 | |
- 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.