integration-test-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill integration-test-generatorIntegration Test Generator - Auto-activating skill for API Integration. Triggers on: integration test generator, integration test generator Part of the API Integration skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%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 listing and lack of concrete actions make this ineffective for Claude to distinguish when to use this skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates integration tests for REST APIs, creates mock server configurations, validates request/response schemas, and produces test fixtures'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks to test API endpoints, write integration tests, mock API responses, or validate API contracts'
Add common file types and technologies: 'Works with OpenAPI specs, Postman collections, .spec.ts files, Jest, or pytest'
| 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. No explicit 'Use when...' clause with meaningful triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('integration test generator' listed twice) and overly specific. Missing natural variations users would say like 'API tests', 'test my endpoint', 'write integration tests', 'test coverage for API'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'API Integration' category and 'integration test' focus provide some specificity, but without concrete actions described, it could overlap with general testing skills or API documentation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It describes what an integration test generator skill should do without providing any concrete guidance, code examples, or actionable steps. The content would be completely unhelpful for actually generating integration tests.
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: 1) Analyze API endpoints, 2) Generate test scaffolding, 3) Add assertions, 4) Validate test coverage
Include specific examples of input (API spec or endpoint) and expected output (generated test code)
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with actual technical guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific examples of how to actually generate integration tests. The content only describes what the skill supposedly does without showing how to do anything. | 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 monolithic block of vague descriptions with no structure for discovery. There are no references to detailed materials, no examples to follow, and no clear organization of information. | 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.