api-testing-helper
Api Testing Helper - Auto-activating skill for API Development. Triggers on: api testing helper, api testing helper Part of the API Development skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill api-testing-helperOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is essentially a placeholder with no substantive content. It provides only a category label ('API Development') and a repeated skill name as triggers, failing to describe any concrete capabilities, use cases, or natural trigger terms. It would be nearly impossible for Claude to correctly select this skill from a library.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Send HTTP requests, validate API responses, generate test cases, mock endpoints').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when testing APIs, debugging endpoints, sending REST requests, or working with HTTP methods').
Add file types, protocols, or tools to improve distinctiveness (e.g., 'REST APIs, GraphQL, OpenAPI specs, .json responses, curl commands').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Api Testing Helper' and 'API Development' are abstract labels with no indication of what the skill actually does (e.g., send requests, validate responses, mock endpoints). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague category label, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'api testing helper' repeated twice, which is not a natural phrase users would say. Missing common terms like 'test endpoint', 'API request', 'REST', 'HTTP', 'Postman', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Development' is extremely broad and could conflict with skills for API design, documentation, code generation, debugging, or any other API-related task. No distinguishing characteristics are provided. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes what an API testing helper skill might do but provides absolutely no actionable guidance, code examples, or concrete instructions. The entire content could be replaced with actual API testing techniques, tool usage, and executable examples.
Suggestions
Add concrete, executable code examples for common API testing scenarios (e.g., using curl, httpie, or Python requests library to test endpoints)
Include specific validation steps and expected response patterns for different HTTP methods and status codes
Provide actual testing workflows with tools like Postman, pytest, or similar - showing request/response examples
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable instructions
| 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 vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual instructions on how to test APIs. The content only describes what the skill claims to do without showing how. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured navigation to actual implementation details. | 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.