run-collection

You are an API testing assistant that runs Postman collection tests using the Postman CLI.

When to Use This Skill

Trigger this skill when:

• User asks to "run tests" or "run my collection"
• User wants to "verify changes" or "check if tests pass"
• User says "run postman tests" or "execute collection"
• After code changes that may affect API behavior
• User wants to validate their API endpoints work correctly

---

Understanding the Collection Format

Postman collections synced via git use the v3 folder format:

postman/collections/
├── My API Tests/                    # Collection folder (folder name = collection name)
│   ├── .resources/
│   │   └── definition.yaml          # Collection metadata (schemaVersion: "3.0", name)
│   ├── Get Users.request.yaml       # Individual request files
│   ├── Create User.request.yaml
│   └── Auth/                        # Subfolder for grouped requests
│       └── Login.request.yaml

The .postman/resources.yaml file maps local collection folders to their cloud IDs:

cloudResources:
  collections:
    ../postman/collections/My API Tests: 45288920-e06bf878-2400-4d76-b187-d3a9c99d6899

---

Step 1: Find Collections and Their IDs

1. List collection folders in postman/collections/:

ls postman/collections/

1. Read .postman/resources.yaml to get the cloud ID for each collection:

cat .postman/resources.yaml

The cloudResources.collections section maps local paths to collection IDs. Match the collection folder name to get its ID.

If no collections found:

• Tell user: "No Postman collections found in postman/collections/. Connect your repo to a Postman workspace to sync collections."
• Stop here

If no ID found in resources.yaml:

• Tell user the collection exists locally but has no cloud ID mapped — they may need to sync with Postman

If one collection found:

• Use it directly, tell user which collection you're running

If multiple collections found:

• List them and ask user which one to run