New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

API Testing Quickstart

by FerroxLabs in FerroxLabs/wayland

Rapid-start guide for testing APIs using Postman and similar tools, covering HTTP request types, authentication methods, collection organization, environment variables, and common debugging…

Apache-2.0Auto-check passedTesting & QA

Install API Testing Quickstart

skills CLI
$ npx skills add FerroxLabs/wayland --skill api-testing-quickstart -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland api-testing-quickstart --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/testing-quality/api-testing-quickstart .claude/skills/api-testing-quickstart && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
api-testing-quickstart
GitHub stars
608
Token cost
~3.3k tokens
SKILL.md length
1,235 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Rapid-start guide for testing APIs using Postman and similar tools, covering HTTP request types, authentication methods, collection organization, environment variables, and common debugging…

  • Works in 6 steps: Open Postman → Click the "+" tab to create a new request → Set the method to GET → …
  • The user asks about api testing quickstart
  • SKILL.md covers When to Use, Quick Diagnosis, Getting Started in 2 Minutes and HTTP Methods, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

API Testing Quickstart is an agent skill from FerroxLabs/wayland. Rapid-start guide for testing APIs using Postman and similar tools, covering HTTP request types, authentication methods, collection organization, environment variables, and common debugging techniques. Use when the user asks about api testing quickstart, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of api testing quickstart or requires a different specialized skill.

Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering API testing. It works with Postman. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about api testing quickstart
  • Related techniques
  • Needs guidance in this domain
  • The request is outside the scope of api testing quickstart

Example prompts

  • “/api-testing-quickstart”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Open Postman
  2. Click the "+" tab to create a new request
  3. Set the method to GET
  4. Enter this URL: `[external resource]
  5. Click Send
  6. You should see a JSON response with a post object

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json, javascript, bash and template).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

API Testing Quickstart loads about 3.3k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 1,235 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~116
When it runs · the whole SKILL.md, loaded when a task matches
~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 1,235 words, ~3,281 tokens.

Download SKILL.mdSave it as .claude/skills/api-testing-quickstart/SKILL.md (or your agent's skills folder).
name
api-testing-quickstart
description
Rapid-start guide for testing APIs using Postman and similar tools, covering HTTP request types, authentication methods, collection organization, environment variables, and common debugging techniques. Use when the user asks about api testing quickstart, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of api testing quickstart or requires a different specialized skill.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
quickstart testing guide javascript api-design cloud email cleaning
metadata.category
testing-quality
metadata.subcategory
test-methodology
metadata.disclaimer
none
metadata.difficulty
beginner

API Testing Quickstart

You are a pragmatic API testing guide. When the user needs to test an API quickly - whether debugging an integration, exploring a new service, or verifying their own endpoints - you get them productive in minutes, not hours. You focus on practical patterns, not theory.

When to Use

Use this skill when:

  • User asks about api testing quickstart techniques or best practices
  • User needs guidance on api testing quickstart concepts
  • User wants to implement or improve their approach to api testing quickstart

Do NOT use when:

  • The request falls outside the scope of api testing quickstart
  • User needs a different specialized skill for their specific situation
  • The topic requires professional consultation beyond general guidance

Quick Diagnosis

Ask the user: What do you need to do? Then jump to the relevant section.

Getting Started in 2 Minutes

Pick Your Tool
ToolCostBest For
PostmanFree (basic)Most popular, great UI, team features
InsomniaFree (basic)Clean interface, good for REST and GraphQL
HTTPie (CLI)FreeTerminal lovers, scripting
HTTP client requestFree (pre-installed)Already on every system, scripting
Thunder ClientFreeVS Code extension, stays in your editor
BrunoFree (open source)Git-friendly, local-first, no cloud account needed

Start with Postman unless you have a reason not to. Download at postman.com.

Your First Request
  1. Open Postman
  2. Click the "+" tab to create a new request
  3. Set the method to GET
  4. Enter this URL: `[external resource]
  5. Click Send
  6. You should see a JSON response with a post object

You just made your first API call.

HTTP Methods

MethodPurposeExample
GETRetrieve dataGet a user profile
POSTCreate new dataCreate a new user
PUTReplace existing data completelyUpdate an entire user record
PATCHUpdate part of existing dataChange just the user's email
DELETERemove dataDelete a user
HEADGet headers only (no body)Check if a resource exists
OPTIONSCheck what methods are allowedCORS preflight requests
When to Use What
Need to read data?          → GET
Need to create something?   → POST
Need to fully replace?      → PUT
Need to partially update?   → PATCH
Need to remove something?   → DELETE

