AutoGineer
Generated banner for Package Usage
Generated logo for Package Usage

Package Usage

PulumiOfficialPublished by Pulumi

  • Skill
  • Research and analysis
  • Cloud and DevOps
  • Apache-2.0
  • No issues found
Download ZIP

From the author

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.
— the description by Pulumi

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The package-usage skill provides a systematic way to query the Pulumi Cloud API to audit package versions across multiple stacks. It helps engineering teams maintain visibility into their infrastructure dependencies by identifying which projects and stacks are using specific package versions. This is essential for planning coordinated upgrades, assessing the impact of breaking changes, and ensuring consistency across an organization's infrastructure footprint.

What it does

  • Queries the Pulumi Cloud API to retrieve the latest version of a specific package.
  • Lists all stacks within an organization that utilize a specified package.
  • Compares current stack versions against the latest available package version.
  • Generates a structured markdown report detailing the status of each stack.
  • Provides a summary count of outdated versus up-to-date stacks.

When to use it

  • When you need to perform a cross-stack audit of package versions.
  • Before publishing breaking changes to a component package to identify affected stacks.
  • When planning a coordinated rollout of a package upgrade across the organization.
  • To identify unmaintained or outdated package versions across multiple projects.

Advantages

  • Centralized visibility into package usage across the entire organization.
  • Simplifies the identification of technical debt related to outdated dependencies.
  • Reduces the risk of breaking changes by identifying all impacted stacks beforehand.
  • Standardizes the reporting format for dependency audits.

Usage examples

“Which stacks in my organization are using an outdated version of the custom-vpc package?”
The agent queries the latest version of custom-vpc, retrieves all stacks using it, compares the versions, and outputs a markdown table showing which stacks are outdated.
“List all stacks currently using the my-company-auth package.”
The agent returns a list of all projects and stacks currently utilizing the specified package, including their current version and last update timestamp.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/pulumi/package-usage/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip package-usage.zip -d .agents/skills

Documentation by Pulumi

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.

Files

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Pulumi
Publisher
Pulumi (Official)
Source
pulumi/agent-skills · pulumi/skills/package-usage · commit 82f222a
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Pulumi.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download package-usage.zip