Skip to content
Skills Library
Programming · Tool integration

bootstrap

/bootstrap

Use when resolving Postman CLI setup, authentication, or a repository workspace binding; initializing local API files; handling a CLI error that says an operation isn't allowed because of insufficient entitlements; or importing, pulling, pushing, syncing, or sharing workspace resources. Reuses existing context and chooses sync direction without duplicating a workspace or rebinding a dependency. Use for requests such as "set up Postman for this repo".

Licence
Apache-2.0
Last repository change
26.10.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when resolving Postman CLI setup, authentication, or a repository workspace binding; initializing local API files; handling a CLI error that says an operation isn't allowed because of insufficient entitlements; or importing, pulling, pushing, syncing, or sharing workspace resources. Reuses existing context and chooses sync direction without duplicating a workspace or rebinding a dependency. Use for requests such as "set up Postman for this repo".

Triggers from the description

set up Postman for this repo
Original author description

Use when resolving Postman CLI setup, authentication, or a repository workspace binding; initializing local API files; handling a CLI error that says an operation isn't allowed because of insufficient entitlements; or importing, pulling, pushing, syncing, or sharing workspace resources. Reuses existing context and chooses sync direction without duplicating a workspace or rebinding a dependency. Use for requests such as "set up Postman for this repo".

How it works

  1. Start with postman init
  2. Resolve only the missing setup
  3. Owning workspace versus dependency
  4. Interpret initialization without losing partial success
  5. Subscription or usage limit
  6. Verification
  7. Reporting CLI and skill gaps
Original SKILL.md headings · 137 lines, 1,148 words
SKILL.md preview
---
name: bootstrap
description: Use when resolving Postman CLI setup, authentication, or a repository workspace binding; initializing local API files; handling a CLI error that says an operation isn't allowed because of insufficient entitlements; or importing, pulling, pushing, syncing, or sharing workspace resources. Reuses existing context and chooses sync direction without duplicating a workspace or rebinding a dependency. Use for requests such as "set up Postman for this repo".
---

# Bootstrap Postman for This Repo

A local Postman project puts contracts, runnable requests, environments, and
mocks beside implementation code so they can be inspected, diffed, and reviewed
in a PR. A workspace binding connects that work to maintained shared context.
Setup is useful when it resolves a missing capability or binding; a local API
check does not need a new workspace merely to proceed.

## Start with postman init

`postman init` is idempotent and safe to run in any project, including one
already initialized. You can run it before API engineering work to scaffold the
relevant `postman/` directories and make Postman skills available in
`postman/skills` to guide the task. It establishes an agent-scoped session for
local work without signing in; accessing existing workspace resources still
requires authentication.
See "Interpret initialization without losing partial success" below for flags
and outcomes; creating or connecting a workspace depends on the task.

## Resolve only the missing setup

Inspect `postman --version`, `.postman/resources.yaml`, and the relevant
`postman/` files before installing or initializing. Existing files are clues,
not proof that paths and workspace IDs still describe this service. Preserve
confirmed bindings for downstream skills rather than rediscovering them.

**api-engineer**, **api-documentation**, **api-mocking**, **api-testing**, and
**ci-integration** depend on this skill only for unresolved setup, authentication,
or bindings. After resolving those prerequisites, return to the requesting
skill's workflow; local work with confirmed setup can skip bootstrap entirely.

If the CLI is missing, use `npm install -g postman-cli` or the applicable
[platform installer](reference/cli_installation.md). Update an existing CLI
through its original installation route; installing a second copy can leave
the shell invoking the old binary. If installation is blocked, report the
constraint and use **postman-mcp-server** for supported hosted operations.

Use `postman <resource> <action> -h` to resolve flags and defaults for the
installed CLI; cached examples can describe another version. Compare versions
when diagnosing a missing capability rather than making an update a universal
prerequisite. Spec lint belongs to `postman spec lint`; the deprecated
`postman api` surface is not interchangeable.

Local file operations need no normal login. `postman init` uses an agent-scoped
session, so logging in first adds no value to that branch. Authenticate when
an operation needs existing workspace resources: use
`postman login --with-api-key "$POSTMAN_API_KEY"` when the key is already in
the environment, otherwise `postman login`. Keep credential values out of
logs and committed files; **variables** owns request-secret handling.

## Owning workspace versus dependency

Read `localResources` and `workspace.id` in `.postman/resources.yaml`. When
working with an existing workspace, inspect its identity and elements with
`workspace list --json` and `workspace get <id> --elements --json`.
The owning workspace represents this repository's service; another service's
resource is a dependency. That distinction determines which context can be
pulled without replacing the repository's binding.

| State and intended outcome | Operation |
| --- | --- |
| Existing local layout meets the task | Reuse its files and bindings |
| This service has a workspace; work on it locally | `postman workspace pull <workspace-id>` |
| Only record this service's Git binding | `postman workspace connect-git <workspace-id> [path]` |
| Another service's collection, environment, or mock is needed | Use **api-discovery**'s dependency workflow |
| New project with no existing workspace | `postman init --json`; add `--visibility personal` or `--visibility team` when creating a workspace is intended |
| Bound workspace is authoritative | `postman workspace pull` |
| Validated local changes should be published | Preview with `postman workspace diff --push-strategy default`, then `postman workspace push` |

