Pulumi skills
Infrastructure-as-code skills for Pulumi skills-hub.ai mirrors 12 skills from Pulumi daily — every skill links back to its upstream GitHub source. Install with one command across Claude Code, Cursor, Codex, Windsurf, and any MCP-compatible tool.
Upstream: github.com/pulumi/agent-skills
Installing a Pulumi skill
Pick a skill below, then run the install command for your AI coding tool. The skills-hub CLI writes the SKILL.md to the right directory and tracks the install in .skills.json so your team gets reproducible installs.
# Install a Pulumi skill
npx @skills-hub-ai/cli install <skill-slug>
# Browse all Pulumi skills via API
curl https://skills-hub.ai/api/v1/skills?source=pulumi
# Browse all sources
open https://skills-hub.ai/sourcesTop Pulumi skills
See all →The most-installed skills from Pulumi, ranked by adoption.
01provider-upgrade
Upgrade any Pulumi provider to a newer version. Use when users explicitly want to upgrade or update a provider, update provider dependencies, check for breaking changes, or bump provider versions in their code. This applies to all providers (aws, azure-native, gcp, kubernetes, aws-native, cloudflare, datadog, etc.) - not just Tier 1 providers. Do NOT use for just querying which stacks use what versions. Use skill `package-usage` for version audits and affected-stack discovery. Do NOT use for general infrastructure tasks.
Buildfrom Pulumi02pulumi-arm-to-pulumi
Convert or migrate Azure ARM (Azure Resource Manager) templates, Bicep templates, or code to Pulumi, including importing existing Azure resources. This skill MUST be loaded whenever a user requests migration, conversion, or import of ARM templates, Bicep templates, ARM code, Bicep code, or Azure resources to Pulumi.
Buildfrom Pulumi03pulumi-terraform-to-pulumi
Migrate Terraform/OpenTofu projects to Pulumi, including translating HCL source code and/or importing Terraform state into a Pulumi stack. Use when a user wants to convert Terraform to Pulumi, migrate from HCL, or import tfstate into Pulumi. Do NOT trigger for general Terraform-vs-Pulumi comparisons or questions about using both tools side-by-side.
Buildfrom Pulumi04pulumi-cdk-to-pulumi
Convert an AWS CDK application to Pulumi. This skill MUST be loaded whenever a user requests migration or conversion of a CDK application to Pulumi.
Buildfrom Pulumi05pulumi-best-practices
Best practices for writing reliable Pulumi programs. Covers Output handling, resource dependencies, component structure, secrets management, safe refactoring with aliases, and deployment workflows.
Buildfrom Pulumi06pulumi-esc
Guidance for working with Pulumi ESC (Environments, Secrets, and Configuration). Use when users ask about managing secrets, configuration, environments, short-term credentials, configuring OIDC for AWS, Azure, GCP, integrating with secret stores (AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, 1Password), or using ESC with Pulumi stacks.
Buildfrom Pulumi07cloudformation-to-pulumi
Convert an AWS CloudFormation stack or template to Pulumi. This skill MUST be loaded whenever a user requests migration or conversion of CloudFormation to Pulumi.
Buildfrom Pulumi08pulumi-component
Guide for authoring Pulumi ComponentResource classes. Use when creating reusable infrastructure components, designing component interfaces, setting up multi-language support, or distributing component packages.
Buildfrom Pulumi09pulumi-automation-api
Best practices for using Pulumi Automation API to programmatically orchestrate infrastructure operations. Covers multi-stack orchestration, embedding Pulumi in applications, architecture choices, and common patterns.
Buildfrom Pulumi10package-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.
Buildfrom Pulumi11pulumi-upgrade-provider
Automate Pulumi provider repo upgrades with the `upgrade-provider` tool. Use when upgrading a pulumi provider repository to a new upstream version, running `upgrade-provider`, and addressing its common failure modes like patch conflicts or missing module mappings.
Buildfrom Pulumi12upstream-patches
Create, amend, remove, and rebase patches for Terraform provider submodules using `./scripts/upstream.sh`. Use when `upgrade-provider` or manual patch work needs owning-patch lookup, patch conflict fixes, patch/hunk removal, or upstream rebase.
Buildfrom Pulumi
About this source
skills-hub.ai mirrors skills from 90+ official GitHub repositories every day. Each imported skill is parsed from a SKILL.md file in the source repo, gets a security scan and quality score on import, and links back to its upstream source of truth.
Last sync: Apr 30, 2026, 10:11 PM (success).
Pulumi skills — frequently asked
What are Pulumi skills?
Pulumi skills are AI coding skills published by Pulumi (Infrastructure-as-code skills for Pulumi) and mirrored daily on skills-hub.ai. They are SKILL.md files that follow the open Agent Skills standard, so they work in Claude Code, Cursor, Codex CLI, Windsurf, Copilot, and any MCP-compatible tool.
How many Pulumi skills are available?
skills-hub.ai indexes 12 skills from Pulumi, synced daily from the upstream GitHub repository (https://github.com/pulumi/agent-skills).
How do I install a Pulumi skill?
Run `npx @skills-hub-ai/cli install <skill-slug>` in your project. The CLI writes the SKILL.md to the right directory for your AI tool and adds it to your `.skills.json` lockfile so your team gets the same skills at the same versions.
Are these official Pulumi skills?
Yes. Every skill from this source is mirrored from Pulumi's own GitHub repository (https://github.com/pulumi/agent-skills). Each skill page links back to the upstream source of truth, so you can verify the original.