Agent skill · pulumi
pulumi-context-api
Query the Pulumi Context API, a graph query interface over an organization's infrastructure in Pulumi Cloud. Use when a question is about relationships or reachability across resources and stacks: the impact of a change ("what breaks if I change this?", blast radius), what depends on a resource or a stack's outputs, which provider instances manage which resources and at what versions, orphaned or unreferenced resources, or references that cross stacks and cloud accounts, including resources Pulumi doesn't manage. Don't load it for finding a single resource by name, type, or property (Resource Search covers that), or for update history and failure debugging (use skill `pulumi-debug-failed-operation`).
What it needs
About 3k tokens when loaded.
What this skill does
Query the Pulumi Context API The Context API answers questions about an organization's cloud infrastructure as a graph: what exists, what depends on what, what a change would affect. It covers resources found through Pulumi Discovery, not just Pulumi-managed ones. Prefer it over Resource Search whenever the question involves relationships. Resource Search finds individual resources but cannot follow edges, so answering "what depends on X" with repeated searches is slow and usually incomplete. Public preview, for organizations on the Enterprise and Business Critical editions. Needs Pulumi CLI v3.243.0 or newer, an active pulumi login, and a role granting resources:search (the default Member and Admin roles do). Step 1: fetch the primer, always pulumi whoami -v lists every organization the login can reach. Ask which one the question is about rather than assuming the default org — that is often an individual account with no entitlement. This returns a self-contained guide to composing selectors — vocabulary, edge types, engine caps, worked examples, pagination, completeness rules, and the traps that produce a confident wrong answer instead of an error. It is served by the deployment that answers your queries, so it is the contract, and it moves between schema versions. This skill bootstraps you to it and stops there; everything below defers to it. Fetch it fresh in every session and for every org you query — a primer remembered from earlier may describe a schema this deployment no longer serves. Read it in full — never truncate it with head, tail, or a byte cap. A clipped primer means malformed selectors and rejected queries. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pulumi/pulumi-context-api