Building Requests

Anatomy of an API Request
METHOD  URL
Headers:
  Content-Type: application/json
  Authorization: Bearer <token>

Body (for POST/PUT/PATCH):
  {
    "name": "John",
    "email": "john@example.com"
  }

Query Parameters (appended to URL):
  ?page=1&limit=10
GET Request with Query Parameters
GET [api-endpoint]/users?page=2&limit=25&sort=name

In Postman: Use the Params tab instead of typing in the URL.
Key: page     Value: 2
Key: limit    Value: 25
Key: sort     Value: name
POST Request with JSON Body
POST [api-endpoint]/users

Headers:
  Content-Type: application/json

Body (raw, JSON):
{
  "name": "Jane Smith",
  "email": "jane@example.com",
  "role": "admin"
}

In Postman: Select Body tab > raw > JSON from dropdown > paste your JSON.

PUT vs PATCH

PUT replaces the entire resource:

json
PUT /users/123
{
  "name": "Jane Smith",
  "email": "jane@newdomain.com",
  "role": "admin",
  "active": true
}

PATCH updates only specified fields:

json
PATCH /users/123
{
  "email": "jane@newdomain.com"
}

Authentication

Common Auth Methods
MethodHow It WorksWhere to Set It
API KeyKey sent as header or query paramHeader: X-API-Key: your-key
Bearer TokenJWT or OAuth token in headerHeader: Authorization: Bearer <token>
Basic AuthUsername:password base64 encodedPostman Auth tab > Basic Auth
OAuth 2.0Token exchange flowPostman Auth tab > OAuth 2.0 (handles the flow)
No AuthPublic APINothing needed
Setting Up Auth in Postman

API Key:

  1. Go to the Headers tab
  2. Add: Key = X-API-Key (or whatever the API requires), Value = your key
  3. Or use the Auth tab > API Key and specify the header name

Bearer Token:

  1. Go to the Auth tab
  2. Select "Bearer Token"
  3. Paste your token

Basic Auth:

  1. Go to the Auth tab
  2. Select "Basic Auth"
  3. Enter username and password
  4. Postman handles the encoding

OAuth 2.0:

  1. Auth tab > OAuth 2.0
  2. Enter the authorization URL, token URL, client ID, client secret
  3. Click "Get New Access Token"
  4. Postman handles the redirect flow

Organizing Your Work

Collections

Collections group related requests together. Create one per API or project.

Structure example:

My API Collection/
  ├── Auth/
  │   ├── Login
  │   └── Refresh Token
  ├── Users/
  │   ├── Get All Users
  │   ├── Get User by ID
  │   ├── Create User
  │   ├── Update User
  │   └── Delete User
  └── Products/
      ├── List Products
      ├── Search Products
      └── Get Product Details
Environment Variables

Environment variables let you switch between dev, staging, and production without changing every request.

Setup:

  1. Click the gear icon (Environments) in Postman
  2. Create environments: "Development," "Staging," "Production"
  3. Add variables:
VariableDevelopmentStagingProduction
base_url[local-server]:3000[external resource][external resource]
api_keydev-key-123staging-key-456prod-key-789

Usage in requests: Replace hardcoded values with {{variable_name}}:

  • URL: {{base_url}}/users
  • Header: X-API-Key: {{api_key}}

Now switching environments changes all your requests at once.

Saving Responses

When you find a good response, save it as an example:

  1. Send the request
  2. Click "Save Response" > "Save as Example"
  3. Name it descriptively ("200 - Success" or "404 - Not Found")
  4. Examples serve as documentation for your team

Debugging Common Issues

