How do I install the Test API Postman Newman skill?

Run npx skillmds@latest add willyu1007/test-api-postman-newman in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Test API Postman Newman skill do?

Postman + Newman API Automation (workflow) It is listed under Integrations & APIs on SkillMD.

Is Test API Postman Newman safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Test API Postman Newman?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Test API Postman Newman free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Test API Postman Newman?

willyu1007 (@willyu1007) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Test API Postman Newman by willyu1007

Name: Test API Postman Newman
Author: willyu1007

File contents

Postman + Newman API Automation (workflow)

Operating mode (token-efficient)

Treat this skill as a router + governor.
Do not load multiple procedures. Select exactly one procedure below and follow it end-to-end.
Optimize for determinism and actionable failures.

Routing (pick one procedure)

Task	Open this procedure	Optional examples
Bootstrap API automation (collections + Newman)	`reference/procedures/bootstrap.md`	`reference/examples/smoke.collection.json`, `reference/examples/dev.env.json`
Add/extend a request + tests	`reference/procedures/add-request-and-tests.md`	`reference/examples/smoke.collection.json`
Run locally / in CI	`reference/procedures/run.md`	—
Triage failures / improve signal	`reference/procedures/triage-failures.md`	—

Shared non-negotiables (apply to all procedures)

Collection conventions
- Keep collections versioned in-repo (exported JSON).
- Use folders to reflect product areas and suites (smoke/regression).
Deterministic assertions
- Assert on stable contracts: status code, schema, key fields.
- Avoid asserting on volatile fields (timestamps, random IDs) unless normalized.
Environment separation
- Use environment files for non-secret config.
- Inject secrets via CI secrets / env vars at runtime.
Artifact contract (for CI + triage)
- Standardize under: artifacts/newman/
- Include at least:
  - JUnit XML (machine-readable)
  - JSON/HTML summary (human-readable) when feasible
No secrets in repo
- Never commit tokens, passwords, or private keys in collection/env JSON.

Minimal inputs you should capture before changing code

API base URL(s) per environment
Auth model (API key / OAuth / session cookie) and test credentials strategy
Test data strategy (seeded fixtures, dedicated test tenant)
Which endpoints are in scope (smoke vs regression)

Verification

If you changed skills:
- Prefer host-repo tooling if present:
  - node .ai/scripts/lint-skills.mjs --strict
- Always run the local validator:
  - node .ai/skills/testing/test-api-postman-newman/scripts/validate-skill.mjs
If you changed collections/tests:
- npx newman --version
- Run the target collection:
  - npx newman run <collection.json> -e <env.json>

Boundaries

Do not edit .codex/skills/ or .claude/skills/ directly (generated).
Do not introduce a second API test DSL unless Postman/Newman is insufficient for the specific need.
Do not run destructive mutations against shared environments without explicit gating.

---name: test-api-postman-newmandescription: Postman + Newman API Automation (workflow)---# Postman + Newman API Automation (workflow)## Operating mode (token-efficient)- Treat this skill as a **router + governor**.- Do **not** load multiple procedures. Select exactly **one** procedure below and follow it end-to-end.- Optimize for determinism and actionable failures.## Routing (pick one procedure)| Task | Open this procedure | Optional examples ||---|---|---|| Bootstrap API automation (collections + Newman) | `reference/procedures/bootstrap.md` | `reference/examples/smoke.collection.json`, `reference/examples/dev.env.json` || Add/extend a request + tests | `reference/procedures/add-request-and-tests.md` | `reference/examples/smoke.collection.json` || Run locally / in CI | `reference/procedures/run.md` | — || Triage failures / improve signal | `reference/procedures/triage-failures.md` | — |## Shared non-negotiables (apply to all procedures)1) **Collection conventions** - Keep collections versioned in-repo (exported JSON). - Use folders to reflect product areas and suites (smoke/regression).2) **Deterministic assertions** - Assert on stable contracts: status code, schema, key fields. - Avoid asserting on volatile fields (timestamps, random IDs) unless normalized.3) **Environment separation** - Use environment files for non-secret config. - Inject secrets via CI secrets / env vars at runtime.4) **Artifact contract (for CI + triage)** - Standardize under: `artifacts/newman/` - Include at least: - JUnit XML (machine-readable) - JSON/HTML summary (human-readable) when feasible5) **No secrets in repo** - Never commit tokens, passwords, or private keys in collection/env JSON.## Minimal inputs you should capture before changing code- API base URL(s) per environment- Auth model (API key / OAuth / session cookie) and test credentials strategy- Test data strategy (seeded fixtures, dedicated test tenant)- Which endpoints are in scope (smoke vs regression)## Verification- If you changed **skills**: - Prefer host-repo tooling if present: - `node .ai/scripts/lint-skills.mjs --strict` - Always run the local validator: - `node .ai/skills/testing/test-api-postman-newman/scripts/validate-skill.mjs`- If you changed **collections/tests**: - `npx newman --version` - Run the target collection: - `npx newman run <collection.json> -e <env.json>`## Boundaries- Do not edit `.codex/skills/` or `.claude/skills/` directly (generated).- Do not introduce a second API test DSL unless Postman/Newman is insufficient for the specific need.- Do not run destructive mutations against shared environments without explicit gating.

Frequently asked questions

Test API Postman Newman