api-tester
Test APIs With Request and Validation Guidance
API testing often misses authentication, schema, and error cases. This skill helps create endpoint checks, sample requests, collections, and performance tests.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "api-tester" from https://skillstore.io/skills/curiouslearner-api-tester.md and its manifest at https://skillstore.io/api/skills/curiouslearner-api-tester/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "api-tester". Need quick tests for GET /api/users and POST /api/users.
Expected outcome:
Returns a compact test plan with request methods, headers, sample fields, expected status codes, and validation checks.
Using "api-tester". Prepare authentication tests for a protected endpoint.
Expected outcome:
Produces cases for valid tokens, missing tokens, expired tokens, invalid roles, and expected 401 or 403 responses.
Using "api-tester". Plan a staging load test for user search.
Expected outcome:
Suggests concurrency levels, duration, success criteria, rate-limit checks, and a reporting outline.
Security Audit
SafeAll 119 static findings were adjudicated as false positives caused by Markdown code fences, JavaScript template literals, placeholder API URLs, and normal API testing examples. The reviewed file contains documentation and sample commands only; no prompt injection, covert exfiltration, or automatic execution path was found. Minor documentation hardening is recommended for credential and load testing examples.
Risk Factors
⚙️ External commands (50)
🌐 Network access (58)
🔑 Env variables (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/curiouslearner-api-tester/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/curiouslearner-api-tester?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/curiouslearner-api-tester?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/curiouslearner-api-tester/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/curiouslearner-api-tester.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
CuriousLearner. (2026). api-tester security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/curiouslearner-api-tester/audits/8BibTeX citation
@techreport{curiouslearner-curiouslearner-api-tester-2026,
author = {CuriousLearner},
title = {api-tester security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/curiouslearner-api-tester/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "api-tester security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "CuriousLearner"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/curiouslearner-api-tester/audits/8"
identifiers:
- type: other
value: "skillstore:curiouslearner-api-tester:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Endpoint Smoke Tests
Create quick request checks for new REST endpoints before merging changes.
Contract Validation
Draft schema, status code, and error-path tests for regression coverage.
Performance Baseline
Plan controlled load tests for staging APIs with concurrency and reporting examples.
Try These Prompts
Use api-tester to create GET and POST tests for /api/users. Include headers, sample bodies, and expected status codes.
Use api-tester for my protected API. Generate tests for valid tokens, missing tokens, invalid tokens, and role-based access.
Use api-tester to outline a Postman collection for these endpoints: [list endpoints]. Include variables, test assertions, and error cases.
Use api-tester to design REST and GraphQL tests for [service]. Include contract validation, negative cases, rate limits, and staged load testing.
Best Practices
- Use staging endpoints and test accounts before testing production APIs.
- Keep real tokens in environment variables or secret managers, not in prompts or files.
- Define expected status codes, schemas, and error messages before generating tests.
Avoid
- Do not run load tests against third-party APIs without written authorization.
- Do not paste real bearer tokens, passwords, or API keys into shared prompts.
- Do not treat generated examples as proof that a live endpoint works.
Frequently Asked Questions
Does this skill call APIs by itself?
Can it create Postman collections?
Does it support GraphQL?
Can it help with authentication testing?
Is it safe for production load testing?
What should I provide in a prompt?
Developer Details
Author
CuriousLearnerLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
02f077c174c5335e2f5d02ca15e77b70d9543e58
Maintenance freshness
7/18/2026
Usage
7 downloads · 307 views
File structure
📄 SKILL.md