Status Codes Quick Reference
CodeMeaningWhat to Check
200SuccessAll good
201CreatedResource created successfully
204No ContentSuccess, no response body (common for DELETE)
400Bad RequestCheck your request body format and required fields
401UnauthorizedCheck your auth token/API key
403ForbiddenYou're authenticated but don't have permission
404Not FoundCheck your URL and resource ID
405Method Not AllowedWrong HTTP method for this endpoint
409ConflictResource already exists (duplicate)
422Unprocessable EntityValidation error - check required fields and data types
429Too Many RequestsRate limited - slow down
500Internal Server ErrorServer-side problem - not your fault
502Bad GatewayServer or proxy issue
503Service UnavailableServer is overloaded or down
Show full SKILL.md (436 more words)Show less
Common Mistakes and Fixes
ProblemLikely CauseFix
401 on every requestMissing or expired auth tokenRefresh your token; check Auth tab
400 Bad RequestMalformed JSON or missing required fieldValidate JSON at jsonlint.com; check API docs for required fields
CORS error (in browser)Browser security policyUse Postman (bypasses CORS); fix CORS on your server for browser apps
Empty response body204 status or wrong Content-TypeCheck status code; some endpoints return no body
Request hangs/times outWrong URL, server down, firewallVerify URL; check if server is running; try HTTP client request from terminal
Unexpected data formatAPI returns XML but you expect JSONAdd header: Accept: application/json
SSL certificate errorSelf-signed cert in devPostman Settings > disable SSL verification (dev only, never in prod)
Reading Error Responses

Most APIs return helpful error messages. Read them:

json
{
  "error": "validation_error",
  "message": "Email field is required",
  "details": [
    {
      "field": "email",
      "rule": "required",
      "message": "The email field is required."
    }
  ]
}

This tells you exactly what to fix: add the email field to your request body.

Testing Workflows

Chaining Requests with Variables

Many APIs require multi-step workflows. In Postman, use the Tests tab to extract values from responses and save them as variables.

Example: Login then use the token

In the Login request's Tests tab:

javascript
var jsonData = pm.response.json();
pm.environment.set("auth_token", jsonData.token);

In subsequent requests, use {{auth_token}} in the Authorization header.

Pre-Request Scripts

Run code before a request sends:

javascript
// Generate a timestamp
pm.environment.set("timestamp", new Date().toISOString());

// Generate a random email for testing
pm.environment.set("random_email", "test+" + Date.now() + "@example.com");
Basic Test Assertions

In the Tests tab, verify responses:

javascript
// Check status code
pm.test("Status code is 200", function () {
    pm.response.to.have.status(200);
});

// Check response contains expected field
pm.test("Response has user name", function () {
    var jsonData = pm.response.json();
    pm.expect(jsonData.name).to.not.be.undefined;
});

// Check response time
pm.test("Response time is acceptable", function () {
    pm.expect(pm.response.responseTime).to.be.below(500);
});

HTTP client request Quick Reference

When you need to test from the terminal:

shell
# GET
HTTP client request [api-endpoint]/users

# GET with headers
HTTP client request -H "Authorization: Bearer TOKEN" [api-endpoint]/users

# POST with JSON
HTTP client request -X POST [api-endpoint]/users \
  -H "Content-Type: application/json" \
  -d '{"name":"Jane","email":"jane@example.com"}'

# PUT
HTTP client request -X PUT [api-endpoint]/users/123 \
  -H "Content-Type: application/json" \
  -d '{"name":"Jane Updated","email":"jane@new.com"}'

# DELETE
HTTP client request -X DELETE [api-endpoint]/users/123 \
  -H "Authorization: Bearer TOKEN"

# Verbose (see headers and connection details)
HTTP client request -v [api-endpoint]/users

# Save response to file
HTTP client request -o response.json [api-endpoint]/users

# Follow redirects
HTTP client request -L [api-endpoint]/old-endpoint

Postman to HTTP command: Right-click any request in Postman > Copy as HTTP command. Instant terminal command.

Process

  1. Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
  2. Analyze context. Review the information provided and identify key factors relevant to api testing quickstart
  3. Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
  4. Present structured output. Deliver findings in the output format below with clear next steps
  5. Address follow-ups. Answer additional questions and refine recommendations based on feedback

Output Format

template
## Api Testing Quickstart Analysis

### Assessment
[Key findings and observations]

### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]

### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]

Edge Cases

  • Incomplete information: Ask clarifying questions before proceeding with recommendations
  • Conflicting requirements: Prioritize the most critical constraint and note trade-offs
  • Out of scope requests: Redirect to appropriate specialized skill or professional resource
  • Beginner vs advanced: Adjust depth and terminology based on user's experience level

Example

Input: "Help me with api testing quickstart for my current situation"

Output:

Based on your situation, here is a structured approach to api testing quickstart:

  1. Assessment: Evaluate your current state and identify key areas for improvement
  2. Strategy: Develop a targeted plan based on best practices
  3. Implementation: Execute the plan with specific, measurable steps
  4. Review: Monitor progress and adjust as needed

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/testing-quality/api-testing-quickstart of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

API Testing Quickstart next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

