Claude Skill

api-test-supertest

Use this skill when you need to parse multi-format API definitions and generate executable Supertest scripts; triggers include Supertest, Node.js API testing, and Supertest automation.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download naodeng-awesome-qa-skills-skills_en_testing-types_api-test-supertest-9df700b.zip · 27 KB

Install

skills CLI npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/api-test-supertest
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart
Git git clone https://github.com/naodeng/awesome-qa-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole naodeng/awesome-qa-skills collection as a plugin from our marketplace. Git is the plain clone.

README

api-test-supertest (EN)

Skill Overview

Need API outputs that should land in Supertest based automation; The project is Node.js-based or already uses Supertest/Jest.

How to Use

  1. Open SKILL.md in this folder and confirm this skill fits your task.
  2. In your AI tool, call @skill api-test-supertest, then add your real project context and goal.
  3. If you need a specific output format (table, checklist, report), include it directly in your request.

One-Click Install Script

Run from the repository root:

macOS / Linux

bash ./scripts/install-skills-mac.sh --tool codex --lang en --skill api-test-supertest

Windows PowerShell

powershell -ExecutionPolicy Bypass -File .\scripts\install-skills-windows.ps1 -Tool codex -Lang en -Skill api-test-supertest

Skill manifest

api-test-supertest (EN)

Chinese version: See the corresponding Chinese skill.

When to Use

  • Need API outputs that should land in Supertest based automation.
  • The project is Node.js-based or already uses Supertest/Jest.

Generation and execution boundary

Generators produce smoke assertions for known fields only: require nonempty endpoints and explicit expected_statuses; optional expected_json and sourced max_response_ms. Missing data, unresolved parameters/variables, or schema assertions produce incomplete scaffolds and a nonzero exit. Read references/generator-contract.md; configure target and credentials explicitly.

Workflow

  1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
  2. Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
  3. If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
  4. Default to Markdown; switch formats only when the user asks.

Core Constraints

  • Prioritize by risk / business impact — do not treat everything equally.
  • Separate confirmed facts from current assumptions.
  • Do not invent endpoints, fields, environments, or root causes the user did not provide.
  • Use placeholders or env-var semantics for auth/secrets; never hardcode real credentials.
  • Keep output executable: concrete scenarios, clear priority, clear next steps.

Progressive Disclosure

  • Before producing output, read and follow prompts/api-test-supertest.md (minimum coverage, output structure, quality bar).
  • When a ready-made template fits: use matching files under output-templates/.
  • When the user wants examples or alignment with existing assets: read relevant examples/.
  • For deep framework/troubleshoot/schema notes: read only the relevant file(s) under references/, do not load the whole directory.
  • For format conversion or helper checks: prefer existing scripts/ over reinventing.
  • For evaluating/regressing this skill: use evals/ with skill-up.

Pre-delivery Checklist

  • Followed the main prompt's output structure
  • Minimum coverage focus: suite structure, environment setup, auth handling, priority endpoints, positive scenarios, negative and boundary scenarios, assertion focus, data strategy, ... (details in main prompt)
  • Covered the minimum checklist, or explained omissions
  • High-risk items have explicit priority
  • Did not invent details the user did not provide
  • Assumptions and gaps are marked

Common Pitfalls

  • Do not pretend completeness when scope/context is missing.
  • Do not treat every item as equally important.
  • Do not skip assumptions and information gaps.
  • Do not dump generic theory unrelated to the current toolchain.
