pulumi/agent-skills
18 skills11.9k installs1.1k starsGitHub
Install
npx skills add https://github.com/pulumi/agent-skillsSkills in this repo
1Pulumi Arm To PulumiIf you have already generated a migration plan before loading this skill you MUST 1 Review your existing plan against the workflows and requirements in this skill 2 Identify any gaps missing steps or incorrect assumptions 3 Update and revise your plan to align with this skill s guidance 4 Communicate the adjusted plan to the user before proceeding The migration output MUST meet all of the following 1 Complete Resource Coverage Every ARM template resource MUST Be represented in the Pulumi program OR Be explicitly justified in the final report 2 Successful Deployment The produced Pulumi program must be structurally valid and capable of a successful pulumi preview assuming proper config The pulumi arm to pulumi agent skill provides documented workflows prerequisites triggers and safety guidance from its SKILL md source Agents load it when user requests match the description and follow step by step instructions without inventing capabilities It integrates with standard agent tooling for the tasks inputs outputs and failure modes described in the repository documentation1.9kinstalls2Pulumi Best PracticesThe pulumi-best-practices skill loads when writing, reviewing, or debugging Pulumi programs, asking about Output and apply usage, creating ComponentResource classes, refactoring with aliases to avoid destroys, configuring secrets, or setting up pulumi preview/up CI. Key practices forbid creating resources inside apply() because they disappear from preview and break dependency tracking. Detection signals, parent/child relationships, pulumi.interpolate patterns, and dependency ordering guidance help agents catch race conditions before deploy. Use for infrastructure code review, refactors without resource replacement, and secrets/config setup in Pulumi TypeScript or Python. Never create resources inside apply(); breaks preview and dependency tracking ComponentResource patterns and parent/child relationship guidance Aliases for refactors without destroying existing cloud resources Secrets, config, and pulumi preview/up CI workflow setup Output, apply, and pulumi.interpolate correctness patterns pulumi-best-practices guides correct Pulumi TypeScript/Python patterns for resources, outputs, and CI Reviewed Pulumi program with safe Output usage, aliases, and CI preview/up flow User writes.1.8kinstalls3Pulumi EscThe pulumi-esc skill guides Pulumi ESC (Environments, Secrets, and Configuration) for centralizing secrets, composing layered environments, and generating short-term OIDC credentials for AWS, Azure, and GCP. It documents essential CLI commands including env init, set, open, run, and stack linking via pulumi config env add. Agents help teams integrate external secret stores like AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, and 1Password. Workflows distinguish env get static definitions from env open resolved secrets for safe operational use. Pulumi ESC environments, secrets, and configuration management. OIDC dynamic credentials for AWS, Azure, and GCP. External secret store integrations and RBAC auditing. CLI workflows: env init, set, open, run, stack link. Centralized secrets with versioned environment composition. Manage Pulumi ESC environments, secrets, OIDC credentials, and stack-linked configuration.1.2kinstalls4Pulumi ComponentThe pulumi-component skill guides authoring Pulumi ComponentResource classes for reusable infrastructure abstractions with clear interfaces, child resource encapsulation, and multi-language SDK distribution. It documents component design, input/output property patterns, testing strategies, and packaging for npm, PyPI, and other language ecosystems. Agents help platform teams publish internal component libraries instead of copying raw resource boilerplate. The skill triggers when creating reusable IaC components or designing component APIs for org-wide Pulumi adoption. Author Pulumi ComponentResource reusable infrastructure components. Child resource encapsulation and clear component interfaces. Multi-language SDK packaging for npm, PyPI, and more. Testing and distribution patterns for component libraries. Platform IaC abstractions instead of raw resource copies. Author reusable Pulumi ComponentResource classes with multi-language packaging patterns.1.1kinstalls5Pulumi Automation ApiThe pulumi-automation-api skill guides running Pulumi programmatically via the Automation API to embed infrastructure operations in applications, orchestrate multiple stacks in code, and build self-service portals replacing manual CLI flows. It documents inline, local, and remote workspace patterns with language-specific SDK examples. Agents help platform teams expose guarded IaC actions to internal users without handing everyone raw CLI credentials. The skill triggers when users ask to run Pulumi from application code or orchestrate stacks programmatically. Programmatic Pulumi via Automation API embed in apps. Multi-stack orchestration and self-service portal patterns. Inline, local, and remote workspace execution modes. Language SDK examples for guarded IaC automation. Replaces ad hoc CLI scripts with typed Automation API flows. Embed Pulumi programmatically with Automation API for portals and multi-stack orchestration.999installs6Pulumi Terraform To PulumiThe pulumi-terraform-to-pulumi skill walks full Terraform-to-Pulumi migrations without pulumi convert, using terraform-migrate plugin for state mapping instead. Agents confirm terraform_dir, pulumi_dir, target language, and whether to import state before creating an empty Pulumi project inside the repo, running pulumi_up, pulling remote tfstate when needed, generating /tmp/pulumi-state.json and required-providers.json, installing provider packages at pinned versions, importing stack state, and iterating until pulumi_preview shows an empty diff. Critical constraints forbid pulumi convert, terraform-module package add, and writing under /workspace. ESC environment linking is offered for credentials. Ends with a pull request of migrated code.757installs7Pulumi Cdk To PulumiThe pulumi-cdk-to-pulumi skill migrates AWS CDK applications to Pulumi using guided conversion workflows that preserve resource mappings and stack semantics. Agents inventory CDK constructs, translate to Pulumi language SDKs, import or align state where applicable, and iterate on pulumi preview until diffs are acceptable. Emphasizes in-repo project creation, provider version pinning, and credential setup consistent with other Pulumi migration skills. Use when teams exit CDK for Pulumi while minimizing infrastructure drift.705installs8Cloudformation To PulumiThe cloudformation-to-pulumi skill converts existing AWS CloudFormation stacks to Pulumi programs and imported state. Agents export CloudFormation templates and stack resources, map types to Pulumi providers, create projects in-repo, import state, and iterate until pulumi preview shows no unexpected changes. Follows Pulumi migration constraints: no destructive shortcuts, pinned provider versions, and credential environments for secure imports. Use when teams standardize on Pulumi while retaining existing CloudFormation-provisioned infrastructure.701installs9Package UsageTrack 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. `GET /api/registry/packages?name={package_name}&orgLogin={orgName}`579installs10Provider Upgrade>. A provider upgrade is a translation, not a change request. The provider-upgrade skill documents workflows, constraints, and examples from SKILL.md for agent-assisted execution.566installs11Pulumi Upgrade ProviderAutomate 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. Run `upgrade-provider`, fix known failures, and rerun until success. Keep git operations read-only in the repo; the tool owns branch/commit/PR state.520installs12Upstream PatchesCreate, 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. `upstream/` is a git submodule pointing to the upstream Terraform provider. `patches/` contains patch files applied on top of it. Use `./scripts/upstream.sh` to manage patch state.478installs13Pulumi OverviewRoutes infrastructure work across three Pulumi levels. Level 1 uses pulumi do for direct CRUD against any provider without project files, ideal for one-off buckets, DNS records, or monitors. Level 2 scaffolds multi-resource programs in Python, TypeScript, Go, C#, or Java with preview, up, refresh, stacks, and config. Level 3 adds ESC credentials, policy packs, hosted deployments, drift detection, and scheduled operations. Covers npx pulumi invocation, agent account claim URLs, provider credential separation, property input via flags or PCL files, cross-command resource wiring, and graduating do-created resources via pulumi import. References specialized migration and best-practice skills for Terraform, CDK, CloudFormation, components, ESC OIDC, and provider upgrades.280installs14Pulumi Neo HandoffHand off the current thread to a new Pulumi Neo task as a one-way transfer. Use when the user explicitly asks to hand off, send, transfer, or continue current work in Pulumi Neo (e.g. "hand this to Neo", "continue in Neo", "/neo-handoff"). Do not load when the user only mentions Neo, asks what Neo can do, asks for an AI-written PR or preview explanation, or hands off to a different agent. Transfer the current in-progress work to a new Pulumi Neo task. This is a one-way handoff: control passes to Neo and does not return to the calling agent.248installs15PulumiPulumi Agent Skills. Covers setup, configuration, and when-to-use guidance from upstream documentation for pulumi.0installs16Pulumi DelegationPulumi Agent Skills. Covers setup, configuration, and when-to-use guidance from upstream documentation for delegation.0installs17Pulumi MigrationPulumi Agent Skills. Covers setup, configuration, and when-to-use guidance from upstream documentation for migration.0installs18Pulumi Package MaintenancePulumi Agent Skills. Covers setup, configuration, and when-to-use guidance from upstream documentation for package-maintenance.0installs