api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill api-testingOverall
score
85%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%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 is a strong description with excellent specificity, naming concrete actions and specific tools/frameworks. The trigger terms are natural and comprehensive for developers. The main weakness is the absence of an explicit 'Use when...' clause, which limits Claude's ability to know exactly when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when testing HTTP endpoints, writing API tests, validating REST responses, or setting up integration tests with Supertest or httpx.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Test REST APIs, GraphQL, request/response validation, authentication, and error handling' along with specific tools (Supertest, httpx, pytest). | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities and tools, but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'HTTP', 'API testing', 'REST APIs', 'GraphQL', 'authentication', 'TypeScript', 'Python', plus specific library names that developers would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on HTTP API testing with named frameworks (Supertest, httpx, pytest); unlikely to conflict with general testing or other API-related skills due to specific technology stack mentions. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill that efficiently covers API testing patterns for both TypeScript and Python ecosystems. The code examples are complete and immediately usable. The main weakness is the lack of explicit workflow guidance for setting up test infrastructure or a clear sequence for developing comprehensive API test suites.
Suggestions
Add a brief workflow section showing the sequence: setup test client → write happy path tests → add error cases → validate coverage
Include a validation checkpoint pattern, e.g., 'Run tests after each new endpoint to catch regressions early'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, jumping directly into installation and executable code examples without explaining what APIs are or how HTTP works. Every section provides actionable code without unnecessary preamble. | 3 / 3 |
Actionability | All code examples are complete, executable, and copy-paste ready. The skill covers both TypeScript and Python with real imports, proper test structure, and specific assertions that can be used immediately. | 3 / 3 |
Workflow Clarity | While individual test patterns are clear, there's no explicit workflow for setting up a test suite from scratch or validation steps. The 'Best Practices' section lists recommendations but doesn't sequence them into a clear process for test development. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers progressing from basic setup to advanced topics (GraphQL, performance). The 'See Also' section provides clear one-level-deep references to related skills without nested indirection. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
68%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
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 |
license_field | 'license' field is missing | 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.