api-tester
Sends HTTP requests to REST and GraphQL API endpoints, validates response codes, headers, and payloads, measures response times against SLA thresholds, generates structured test suites, and produces test reports covering functional, security, and performance scenarios. Use when the user asks about testing APIs, validating endpoints, checking HTTP status codes or response bodies, load testing, stress testing, debugging REST or GraphQL services, testing authentication flows, checking rate limiting, detecting SQL injection or OWASP API vulnerabilities, or integrating API tests into CI/CD pipelines.
93
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that thoroughly covers specific capabilities, provides abundant natural trigger terms, and clearly delineates both what the skill does and when it should be used. It uses proper third-person voice throughout and is well-structured with a clear separation between the capability statement and the trigger clause. The description is comprehensive without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: sends HTTP requests, validates response codes/headers/payloads, measures response times against SLA thresholds, generates structured test suites, and produces test reports covering functional, security, and performance scenarios. | 3 / 3 |
Completeness | Clearly answers both 'what does this do' (sends HTTP requests, validates responses, measures response times, generates test suites, produces reports) AND 'when should Claude use it' with an explicit 'Use when...' clause listing numerous trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'testing APIs', 'validating endpoints', 'HTTP status codes', 'response bodies', 'load testing', 'stress testing', 'REST', 'GraphQL', 'authentication flows', 'rate limiting', 'SQL injection', 'OWASP', 'CI/CD pipelines'. These are all terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around API testing specifically. The combination of REST/GraphQL, HTTP validation, SLA thresholds, security testing (OWASP, SQL injection), and CI/CD integration makes it highly distinguishable from general coding, security, or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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, well-structured skill that provides executable code examples, clear multi-step workflows with explicit validation gates and feedback loops, and good progressive disclosure to supporting files. The main area for improvement is conciseness — the code examples, while valuable, are lengthy, and some workflow steps contain somewhat generic guidance that could be tightened. Overall it's a high-quality skill that would effectively guide Claude through API testing tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic concepts Claude already knows, but the code examples are quite lengthy and could be tightened. Some sections like the workflow steps include guidance that's somewhat generic (e.g., 'Enumerate all API endpoints from specs'). Overall reasonable but not maximally lean. | 2 / 3 |
Actionability | Provides fully executable Playwright/fetch test code and k6 load test scripts that are copy-paste ready. Includes specific commands (zap-cli, k6 run), concrete thresholds (P95 ≤ 200ms, error rate < 0.1%), and a structured report template with exact fields. Very concrete and actionable throughout. | 3 / 3 |
Workflow Clarity | Step 4 provides explicit validation gates with a clear sequence (functional → security → performance → integration), explicit 'do not proceed if a gate fails' instruction, and feedback loops (fix → re-run until pass) for each gate. The 5-step workflow is well-sequenced with clear checkpoints for destructive/batch-like operations. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to EXAMPLES.md, TEMPLATES.md, and ADVANCED.md. Content is appropriately split — the main file covers the workflow and key patterns while deferring full reference suites, report templates, and advanced topics to separate files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-agents
- Commit
010799b
- 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.