agentleFS
pankajkumar-codespankajkumar-codes/api-test-pilot-skill/skills/api-testing/SKILL.md

api-testing

Skill2 starsChanged 4 days agoMITView on GitHub

Plan, generate and run API tests from an OpenAPI spec, GraphQL schema, Postman collection or curl examples. Covers functional (positive, negative, edge, integration), contract, security, load/stress/soak and chaos testing. Use when the user wants to test, audit or load-test an HTTP API.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use analytics-tracking-testing, database-testing and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • petrkindlmannSkill

    analytics-tracking-testing

    Validate that analytics and marketing tracking fire CORRECTLY: GA4/GTM dataLayer events, Meta/TikTok/LinkedIn pixels, and ad-tech tags. Covers building a tracking plan as the contract, intercepting collect-endpoint beacons and dataLayer.push in Playwright, asserting event name + params + values + timing + de-duplication, Consent Mode v2 gating, CI regression gating, and news-media events (article-view, scroll-depth, paywall). Use when: "test analytics tracking," "GA4 event test," "verify the pixel fires," "dataLayer test," "tracking plan," "Meta Pixel dedup," "scroll-depth tracking test," "gate tracking in CI." Not for: whether tracking is ALLOWED to fire under consent law (GDPR/CMP) — that is compliance-testing; this skill checks the data is CORRECT. SEO meta tags / structured data — out of scope. Related: compliance-testing, playwright-automation, api-testing, qa-project-context.

    Also in 3 projects that use this

  • petrkindlmannSkill

    database-testing

    Validate database integrity, test migrations forward and backward, verify schema constraints, manage seed data, detect migration drift, and identify query performance issues. Covers PostgreSQL, MySQL, MongoDB with Prisma, TypeORM, Drizzle, and SQLAlchemy, plus Testcontainers test databases. Use when: "database test," "migration test," "migration rollback," "rollback test," "data integrity," "SQL test," "schema validation," "seed data," "query performance," "Testcontainers." Not for: synthetic data generation/masking at scale — use test-data-management; Docker/IaC test-environment provisioning — use test-environments; SQL injection — use security-testing. Related: test-data-management, test-environments, security-testing, ci-cd-integration.

    Also in 4 projects that use this

  • testified-ossSkill

    exploratory-testing

    Guide exploratory testing sessions including charter creation, session-based testing, heuristics application, and finding documentation. Use when planning exploratory testing, conducting test sessions, or documenting discoveries.

    Also in 5 projects that use this

  • conorluddySkill

    accessibility-testing

    WCAG compliance testing and accessibility quality assurance workflows for iOS apps. Use when validating accessibility labels, testing VoiceOver compatibility, checking contrast ratios, or ensuring WCAG 2.1 compliance. Covers accessibility tree analysis, semantic validation, and automated accessibility testing patterns.

    Also in 4 projects that use this

  • mmondoraSkill

    security-testing

    Automated security testing in CI. SAST, DAST, dependency scanning, authorization testing, secret detection. Use when adding security scans to pipelines, writing tenant isolation tests, or configuring vulnerability scanning.

    Also in 3 projects that use this

  • etewiahSkill

    e2e-testing

    Playwright E2E testing and Lighthouse performance auditing. Use when setting up E2E tests, running Playwright tests, performing Lighthouse audits, or debugging E2E test failures.

    Also in 4 projects that use this

  • +4 more from petrkindlmann

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never ask for, print or log secret values.

    line 23
  2. Very specific:

    Read only the reference files for the chosen test types, then generate runnable pytest: python scripts/gen_pytest.py intake.json -o …

    line 38
  3. Distinctive:

    If k6 is not installed, say so and print the command.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

API Testing

Router only. Follow the steps in order; load a reference file only when its step needs it.

1. Intake

Collect: spec or examples (OpenAPI/Swagger, Postman collection, curl commands, GraphQL SDL or introspection JSON), base URL, auth method, environment (local/staging/prod).

  • Normalize the input: python scripts/intake.py <file> -o intake.json --summary (auto-detects the type; for GraphQL add --url <endpoint>; shape and edge cases in references/intake.md).
  • Surface the parser warnings to the user (missing base URL, no response schemas, etc.) and ask for what is missing.
  • Credentials come from environment variables only (the parser lists the names, e.g. APITEST_BEARERAUTH_TOKEN). Never ask for, print or log secret values.
  • intake.json describes the user's API; keep it out of version control (it is git-ignored by default).

