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.
31
0%
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
0%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 restates the skill name without providing any meaningful detail about capabilities, actions, or usage triggers. It duplicates the trigger term, lacks concrete actions, and provides no guidance for Claude to distinguish this skill from other testing-related skills. It would be nearly useless in a multi-skill selection scenario.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures test frameworks, generates integration test boilerplate, sets up test databases and mock services, creates Docker Compose files for test environments.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to set up integration tests, configure test environments, create test fixtures, or scaffold end-to-end testing infrastructure.'
Remove the duplicate trigger term and add varied natural keywords users might say, such as 'test environment setup', 'test scaffolding', 'e2e test config', or specific framework names like 'Jest', 'pytest', 'Testcontainers'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Integration Test Setup' without describing any concrete actions. There are no specific capabilities listed—no mention of what it actually does (e.g., configures test frameworks, generates test fixtures, sets up database connections). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is essentially just restating the skill name as a trigger. There is no explicit 'Use when...' clause with meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundantly listed as 'integration test setup, integration test setup' (duplicated). There are no natural keyword variations a user might say, such as 'test configuration', 'test environment', 'test scaffolding', 'e2e tests', or specific framework names. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too generic—'integration test setup' could overlap with many testing-related skills. Without specifying the technology, framework, or specific setup actions, it would easily conflict with other test automation or testing skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell—it contains only meta-descriptions and trigger phrases but provides absolutely no actionable content about integration test setup. There is no code, no concrete guidance, no workflow, and no references to supplementary materials. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for setting up integration tests (e.g., pytest fixtures with database setup/teardown, Jest integration test configuration with test containers).
Define a clear multi-step workflow for integration test setup, including validation steps such as verifying test database connectivity or confirming test isolation.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') and replace them with actual instructional content—commands, configuration files, and patterns.
If the topic is broad, provide a concise quick-start section and link to separate files for framework-specific guides (e.g., PYTEST_INTEGRATION.md, JEST_INTEGRATION.md).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does ('provides automated assistance') without providing any actual guidance, code, or actionable content. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no commands, no specific steps for setting up integration tests. The content only describes what the skill could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The phrase 'step-by-step guidance' is promised but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed files, no structured navigation, and no meaningful content organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 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
3076d78
- 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.