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.
36
Quality
7%
Does it follow best practices?
Impact
86%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/integration-test-setup/SKILL.mdQuality
Discovery
7%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 description is essentially a placeholder that provides almost no useful information for skill selection. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The repetitive trigger terms and absence of specific capabilities make it nearly impossible for Claude to confidently select this skill over alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Scaffolds integration test suites, configures test databases, sets up API mocking, and generates test fixtures'
Include a proper 'Use when...' clause with natural trigger terms: 'Use when setting up integration tests, configuring test environments, or when the user mentions end-to-end testing, test database setup, or API test configuration'
Add technology-specific keywords users might mention, such as specific testing frameworks (Jest, Pytest, JUnit), database types, or CI/CD integration terms
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Integration Test Setup' without describing any concrete actions. There are no specific capabilities listed - no verbs describing what the skill actually does (e.g., configure, generate, scaffold). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' line is not a proper 'Use when...' clause and just repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('integration test setup' repeated twice) and overly narrow. Missing natural variations users might say like 'set up tests', 'test configuration', 'testing framework', 'test suite setup', or specific framework names. | 1 / 3 |
Distinctiveness Conflict Risk | While 'integration test' is somewhat specific compared to generic 'testing', it could still overlap with other test-related skills. The lack of specific actions or technologies makes it harder to distinguish from unit test setup or other test automation skills. | 2 / 3 |
Total | 5 / 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 is essentially a placeholder template with no actual instructional content. It describes what a skill should do rather than providing any concrete guidance for integration test setup. The content fails to teach Claude anything actionable about setting up integration tests, lacking code examples, specific frameworks, configuration snippets, or any technical details.
Suggestions
Add concrete, executable code examples for at least one integration test framework (e.g., pytest with fixtures, Jest with test containers)
Include specific configuration files or setup commands (e.g., docker-compose for test databases, pytest.ini settings)
Define a clear workflow with steps: 1) Set up test environment, 2) Configure test database, 3) Write test fixtures, 4) Validate test isolation
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual technical instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains obvious concepts Claude already knows. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' add no actionable value and waste tokens. | 1 / 3 |
Actionability | The skill contains zero concrete code, commands, or executable guidance. It only describes what it claims to do ('Generates production-ready code') without actually providing any examples, configurations, or specific instructions for integration test setup. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all. Despite claiming to provide 'step-by-step guidance,' the skill contains no actual steps, sequences, or validation checkpoints for setting up integration tests. | 1 / 3 |
Progressive Disclosure | The content has some structure with clear section headers, but there are no references to detailed materials, no links to examples or configuration files, and the sections themselves contain no substantive content to organize. | 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
f17dd51
- 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.