From pulumi-authoring
Tracks Pulumi package usage and versions across stacks, identifies outdated versions, and upgrades stacks by updating dependency files like package.json or go.mod and creating pull requests.
npx claudepluginhub pulumi/agent-skillsThis skill uses the workspace's default tool permissions.
`GET /api/registry/packages?name={package_name}&orgLogin={orgName}`
Manages Pulumi stacks for dev, staging, and prod environments with Bash commands for creation, selection, configuration, YAML files, and TypeScript config reading.
Upgrades any Pulumi provider (AWS, Azure, GCP, Kubernetes, etc.) to newer versions by bumping dependencies, running previews, categorizing diffs, and fixing code translations for zero-diff results.
Provides Pulumi IaC best practices for performance and reliability when writing, reviewing, or refactoring code on stacks, components, state management, secrets, lifecycle options, and CI/CD.
Share bugs, ideas, or general feedback.
GET /api/registry/packages?name={package_name}&orgLogin={orgName}
You must include the orgLogin parameter with the user's organization name. The response contains a packages array. Each entry has a version field (the latest version), plus name, publisher, source, and packageStatus.
GET /api/orgs/{orgName}/packages/usage?packageName={package_name}
Replace {orgName} with the organization name from context or the PULUMI_ORG environment variable.
Response fields:
packageName: The queried packagestacks: Array of {stackName, projectName, version, lastUpdate}totalStacks: Total countUse when the user wants to know which stacks are using an outdated version of a package.
version against the latest to identify outdated stacksUse when the user wants to upgrade a specific stack/project to the latest version of a package.
runtime field in Pulumi.yaml, then update the correct dependency file:
nodejs → package.jsonpython → requirements.txt or pyproject.tomlgo → go.modyaml → Pulumi.yamlpulumi preview to catch any breaking changes introduced by the version bump before merging.