2. Plan

Fill templates/test-plan.md from intake.json: endpoints in scope and the test types that apply (type list: references/test-types.md). Show the plan and get a go-ahead before generating anything.

3. Safety gate

Load, stress, spike, soak, chaos and fuzz require the user to confirm (a) the target is non-production and (b) they own or are authorized to test it. If not confirmed, stop. Do not weaken this. The user exports APITEST_TARGET_ENV (non-production value) and APITEST_AUTHORIZED=yes; never set them yourself (loopback targets pass without them; production is always refused). run_k6.py, the k6 scripts and the fuzz tests enforce this too. A public sandbox you only read from: APITEST_READ_ONLY=yes sends only GET/HEAD/OPTIONS and no active probes (pytest suites skip writes and intrusive tests, k6 skips write methods, chaos_run.py skips payload and dependency-command experiments).

4. Generate

Read only the reference files for the chosen test types, then generate runnable pytest: python scripts/gen_pytest.py intake.json -o api_tests --types all (REST and GraphQL; --types smoke,positive,... to pick). It prints the rerun command, the env var names the suite needs and any endpoints it could not cover. Active security probes are intrusive: the generated conftest.py skips them unless the target is local, or non-production and authorized (APITEST_TARGET_ENV, APITEST_AUTHORIZED=yes); never set those variables yourself, ask the user. Spec drift between versions: python scripts/spec_diff.py old.json new.json. Non-functional (after step 3 only; details in each reference):

  • load/stress/spike/soak: python scripts/gen_k6.py intake.json -o k6_tests --profiles load (GET-only, capped, --quick first), run with python scripts/run_k6.py k6_tests/load.js
  • fuzz: python scripts/gen_pytest.py intake.json -o fuzz_tests --types fuzz (opt-in, REST only, seeded and rate-limited)
  • chaos: plan with python scripts/gen_chaos_plan.py intake.json -o chaos-plan.md --env staging; run experiments with python scripts/chaos_run.py intake.json --dry-run first (proxy faults, payload bursts, your own dependency commands; never guess commands)

5. Run

Execute if the environment allows; otherwise print the exact commands to run. Always print the rerun command. If k6 is not installed, say so and print the command; never claim a load run happened when it did not.

6. Report

Collect JUnit XML (pytest --junitxml=results/pytest.xml) and k6 summaries (results/<profile>-summary.json), then: python scripts/summarize_results.py --junit results/pytest.xml --k6 results/load-summary.json --intake intake.json -o reports/report.html Writes a self-contained HTML report and reports/report.json next to it: summary, per-type breakdown, per-endpoint coverage, findings ranked by severity, a reproducible command per finding (references/reporting.md). -o report.md still writes Markdown (templates/report.md). Report what was run and what was skipped; never state results the files do not contain.

Reference files (load on demand)

  • references/test-types.md — the 18 test types and what each checks
  • references/intake.md — normalized intake JSON, parser behavior and limits
  • references/functional.md — smoke, positive, negative, edge
  • references/data-validation.md — types, formats, enums, lengths, ranges, required fields
  • references/graphql.md — GraphQL intake, functional and security checks
  • references/integration.md — multi-endpoint flows (create, read, update, delete)
  • references/contract.md — schema conformance, breaking changes (spec_diff.py)
  • references/security.md — OWASP API Top 10 checks and the safety gate
  • references/resilience.md — idempotency, pagination, timeouts, rate-limit behaviour
  • references/load.md — k6 setup, caps and the launcher; load profile
  • references/stress.md, references/spike.md, references/soak.md — the other k6 profiles
  • references/reporting.md — building the report, severity rules, what it never prints
  • references/chaos.md — chaos plans and runnable experiments (chaos_run.py)
  • references/fuzzing.md — malformed-input fuzzing

Not covered

UI accessibility and mobile app testing (not API testing), a hosted service, and gRPC (planned for v2).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.