agentleFS
Sign inStart free
jgamaraalvjgamaraalv/delivery-loop/.claude/skills/postman/SKILL.md

postman

Skill0 starsChanged 4 months agoMITView on GitHub

Full API lifecycle via the Postman MCP Server — sync OpenAPI specs to collections, generate typed clients, run API tests, create mocks, publish docs, OWASP audits. Use for Postman, collections, specs, mocks, or SDKs.

  • Reads credentials

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Setup check: Call getAuthenticatedUser via MCP.

    line 12
  2. Very specific:

    If MCP tools are not available or getAuthenticatedUser fails:

    line 16
  3. Very specific:

    Verify: call getAuthenticatedUser, then list workspaces and collection counts so the user sees they're connected.

    line 20
  4. Very specific:

    Only use mcp__postman__* tools directly for single targeted updates or when the user explicitly asks.

    line 40

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Postman

Full API lifecycle management through the Postman MCP Server (111+ tools for workspaces, collections, specs, environments, mocks, and monitors). Sync specs, generate code, run tests, create mocks, publish docs, and audit security.

Prerequisites

Setup check: Call getAuthenticatedUser via MCP. If it succeeds, you're connected. If it fails, walk through Setup below.

Setup

If MCP tools are not available or getAuthenticatedUser fails:

  1. Get a Postman API key at https://postman.postman.co/settings/me/api-keys — "Generate API Key", name it "Claude Code", copy the key (starts with PMAK-).
  2. Set the environment variable — export POSTMAN_API_KEY=PMAK-your-key-here (add to ~/.zshrc or ~/.bashrc to persist).
  3. Verify: call getAuthenticatedUser, then list workspaces and collection counts so the user sees they're connected.

Routing

Match the user's intent to a workflow, then read that workflow's reference file and follow it. Each file is loaded on demand — read one only when the task needs that depth (progressive disclosure).

User intentWorkflow reference
Import a spec, push spec to Postman, create collection from spec, sync changesreferences/sync-collections.md
Generate client code, SDK, wrapper, typed client, consume an APIreferences/generate-client-code.md
Find API, search endpoints, what's available, discover APIsreferences/discover-apis.md
Run tests, check if tests pass, validate API, test collectionreferences/run-collection-tests.md
Create mock server, fake API, mock for frontend, mock URLreferences/create-mock-servers.md
Generate docs, improve documentation, publish docs, API docsreferences/api-documentation.md
Security audit, vulnerabilities, OWASP, security checkreferences/security-audit.md

Routing rules:

  1. Specific workflows take priority. If intent clearly maps to one, use it.
  2. Ambiguous requests: ask the user what they need.
  3. Multi-step requests chain workflows. "Import my spec and run tests" = Sync then Test.
  4. Only use mcp__postman__* tools directly for single targeted updates or when the user explicitly asks.

References

  • references/mcp-limitations.md — known MCP behaviors and workarounds (300KB+ payloads from getWorkspaces/getCollection model=full, async HTTP 202 polling, plan-gated tag tools, aggregate-only runCollection, public-only searchPostmanElements) · read before composing any tool calls a workflow doesn't already cover.
  • references/mcp-tools.md — the complete tool catalog by category · read when picking the right tool outside a workflow.

Error Handling

These patterns apply across all workflows:

ErrorResponse
MCP tools not available"The Postman MCP Server isn't configured. Set your POSTMAN_API_KEY environment variable and restart your editor."
401 Unauthorized"Your Postman API key was rejected. Generate a new one at https://postman.postman.co/settings/me/api-keys"
Network timeoutRetry once. Check https://status.postman.com for outages.
Async operation stuckIf polling shows no progress after 30 seconds, inform user and suggest checking Postman app directly.
Collection not found"No collection matching that name. Try discovering APIs across your workspace."
Empty collection"This collection has no requests. Add endpoints in Postman or sync from a local spec."
Invalid specReport specific parse errors with line numbers. Offer to fix common YAML/JSON syntax issues.
Plan limitations"Some features may require a paid Postman plan. Core operations work on all plans."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free