running-integration-tests
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill running-integration-testsThis 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.
Validation
69%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 11 / 16 Passed | |
Implementation
20%This skill content is descriptive rather than instructive—it explains what the skill does conceptually but provides no actionable commands, code examples, or concrete configuration guidance. Claude cannot execute anything based on this content because it lacks specific commands, scripts, file paths, or executable examples. The workflow is outlined at a high level but missing validation steps and error recovery guidance.
Suggestions
Add concrete, executable commands for each step (e.g., actual shell commands to run tests, database setup scripts, or the exact CLI invocation)
Include a real configuration example showing the expected structure of 'test/integration/config.json' or '.env.test'
Add validation checkpoints with specific error handling (e.g., 'If database connection fails, check X; if migrations fail, run Y')
Remove filler phrases like 'empowers Claude' and 'ensuring seamless interactions'—focus on what Claude should actually do
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Verbose and padded with unnecessary explanations. Phrases like 'empowers Claude to execute comprehensive integration tests' and 'ensuring seamless interactions' are filler. The entire content describes what the skill does rather than providing actionable instructions Claude can execute. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance. The examples describe what 'the skill will' do in abstract terms but provide no actual commands, scripts, or configuration examples. There's nothing copy-paste ready or executable. | 1 / 3 |
Workflow Clarity | Steps are listed (prepare, execute, cleanup) but lack specifics. No validation checkpoints, no error handling guidance, no feedback loops for when tests fail or environment setup encounters issues. The sequence is present but shallow. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline with no references to detailed documentation. Mentions config files like 'test/integration/config.json' but doesn't link to examples or schemas. Could benefit from separating configuration details into referenced files. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and has a clear distinctive niche that minimizes conflict with other skills.
| 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'. | 3 / 3 |
Completeness | Clearly answers both what (run/manage integration test suites, automate setup, seeding, orchestration, cleanup) AND when (explicit 'Use this skill when...' clause with specific trigger phrases and scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'run integration tests', 'execute integration tests', '/run-integration', '/rit', 'integration tests', 'test suites', 'code coverage'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on integration tests with distinct triggers like '/run-integration', '/rit', and specific mention of database/service orchestration that distinguishes it from unit testing or other test-related skills. | 3 / 3 |
Total | 12 / 12 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.