pulumi agent-skills
OFFICIALLABSCO SUMMARY
Four of the fourteen convert other infrastructure-as-code tools into Pulumi programs: pulumi-terraform-to-pulumi, pulumi-cdk-to-pulumi, cloudformation-to-pulumi, and pulumi-arm-to-pulumi, which handles both ARM JSON and Bicep. Seven more are the entry-point and specialist skills for writing and running Pulumi itself: pulumi-overview routes a request to the right specialist, and the rest cover ComponentResource authoring, the Automation API, ESC secrets and configuration, safe provider upgrades, and a package-usage auditor that finds every stack in an organization still on an old provider version.
The last three are for a narrower audience than "anyone using Pulumi": pulumi-upgrade-provider and upstream-patches are for people maintaining a Pulumi provider repository itself, bridging and patching an upstream Terraform provider, not for someone deploying their own infrastructure. pulumi-neo-handoff transfers an in-progress coding-agent session to Pulumi Neo, Pulumi's own hosted agent product, and does nothing on its own if you don't use Neo.
READ THE FULL ANALYSIS
Most of this expects a Pulumi setup already in place. Eight of the fourteen skills are classed as needing account credentials, a logged-in Pulumi CLI, cloud provider credentials, or both, before they do anything beyond reading code. Five are local developer tooling, CLI scripts like upgrade-provider and upstream.sh, that work from a checked-out repository alone, and just one, pulumi-automation-api, is guidance you can read without any of that.
This is Pulumi's own repository, not a community wrapper. It is Apache-2.0 licensed, sits at 61 stars, and installs through Pulumi's own plugin groups, pulumi-migration, pulumi, pulumi-delegation, and pulumi-package-maintenance, or via npx skills add for other agents; the four groups map exactly to the four audiences above.
ALSO IN THIS PACKAGE
pulumi-migration
Convert and import infrastructure from Terraform, CDK, ARM, and CloudFormation to Pulumi
pulumi
Teach your agent Pulumi: infrastructure as code in TypeScript, Python, Go, C#, Java, YAML, or HCL. Skills for writing and operating cloud infrastructure, migrating from Terraform, CloudFormation, CDK, and ARM, and delegating work to Pulumi Neo, Pulumi's AI platform engineer.
pulumi-delegation
Hand off in-progress work from coding agents to Pulumi Neo for delegated execution
pulumi-package-maintenance
Maintain Pulumi provider repositories: run upgrade-provider and manage upstream Terraform patches
WHAT'S INSIDE
14 showing · 14 totalNothing else to set up — install it and go.
cloudformation-to-pulumi
Takes the AWS setup a CloudFormation template currently manages and rebuilds it as a Pulumi program — then hands the live resources across untouched, checked by the fact that the first run afterwards wants to change nothing.
package-usage
A version audit for one Pulumi organization: every deployment that uses a given package, the version it is on, and whether that has fallen behind the current release.
provider-upgrade
Moving a Pulumi provider to a newer version often makes the next deployment want to destroy and rebuild things that should not change at all. This walks through every one of those surprises, resource by resource, and stops short of deploying anything.
pulumi-arm-to-pulumi
No tool converts an Azure ARM or Bicep template to Pulumi automatically, so the translation is done here by hand, one resource at a time. The finished program can then take charge of the Azure resources that are already running, rather than creating new ones.
pulumi-automation-api
Lets one program deploy, inspect, and tear down cloud infrastructure directly, instead of a person typing commands at a terminal, so infrastructure can be handed out on request by other software.
pulumi-best-practices
A checklist of seven common Pulumi coding mistakes, each shown wrong then fixed — among them leaving secrets in plain text, renaming a resource in a way that quietly destroys it, and deploying without first looking at what will change.
pulumi-cdk-to-pulumi
A converter does the first pass from an AWS CDK app to Pulumi; the work here is everything it leaves behind — the one-off helper resources, the container images, and the pre-packaged code — finished by hand so the result actually deploys.
pulumi-component
Packs cloud resources that always go together — a storage bucket and the permissions around it, say — into a single reusable building block, then covers how to hand that block to other teams and other programming languages.
pulumi-esc
One place to keep the passwords, keys and settings a deployment needs, so they stop being copied into each project by hand — and a way to borrow a cloud login that expires on its own rather than storing a permanent one.
pulumi-neo-handoff
Passes the work you are halfway through to Pulumi Neo, Pulumi's own AI agent, together with what has been decided so far and where the code lives. It is a one-way move: nothing comes back to whoever handed it over.
pulumi-overview
The front door for anything to do with Pulumi: it sizes up the request — one quick cloud resource, a whole project kept in code, or ongoing supervision of what is already running — and sends it to the right place rather than answering everything itself.
pulumi-terraform-to-pulumi
Two things have to move when a team leaves Terraform or OpenTofu for Pulumi: the record of what is already deployed, and the code that describes it. Both are carried across here, and the job is not finished until Pulumi agrees nothing needs changing.
pulumi-upgrade-provider
This is for the people who build a Pulumi provider rather than the people who use one: it brings the provider's own source code up to a newer release of the thing it wraps, unsticks the upgrade tool whenever it stalls, and leaves a branch ready for review.
upstream-patches
Pulumi keeps a stack of small private fixes layered on top of somebody else's Terraform provider code. This is how those fixes get edited, dropped, or re-applied on a newer version of that borrowed code, without anyone editing the borrowed copy by hand.
HOW TO GET IT
npx skills add pulumi/agent-skillsnpx skills add pulumi/agent-skills --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.
/plugin marketplace add pulumi/agent-skills/plugin install pulumi-migration@pulumi-agent-skills/plugin install pulumi@pulumi-agent-skills/plugin install pulumi-delegation@pulumi-agent-skillsTyped inside the agent's own prompt, not in a terminal. The marketplace lists 4 plugins; three are shown. Every one installs the same way, with its own name before @pulumi-agent-skills.