Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Browse and inspect Postman collections, requests, and environments from the terminal using pmctl. Use when you need to discover API endpoints, look up reques...
Browse and inspect Postman collections, requests, and environments from the terminal using pmctl. Use when you need to discover API endpoints, look up reques...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
pmctl wraps the Postman API to let you browse collections, inspect requests, and resolve environment variables from the terminal. Use it to discover endpoints, construct curl commands, and understand APIs without opening the Postman GUI. Install: pip install pmctl Source: github.com/wbingli/pmctl
# Add a profile with your Postman API key pmctl profile add <name> --api-key "PMAK-..." --default # Set a default workspace (scopes list commands) pmctl profile set-workspace <workspace-id> # Verify pmctl profile whoami Get an API key at https://go.postman.co/settings/me/api-keys
pmctl profile list # List profiles pmctl profile add <name> -k "PMAK-..." -d # Add (--default) pmctl profile switch <name> # Switch default pmctl profile set-workspace <id> # Set default workspace pmctl profile remove <name> # Remove pmctl profile whoami # Current user info
pmctl collections list # List (scoped to default workspace) pmctl collections list --all # All workspaces pmctl collections show <UID> # Tree view of all requests
# List all requests in a collection (flat table: method, name, path, URL) pmctl requests list -c "Collection Name" pmctl requests list -c <collection-uid> # Fuzzy search (characters matched in order, e.g. "getCmp" matches "get Campaign") pmctl requests list -c "My API" --search "getUser" # Show request details (headers, body, query params, path variables) pmctl requests show "request name" -c "Collection Name" -c / --collection accepts a collection name (case-insensitive) or UID. requests show uses case-insensitive substring match โ use short terms. requests list --search uses fuzzy matching (characters in order).
pmctl environments list # List environments pmctl environments show <name-or-id> # Show variables pmctl environments show <name> --full # Full values (no truncation)
pmctl workspaces list # List accessible workspaces pmctl workspaces list --search "keyword" # Filter by name
--json โ Machine-readable JSON output (works as global flag or per-subcommand) --profile <name> / -p โ Use a specific profile instead of default
Postman requests use {{variable}} placeholders. Resolve them via environments: # 1. Get the request (shows URL like {{base-url}}/v1/users/:userId) pmctl requests show "get User" -c "My API" --json # 2. Resolve the variable for a specific environment pmctl environments show "Production" --json | jq -r '.values[] | select(.key == "base-url") | .value' # 3. Combine: replace {{base-url}} with resolved value, :userId with actual ID
# Get full request details as JSON REQ=$(pmctl requests show "create User" -c "My API" --json) # Extract method, URL, headers, body echo "$REQ" | jq '.[0].request | {method, url: .url.raw, headers: .header, body: .body.raw}' # Get environment base URL BASE=$(pmctl environments show "QA" --json | jq -r '.values[] | select(.key == "base-url") | .value')
# Fuzzy search across a collection pmctl requests list -c "My API" --search "user" # Or browse the full tree pmctl collections show <uid>
--json output is pipeable to jq for scripting environments show --json returns unmasked secrets โ useful for scripting Collection names are matched case-insensitively; prefer names over UIDs for readability Multiple profiles let you manage separate Postman accounts (personal, work, etc.)
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.