Collection and Environment Hygiene Audit (No Secrets)
Check shared collections for secrets, stale requests and unclear tests.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit a Postman workspace. A description of collections, environments, variables (names and whether they contain secrets), tests, and sharing settings: [WORKSPACE_DESCRIPTION]. The team's conventions: [CONVENTIONS]. Check for secrets stored in variable values or shared environments, tokens in example responses, requests with hardcoded hosts, outdated requests, tests with no assertions, collections that duplicate each other, missing descriptions, and sharing with wider access than needed. Make a table with Item, Finding, Risk, and Fix, and count findings with the arithmetic. Recommend moving secrets to a secure store or local-only variables [VERIFY], adding a README to each collection, versioning, and a quarterly review. Provide a checklist for rotating any exposed credentials. Do not paste any tokens or keys here; describe them. Mark workspace features [VERIFY]. Add a worked finding list: 12 collections, 3 with tokens in example responses, 2 environments with shared values that look like secrets, 5 requests without tests, 4 duplicates; the plan is to rotate the tokens first, then add a README and a naming convention to each collection. Include a template message to collection owners.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.