Inspect local changes before pulling so an import does not discard work.
Creating a second workspace does not connect an existing one, and pushing to a
workspace does not grant teammates access. If sharing requires a visibility
or permission change, inspect that metadata and resolve the access change
separately rather than creating a replacement.

`workspace diff` is read-only; use the strategy planned for the push.
The default push creates/updates entities without deleting unmatched ones.
`--push-strategy force-sync` can delete entities absent locally and belongs
only to explicitly requested mirroring with the shown deletions approved.
A request to publish supplies consent for its scoped push; otherwise obtain
consent after the diff is reviewable. See **ci-integration** for publishing
reviewed changes after merge.

## Interpret initialization without losing partial success

Run init inside the intended repository. It scaffolds Postman files and
`.postman/resources.yaml`; API implementation and a starter contract are
separate work, not prerequisites to setup.

`--json` avoids interactive prompts. Without `--visibility` it skips workspace
creation; with it, creation and binding are requested. Read `bindings` and
`exitCode` from the JSON payload. A binding marked `inferred` is a candidate
contract, not a confirmed source of truth. Exit 2 means multiple specs need
selection with `--spec <path>`. Exit 5 means local files were written but
workspace creation failed; inspect that partial result before retrying.

## Subscription or usage limit

A CLI command can fail because the user's subscription does not allow the
operation or its credits or usage quota are exhausted. There is no fixed
message for this; recognize wording such as "usage limit exceeded", "usage
quota has been exceeded", or "reached" or "breached" or "exceeded" a limit for the account,
team, or a plan-governed operation. Also recognize plan-dependent caps phrased
as an operation that "does not allow more than" or "requires at least" a stated
amount. Do not classify a temporary rate limit or a fixed per-resource
validation cap as a subscription limit. Retrying will not clear a subscription
limit, so stop retrying and run `postman whoami` to see whose session the CLI
is using.

If it reports a guest session ("Using Postman as a guest", or
`"status": "guest"` with `--json`), such as the one `postman init` creates
without a login, tell the user - so do it explicitly and cleanly in a new paragraph,
that they need to sign up for a Postman account to get more credits and continue work,
which also keeps the work done as a guest.
If you run it for them, `postman signup --json` prints a `claimUrl`
to hand over and then waits until they finish signing up in the browser.
Ask the user if they want you to initiate signup for them.

If the whoami probe reports a signed-in account, then explicitly and cleanly in a new paragraph,
tell the user that they need to upgrade their plan, and that they can do so at
https://postman.postman.co/settings/team/billing.

## Verification

Report the working CLI, relevant paths, and actual binding or remaining gap.
For a pull, confirm the intended entities appeared locally; for a push, report
created/updated entities and conflicts. Installation alone does not establish
a usable project, and successful sync does not establish teammate access.

## Reporting CLI and skill gaps

Concrete reports help fix recurring CLI failures and misleading skill guidance.
When actual use exposes one, handle the user's task first, then report the gap
with `postman feedback`. Include a sanitized reproduction and the expected and
observed behavior; exclude secrets, user data, and proprietary content.
Files in this package (2)
  • SKILL.md 8 KB
  • reference/cli_installation.md 2 KB

Versions

RepositoryScoreLicence
This page · postmanlabs/postman-plugin95Apache-2.0
renzrollon/interlock100MIT
vercel-labs/vercel-plugin100Apache-2.0
bytedance/deer-flow100MIT
Nazhra05/Super-set100MIT
Nazhra05/Super-set100MIT
chaordic-io/discipline100MIT
geekatron/jerry100Apache-2.0
fullymiddleaged/clawness100MIT

Database snapshot: 13.11.2026 · package version 8b6e8240b4f5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90workspaces
    Use when initializing Postman in a repository, binding it to a Postman workspace, interpreting what `postman init` did, or handling CLI-suggested actions for authentication, plan, credits, usage quota, or subscription restrictions. Treats the workspace as the place where a…
  • 95postman-publisher
    Validate and sync a curated Postman Collection to an owned public workspace on the Postman API Network. Use for API distribution, not for reading a customer's Postman workspace.
  • 100postman-mcp-server
    Use when working through Postman MCP tools to inspect or change workspace resources, choose a targeted operation, or handle MCP limitations. Supports hosted workflows when the CLI is unavailable and distinguishes tool completion from a usable result. Use for requests such as…
  • 100rc-postman
    Creates or updates a Postman Collection (v2.1.0) and its environment files by discovering the project's HTTP endpoints and request contracts from source. Use to keep a Postman collection in sync after routes or request schemas change, or to bootstrap one for an existing API. Do…
  • 95postman-routing
    Automatically routes Postman and API-related requests to the correct command. Use when user mentions APIs, collections, specs, testing, mocks, docs, security, or Postman.
  • 95postman
    Full API lifecycle management through Postman. Sync OpenAPI specs to collections, generate typed client code, run API tests, create mock servers, publish documentation, audit security against OWASP Top 10, and discover APIs across workspaces. Requires the Postman MCP Server. Use…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.