How do I install the Package Usage skill?

Run npx skillmds@latest add pulumi/package-usage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Package Usage safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Package Usage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Package Usage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Package Usage?

pulumi (@pulumi) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Package Usage by pulumi — Agent Skill

Name: Package Usage
Rating: 4.5 (4 reviews)
Author: pulumi

Package Usage

Track which stacks across a Pulumi organization use a specific package and at what versions. Use for cross-stack audits, identifying outdated or unmaintained package versions across many stacks, finding affected stacks before publishing breaking changes to a component package, or planning coordinated upgrade rollouts. Do NOT use for upgrading a cloud provider package (pulumi-aws, pulumi-azure-native, pulumi-gcp, pulumi-kubernetes, etc.) in a single project — use skill `provider-upgrade` instead. Do NOT use for general infrastructure creation, resource provisioning, or how-to questions about a package.

pulumi ebf00d9 2.8 KB Updated Sep 9, 2026

File contents

API Reference

Query the Pulumi Cloud API with the pulumi api CLI subcommand. It authenticates with your existing Pulumi credentials and returns JSON.

Get the latest version of a package

pulumi api /api/registry/packages -F name={package_name} -F orgLogin={orgName}

Include orgLogin with the user's organization name. Omit -F name=... to list all packages visible to the organization (useful when the user has not named a specific package). The response contains a packages array. Each entry has a version field (the latest version), plus name, publisher, source, and packageStatus.

Get stack usage for a package

pulumi api /api/orgs/{orgName}/packages/usage -F packageName={package_name}

Replace {orgName} with the org name from context, PULUMI_ORG, or ask the user. packageName is required; query one package at a time.

Response fields:

packageName: The queried package
stacks: Array of {stackName, projectName, version, lastUpdate}
totalStacks: Total count

Workflow: Find outdated stacks

Use when the user wants to know which stacks are using an outdated version of a package.

Get the latest version of the package
Get stack usage for the package
Compare each stack's version against the latest to identify outdated stacks
Present results using the output format below

Output Format

Present results as a markdown table followed by a summary line:

| Project | Stack | Current Version | Latest Version | Status |
|---------|-------|-----------------|----------------|--------|
| my-app  | dev   | 6.40.0          | 6.52.0         | Outdated |
| my-app  | prod  | 6.52.0          | 6.52.0         | Up-to-date |

2 of 2 stacks checked. 1 outdated.

Out of scope: upgrading a specific stack

This skill identifies outdated stacks. It does not perform the upgrade itself. For actually bumping a package version in a project — editing package.json, requirements.txt, pyproject.toml, go.mod, or Pulumi.yaml, running pulumi preview, and reconciling the diff — hand off to the provider-upgrade skill.

---name: package-usagedescription: Track which stacks across a Pulumi organization use a specific package and at what versions. Use for cross-stack audits, identifying outdated or unmaintained package versions across many stacks, finding affected stacks before publishing breaking changes to a component package, or planning coordinated upgrade rollouts. Do NOT use for upgrading a cloud provider package (pulumi-aws, pulumi-azure-native, pulumi-gcp, pulumi-kubernetes, etc.) in a single project — use skill `provider-upgrade` instead. Do NOT use for general infrastructure creation, resource provisioning, or how-to questions about a package.--- ## API Reference Query the Pulumi Cloud API with the `pulumi api` CLI subcommand. It authenticates with your existing Pulumi credentials and returns JSON. ### Get the latest version of a package ``` pulumi api /api/registry/packages -F name={package_name} -F orgLogin={orgName} ``` Include `orgLogin` with the user's organization name. Omit `-F name=...` to list all packages visible to the organization (useful when the user has not named a specific package). The response contains a `packages` array. Each entry has a `version` field (the latest version), plus `name`, `publisher`, `source`, and `packageStatus`. ### Get stack usage for a package ``` pulumi api /api/orgs/{orgName}/packages/usage -F packageName={package_name} ``` Replace `{orgName}` with the org name from context, `PULUMI_ORG`, or ask the user. `packageName` is required; query one package at a time. Response fields: - `packageName`: The queried package - `stacks`: Array of `{stackName, projectName, version, lastUpdate}` - `totalStacks`: Total count ## Workflow: Find outdated stacks Use when the user wants to know which stacks are using an outdated version of a package. 1. Get the latest version of the package 2. Get stack usage for the package 3. Compare each stack's `version` against the latest to identify outdated stacks 4. Present results using the output format below ## Output Format Present results as a markdown table followed by a summary line: ``` | Project | Stack | Current Version | Latest Version | Status | |---------|-------|-----------------|----------------|--------| | my-app | dev | 6.40.0 | 6.52.0 | Outdated | | my-app | prod | 6.52.0 | 6.52.0 | Up-to-date | 2 of 2 stacks checked. 1 outdated. ``` ## Out of scope: upgrading a specific stack This skill identifies outdated stacks. It does not perform the upgrade itself. For actually bumping a package version in a project — editing `package.json`, `requirements.txt`, `pyproject.toml`, `go.mod`, or `Pulumi.yaml`, running `pulumi preview`, and reconciling the diff — hand off to the `provider-upgrade` skill.

Frequently asked questions