integration-test-generator
Integration Test Generator - Auto-activating skill for API Integration. Triggers on: integration test generator, integration test generator Part of the API Integration skill category.
34
Quality
3%
Does it follow best practices?
Impact
90%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/16-api-integration/integration-test-generator/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 relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The redundant trigger term listing suggests auto-generated content that wasn't reviewed.
Suggestions
Add specific capabilities: 'Generates integration tests for REST APIs including request/response validation, error handling, and authentication flows'
Include a proper 'Use when...' clause: 'Use when the user needs to create API integration tests, test endpoint behavior, mock external services, or validate API contracts'
Add natural trigger term variations: 'API tests, endpoint testing, test my API, integration testing, mock services, test coverage for APIs'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Integration Test Generator') without describing any concrete actions. There are no specific capabilities listed like 'generates test cases', 'mocks API endpoints', or 'validates response schemas'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a circular reference to the skill name. There is no explicit 'Use when...' clause with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundantly listed twice ('integration test generator, integration test generator') and lack natural variations users might say like 'API tests', 'test my endpoint', 'create integration tests', or 'test coverage'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'integration test' is somewhat specific to a testing domain, the lack of detail about what kind of integration tests (REST APIs, GraphQL, database integrations) means it could overlap with general testing skills or API documentation skills. | 2 / 3 |
Total | 5 / 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 template with no actual instructional content. It describes what an integration test generator skill would do without providing any concrete guidance, code examples, or workflows. The entire content could be replaced with a single sentence and would convey the same (lack of) information.
Suggestions
Add concrete, executable code examples showing how to generate integration tests for common API patterns (REST endpoints, webhooks, OAuth flows)
Define a clear workflow with steps: identify endpoints → generate test cases → write assertions → validate responses → handle error scenarios
Include specific examples of test output formats (e.g., pytest fixtures, mock configurations, expected request/response pairs)
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual technical guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific examples of how to actually generate integration tests. The content describes what the skill does in abstract terms without providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples, and no navigation to supporting documentation. It's essentially a placeholder with no real content to disclose. | 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
0c08951
- 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.