Files (awesome-qa-skills)
  • agents
    • openai.yaml 482 B
      Loading…
  • evals
    • cases
      • basic-success.yaml 933 B
        Loading…
      • edge-bad-or-neighbor.yaml 721 B
        Loading…
      • edge-incomplete-input.yaml 655 B
        Loading…
      • review-repair-regression.yaml 1.3 KB
        Loading…
    • graders
      • review-repair-regression.py 1.1 KB
        Loading…
    • eval.yaml 607 B
      Loading…
  • examples
    • bruno
      • sample.bru 137 B · in bundle
    • ci
      • github-actions-supertest.yml 655 B
        Loading…
      • Jenkinsfile.supertest 545 B · in bundle
    • sample.curl 212 B · in bundle
    • sample.insomnia.json 502 B
      Loading…
    • sample.openapi.yaml 240 B
      Loading…
    • sample.opencollection.json 243 B
      Loading…
    • sample.postman_collection.json 828 B
      Loading…
    • sample.wsdl 534 B · in bundle
  • output-templates
    • template-markdown.md 83 B
      Loading…
  • prompts
    • api-test-supertest.md 5.3 KB
      Loading…
  • references
    • local
      • api-testing_EN.md 491 B
        Loading…
    • framework-spec.md 1.5 KB
      Loading…
    • generator-contract.md 2.3 KB
      Loading…
    • report-schema.md 800 B
      Loading…
    • setup-and-ci.md 437 B
      Loading…
  • scripts
    • templates
      • supertest
        • tests
          • generated.api.test.js 225 B
            Loading…
          • health.test.js 286 B
            Loading…
        • app.js 535 B
          Loading…
        • jest.config.cjs 89 B · in bundle
        • package.json 254 B
          Loading…
    • api_case_contract.py 7.5 KB
      Loading…
    • generate_supertest_tests.py 2.7 KB
      Loading…
    • parse_api_sources.py 18.4 KB
      Loading…
    • run.sh 694 B
      Loading…
  • README.md 812 B
    # api-test-supertest (EN)
    
    ## Skill Overview
    
    Need API outputs that should land in Supertest based automation; The project is Node.js-based or already uses Supertest/Jest.
    
    ## How to Use
    
    1. Open `SKILL.md` in this folder and confirm this skill fits your task.
    2. In your AI tool, call `@skill api-test-supertest`, then add your real project context and goal.
    3. If you need a specific output format (table, checklist, report), include it directly in your request.
    
    ## One-Click Install Script
    
    Run from the repository root:
    
    ### macOS / Linux
    
    ```bash
    bash ./scripts/install-skills-mac.sh --tool codex --lang en --skill api-test-supertest
    ```
    
    ### Windows PowerShell
    
    ```powershell
    powershell -ExecutionPolicy Bypass -File .\scripts\install-skills-windows.ps1 -Tool codex -Lang en -Skill api-test-supertest
    ```
    
  • SKILL.md 3.3 KB
    ---
    name: api-test-supertest
    description: Use this skill when you need to parse multi-format API definitions and generate executable Supertest scripts; triggers include Supertest, Node.js API testing, and Supertest automation.
    license: PolyForm-Noncommercial-1.0.0
    metadata:
      version: "1.0.0"
      compatibility: ""
      author: "Awesome QA Skills contributors"
      language: "en"
      category: "testing-types"
      source: "https://github.com/naodeng/awesome-qa-skills"
      license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0"
    ---
    
    # api-test-supertest (EN)
    
    **Chinese version:** See the corresponding Chinese skill.
    
    ## When to Use
    
    - Need API outputs that should land in Supertest based automation.
    - The project is Node.js-based or already uses Supertest/Jest.
    
    ## Generation and execution boundary
    
    Generators produce smoke assertions for known fields only: require nonempty endpoints and explicit expected_statuses; optional expected_json and sourced max_response_ms. Missing data, unresolved parameters/variables, or schema assertions produce incomplete scaffolds and a nonzero exit. Read `references/generator-contract.md`; configure target and credentials explicitly.
    
    ## Workflow
    
    1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
    2. Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
    3. If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
    4. Default to Markdown; switch formats only when the user asks.
    
    ## Core Constraints
    
    - Prioritize by risk / business impact — do not treat everything equally.
    - Separate confirmed facts from current assumptions.
    - Do not invent endpoints, fields, environments, or root causes the user did not provide.
    - Use placeholders or env-var semantics for auth/secrets; never hardcode real credentials.
    - Keep output executable: concrete scenarios, clear priority, clear next steps.
    
    ## Progressive Disclosure
    
    - Before producing output, read and follow `prompts/api-test-supertest.md` (minimum coverage, output structure, quality bar).
    - When a ready-made template fits: use matching files under `output-templates/`.
    - When the user wants examples or alignment with existing assets: read relevant `examples/`.
    - For deep framework/troubleshoot/schema notes: read only the relevant file(s) under `references/`, do not load the whole directory.
    - For format conversion or helper checks: prefer existing `scripts/` over reinventing.
    - For evaluating/regressing this skill: use `evals/` with skill-up.
    
    ## Pre-delivery Checklist
    
    - [ ] Followed the main prompt's output structure
    - [ ] Minimum coverage focus: suite structure, environment setup, auth handling, priority endpoints, positive scenarios, negative and boundary scenarios, assertion focus, data strategy, ... (details in main prompt)
    - [ ] Covered the minimum checklist, or explained omissions
    - [ ] High-risk items have explicit priority
    - [ ] Did not invent details the user did not provide
    - [ ] Assumptions and gaps are marked
    
    ## Common Pitfalls
    
    - Do not pretend completeness when scope/context is missing.
    - Do not treat every item as equally important.
    - Do not skip assumptions and information gaps.
    - Do not dump generic theory unrelated to the current toolchain.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.