Claude Skill

api-test-postman

Use this skill when you need to design Postman collections, environments, scripts, and Newman-ready API regression plans; triggers include Postman API testing, API testing, and api-test-postman.

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

Install

skills CLI npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/api-test-postman
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-postman (EN)

Skill Overview

Design Postman collections, environments, scripts, and Newman-ready API regression plans.

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-postman, then add your real project context and goal.
  3. If you need a specific output shape, 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-postman

Windows PowerShell

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

Skill manifest

Postman API Testing (EN)

Chinese version: See the corresponding Chinese skill.

When to Use

  • Need outputs that should land in a Postman API testing workflow.
  • The project already uses Postman or wants Postman-ready planning.

Output Format Options

Markdown by default unless the request explicitly asks for another format.

How to Use

  1. Open prompts/api-test-postman.md and use it as the main prompt.
  2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
  3. If the input is incomplete, return a usable first version and mark missing information and assumptions.

Reference Files

  • prompts/api-test-postman.md: main prompt for this skill.
  • references/framework-spec.md: tool-specific structure and coverage notes.
  • references/setup-and-ci.md: setup, execution, and CI notes.
  • examples/sample-context.md: sample request context.
  • scripts/run-tests.sh: lightweight local execution entry point.

Common Pitfalls

  • Do not use it with vague scope and no context.
  • Do not treat every area as equally important.
  • Do not skip assumptions and missing information.

Best Practices

  • Start from the prompt file, then add only the context that matters.
  • Keep the output risk-driven and executable.
  • If the request is incomplete, return a usable first version and mark gaps.
Files (awesome-qa-skills)
  • agents
    • openai.yaml 410 B
      Loading…
  • evals
    • cases
      • basic-success.yaml 836 B
        Loading…
      • edge-incomplete-input.yaml 740 B
        Loading…
      • edge-scope-boundary.yaml 1 KB
        Loading…
      • review-collection-auth-cleanup.yaml 3.2 KB
        Loading…
      • review-unknown-expectation.yaml 996 B
        Loading…
    • eval.yaml 712 B
      Loading…
  • examples
    • sample-context.md 470 B
      Loading…
  • output-templates
    • template-markdown.md 156 B
      Loading…
  • prompts
    • api-test-postman.md 1.6 KB
      Loading…
  • references
    • framework-spec.md 688 B
      Loading…
    • setup-and-ci.md 798 B
      Loading…
  • scripts
    • run-tests.sh 454 B
      Loading…
  • README.md 740 B
    # api-test-postman (EN)
    
    ## Skill Overview
    
    Design Postman collections, environments, scripts, and Newman-ready API regression plans.
    
    ## 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-postman`, then add your real project context and goal.
    3. If you need a specific output shape, 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-postman
    ```
    
    ### Windows PowerShell
    
    ```powershell
    powershell -ExecutionPolicy Bypass -File .\scripts\install-skills-windows.ps1 -Tool codex -Lang en -Skill api-test-postman
    ```
    
  • SKILL.md 1.9 KB
    ---
    name: api-test-postman
    description: Use this skill when you need to design Postman collections, environments, scripts, and Newman-ready API regression plans; triggers include Postman API testing, API testing, and api-test-postman.
    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"
    ---
    
    # Postman API Testing (EN)
    
    **Chinese version:** See the corresponding Chinese skill.
    
    ## When to Use
    
    - Need outputs that should land in a Postman API testing workflow.
    - The project already uses Postman or wants Postman-ready planning.
    
    ## Output Format Options
    
    Markdown by default unless the request explicitly asks for another format.
    
    ## How to Use
    
    1. Open `prompts/api-test-postman.md` and use it as the main prompt.
    2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
    3. If the input is incomplete, return a usable first version and mark missing information and assumptions.
    
    ## Reference Files
    
    - `prompts/api-test-postman.md`: main prompt for this skill.
    - `references/framework-spec.md`: tool-specific structure and coverage notes.
    - `references/setup-and-ci.md`: setup, execution, and CI notes.
    - `examples/sample-context.md`: sample request context.
    - `scripts/run-tests.sh`: lightweight local execution entry point.
    
    ## Common Pitfalls
    
    - Do not use it with vague scope and no context.
    - Do not treat every area as equally important.
    - Do not skip assumptions and missing information.
    
    ## Best Practices
    
    - Start from the prompt file, then add only the context that matters.
    - Keep the output risk-driven and executable.
    - If the request is incomplete, return a usable first version and mark gaps.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.