API Testing Quickstart compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
API Testing Quickstart this skillFerroxLabs/wayland608—~3.3kAutomated safety check: PassApache-2.0
Swing Intellij Dialog Stylelakernote/easy-postman721—~1.8kAutomated safety check: PassApache-2.0
Fontsutil Font Usagelakernote/easy-postman721—~708Automated safety check: PassApache-2.0
Swing UI Test Headless Guardlakernote/easy-postman721—~275Automated safety check: PassApache-2.0
API Testingpetrkindlmann/qa-skills163—~2.7kAutomated safety check: PassMIT
Postman Newman Automationsickn33/agentic-awesome-skills47k1 repos~2.1kAutomated safety check: PassMIT

Similar skills

  • Swing Intellij Dialog Style

    lakernote/easy-postman

    A skill your agent uses when modifying EasyPostman Swing dialogs, popups, wizards, or modal flows to better match IntelliJ IDEA or FlatLaf settings-style visual hierarchy, especially when read-only…

    721 GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed

  • Fontsutil Font Usage

    lakernote/easy-postman

    A skill your agent uses when modifying EasyPostman Swing UI fonts, especially when dialogs, labels, tables, tabs, or renderers look too large or too small, or when a change needs to stay consistent…

    721 GitHub stars~708 tokensUpdated today
    Testing & QAAuto-check passed

  • Swing UI Test Headless Guard

    lakernote/easy-postman

    A skill your agent uses when adding or updating EasyPostman Swing/TestNG UI tests that may run in headless CI or no-display Linux environments.

    721 GitHub stars~275 tokensUpdated today
    Testing & QAAuto-check passed

  • API Testing

    petrkindlmann/qa-skills

    Test REST and GraphQL APIs with Playwright APIRequestContext, Supertest, or standalone HTTP clients.

    163 GitHub stars~2.7k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed

  • Postman Newman Automation

    sickn33/agentic-awesome-skills

    Generate Newman CLI commands, configuration files, Jenkins pipeline scripts, and shell automation for running Postman collections in CI/CD or local environments.

    47k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check passed

  • API Testing

    cosmicstack-labs/mercury-agent-skills

    REST and GraphQL testing, Postman/Insomnia patterns, contract testing, schema validation, and monitoring

    476 GitHub stars~449 tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo

  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes

  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed

  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed

  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed

  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about API Testing Quickstart

What does API Testing Quickstart do?

Rapid-start guide for testing APIs using Postman and similar tools, covering HTTP request types, authentication methods, collection organization, environment variables, and common debugging…. API Testing Quickstart is an agent skill from FerroxLabs/wayland. Rapid-start guide for testing APIs using Postman and similar tools, covering HTTP request types, authentication methods, collection organization, environment variables, and common debugging techniques.

When should I use API Testing Quickstart?

API Testing Quickstart fits situations like: the user asks about api testing quickstart; related techniques; needs guidance in this domain; the request is outside the scope of api testing quickstart.

How do I install API Testing Quickstart in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill api-testing-quickstart -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/testing-quality/api-testing-quickstart in FerroxLabs/wayland) into .claude/skills/api-testing-quickstart in your project. Claude Code loads it when a task matches its description.

How do I install API Testing Quickstart in Codex?

Run `npx skills add FerroxLabs/wayland --skill api-testing-quickstart -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/testing-quality/api-testing-quickstart in FerroxLabs/wayland) into .agents/skills/api-testing-quickstart in your project. Codex loads it when a task matches its description.

Can I use API Testing Quickstart in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill api-testing-quickstart -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-testing-quickstart, .gemini/skills/api-testing-quickstart, .github/skills/api-testing-quickstart and .opencode/skills/api-testing-quickstart in your project.

What does API Testing Quickstart need to run?

SKILL.md names no scripts, command-line tools or credentials: API Testing Quickstart is instructions for the agent only.

Does API Testing Quickstart access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is API Testing Quickstart safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does API Testing Quickstart use?

API Testing Quickstart is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does API Testing Quickstart use?

About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to API Testing Quickstart?

Skills that share tags, products or a category with API Testing Quickstart: Swing Intellij Dialog Style (lakernote/easy-postman, 721 stars), Fontsutil Font Usage (lakernote/easy-postman, 721 stars), Swing UI Test Headless Guard (lakernote/easy-postman, 721 stars) and API Testing (petrkindlmann/qa-skills, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains API Testing Quickstart?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.