pulumi/agent-skills
8 skills7k installs448 starsGitHub
Install
npx skills add https://github.com/pulumi/agent-skillsSkills in this repo
1Pulumi Arm To Pulumipulumi-arm-to-pulumi is a Pulumi agent skill that teaches conversion patterns from Azure ARM and Bicep templates into Pulumi TypeScript using the azure-native provider. Solo and indie builders who inherited JSON templates, are standardizing on Pulumi, or need agent-assisted migrations use it when Operate-phase infra work blocks shipping fixes. The skill walks through parameterization with pulumi.Config, SKU and kind enums, HTTPS flags, and resource group scoping so generated code matches template intent. It is reference documentation packaged for coding agents rather than a live Azure API integration, which makes it ideal for incremental file-by-file migration in a git repo. Use it alongside your existing ARM source of truth until imports and stacks are validated in a non-production subscription.1.7kinstalls2Pulumi Best Practicespulumi-best-practices encodes durable patterns for Pulumi programs in TypeScript and Python, aimed at solo builders who own both application code and cloud stacks. It activates when you are authoring new components, reviewing a teammate’s stack, refactoring resource names, or chasing mysterious dependency races. The centerpiece anti-pattern—creating resources inside apply()—is called out because it breaks preview semantics and hides dependencies from the engine. The skill also covers ComponentResource structure, aliases for safe renames, secrets and config handling, and CI flows that treat preview as a contract before up. Use it while scaffolding infra alongside your API, when wiring GitHub Actions for Pulumi, and when debugging ordering issues in production stacks without gambling on destructive replacements.1.3kinstalls3Pulumi Escpulumi-esc is an agent skill from Pulumi’s agent-skills repo for working with Pulumi ESC—Environments, Secrets, and Configuration. Solo builders shipping SaaS or APIs who already use or plan to use Pulumi benefit when they need centralized secrets, environment-specific settings, and safer handoffs between local dev, CI, and cloud deploys. The skill steers coding agents toward ESC-aligned practices instead of scattering `.env` files or pasting credentials into prompts. It sits in the build phase under integrations because that is when stacks, providers, and runtime config are wired together, though the same patterns matter again in ship and operate when rotating secrets or changing environments. Install it when your agent is scaffolding Pulumi projects, debugging missing config, or documenting how teammates should pull secrets at runtime. Prism lists it as a focused integration skill rather than a full DevOps playbook; pair it with broader IaC or CI skills when you need end-to-end deployment.842installs4Pulumi Componentpulumi-component is a Pulumi-focused agent skill for solo builders who are tired of copy-pasting the same VPC, bucket, and service wiring across stacks. It teaches how to extend ComponentResource with a stable type URN, pass name/args/ComponentResourceOptions, parent every child to the component, and call registerOutputs so pulumi preview and Pulumi Cloud show one logical node with nested children. The skill is invoked when you create a new component, design args interfaces, enable consumption from TypeScript, Python, Go, or other Pulumi languages, or refactor inline resources into a distributable package. It deliberately scopes itself to authoring and distribution; for everyday Output handling, secrets, aliases, and preview workflows, the readme points you to pulumi-best-practices. Intermediate builders shipping SaaS or APIs on AWS, Azure, or GCP get the most value—especially when they want infra that reads like product code rather than a flat resource list.794installs5Pulumi Automation Apipulumi-automation-api teaches agents how to run Pulumi without shelling out to the CLI, using the Automation API to create or select stacks, execute inline programs, and orchestrate dependencies across dev, staging, and production. Solo builders who outgrow one-off pulumi up commands—but are not ready for a full platform team—use it to embed infrastructure lifecycle inside a Node service, internal admin app, or release tool. The skill loads when users ask about LocalWorkspace, createOrSelectStack, multi-stack sequencing, parallel deployments, or passing stack outputs between programs. Advanced complexity reflects async orchestration, state backends, secrets, and failure handling that must stay correct when real money and uptime are on the line. It pairs naturally with Pulumi project repos you already maintain and clarifies when programmatic control beats Makefile glue for repeatable ship and operate workflows.748installs6Pulumi Terraform To PulumiPulumi Terraform to Pulumi is an agent skill for solo builders who already run Terraform or OpenTofu and want a guided move to Pulumi without breaking state. It forces a planning conversation up front: where HCL lives, where the new Pulumi project should sit inside the checked-out repository, target language, and whether you only need code translation or also Pulumi stack states from existing tfstate. The workflow is opinionated for safety—use the terraform-migrate plugin instead of pulumi convert, never use pulumi package add terraform-module for this path, and bootstrap with an empty project plus an initial pulumi up before deeper migration work. That structure suits indie teams juggling one cloud footprint who need the agent to follow Pulumi’s supported migration rails rather than improvising destructive commands.570installs7Pulumi Cdk To Pulumipulumi-cdk-to-pulumi is a Pulumi agent skill centered on the `cdk2pulumi` tool plugin, which translates synthesized AWS CDK Cloud Assemblies into Pulumi YAML programs. Solo builders and small teams use it when CDK stacks already exist but they want Pulumi’s workflow, state model, or org standards without manually porting every construct. The skill documents install prerequisites, the required `--assembly` path (typically `cdk.out`), and optional filters for stacks, stages, and custom resources. It also explains how partial conversions leave external stack outputs as config placeholders—an operational detail that prevents broken deploys. Expect intermediate familiarity with both CDK synth and Pulumi CLI; the skill is procedural glue, not a greenfield architecture generator.530installs8Cloudformation To PulumiCloudformation-to-pulumi is a Pulumi agent skill that guides migration from AWS CloudFormation stacks or templates into Pulumi-managed infrastructure. It centers on the cdk-importer CLI plugin: install the tool, load AWS credentials through Pulumi ESC (asking which ESC environment to use if none is set), confirm the target AWS region, then run program import with required flags `--program-dir` and `--stack`. Solo and indie builders shipping on AWS use it when they want Pulumi workflows—previews, policy-as-code, multi-cloud patterns—without replacing resources that CloudFormation already created. The skill stresses that wrong-region imports produce incorrect results, and documents optional bulk import files for partial failures. It fits operators and builders who already have a generated Pulumi program whose resource names align with CloudFormation logical IDs.520installs