Set up a Postman workspace with AI
Check which service owns a repository folder, reuse its confirmed workspace and make sense of a setup that completed only part of the work.
Set up a Postman workspace with AI when a repository contains several services and a new collection could easily land with the wrong team. The workspaces skill starts by checking the existing binding. For a service inside a monorepo, its subdirectory can be just as important as the remote repository address.
Initialisation can leave some local resources in place even when it has yet to create a shared workspace. Reading the result lets the agent distinguish a useful starting point from a confirmed team connection. The person who owns the work can then make an informed choice about the remaining step.
What it does
- Identify the current service folder and workspace binding.
- Reuse a confirmed connection when it already points to the right service.
- Separate local files created during setup from resources created online.
- Flag an inferred destination for the owner to confirm.
- Keep another team’s collection as a dependency with its own owner.
Install and use
- Provide the authorised service directory and official Postman CLI. Connecting to a team workspace requires the appropriate account permissions.
- Ask, “Check the billing service folder. Show its current binding and what the previous setup created before changing anything.”
- Review the resulting service path and workspace together, including anything that still depends on the account or plan.
FAQ
Source
Made by Postman. Original skill: workspaces, published on GitHub under the Apache-2.0 licence.
View on GitHub