integration-test-setup
Integration Test Setup - Auto-activating skill for Test Automation. Triggers on: integration test setup, integration test setup Part of the Test Automation skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill integration-test-setupOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without providing any actionable information. It lacks concrete capabilities, natural trigger terms, and explicit usage guidance. Claude would struggle to know when to select this skill over other testing-related skills.
Suggestions
Add specific concrete actions like 'Configure test frameworks, set up test databases, create mock services, define test fixtures and data seeding'
Include a 'Use when...' clause with explicit triggers: 'Use when the user needs to set up integration tests, configure test environments, or mentions terms like integration testing, test setup, test fixtures, or test database'
Add natural keyword variations users might say: 'integration tests', 'test environment setup', 'test configuration', 'API testing setup', 'database test setup'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Integration Test Setup' without describing any concrete actions. There are no specific capabilities listed like 'configure test frameworks', 'set up test databases', or 'create test fixtures'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title, and there is no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('integration test setup' listed twice) and lack natural variations users might say like 'set up tests', 'test configuration', 'testing environment', 'e2e tests', or 'end-to-end testing'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'integration test' is somewhat specific compared to generic 'testing', it could still overlap with unit testing, e2e testing, or general test automation skills. The lack of specific actions makes it harder to distinguish from related testing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no substantive content. It describes what a skill about integration test setup might do but provides zero actual guidance, code examples, framework-specific instructions, or actionable steps for setting up integration tests.
Suggestions
Add concrete code examples for at least one test framework (e.g., Jest or pytest) showing actual integration test setup patterns
Include specific steps for common integration test scenarios: database setup/teardown, API mocking, test isolation strategies
Provide executable configuration snippets for test runners and environment setup
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual instructional content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are meaningless filler without actual content. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The entire skill describes what it could do rather than providing any executable guidance for integration test setup. | 1 / 3 |
Workflow Clarity | No actual workflow or steps are defined. The skill claims to provide 'step-by-step guidance' but contains zero steps for setting up integration tests. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, examples, or supporting documentation that would actually teach integration test setup. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.