Pulumi Agent Skills

Install

/plugin marketplace add pulumi/agent-skills
/plugin install pulumi

This is third-party code. Review the repository files before installing.

What it does

Skills from the Pulumi team come in four groups. The core group teaches the agent to write reliable Pulumi programs, author components, use the Automation API and ESC, upgrade providers safely and debug a failed pulumi up. The migration group converts Terraform, AWS CDK, CloudFormation, ARM and Bicep projects into idiomatic Pulumi code. Separate skills serve provider authors and hand off in-progress work to Pulumi Neo.

Who it is for. For DevOps engineers and developers who define cloud infrastructure with Pulumi or are moving to it.

Example request

Convert this Terraform configuration to Pulumi TypeScript

Limitations

Some skills rely on Pulumi Cloud: Discovery, the Context API, package usage tracking and Neo handoff require a Pulumi Cloud account. The skills do not replace reviewing pulumi preview before applying changes.

How to disable. Uninstall the pulumi plugin via /plugin in Claude Code or Codex, or delete the skill folders installed with npx skills.

Security check

• The agent may run pulumi commands that change cloud infrastructure
• The skills deal with secrets and credentials through ESC

README in short

The README describes four skill groups: migration, core Pulumi skills, provider maintenance and Neo handoff, with a table per skill. Install via /plugin in Claude Code, including declaratively through .claude/settings.json for teams, via the Codex marketplace or via npx skills per group. It gives example prompts for migration, ESC and components. Apache 2.0 licensed.

SKILL.md

---
name: pulumi-best-practices
version: 1.0.0
description: Load when the user is writing, reviewing, or debugging Pulumi TypeScript/Python programs; asks about Output<T> or apply() usage; wants to create ComponentResource classes; needs to refactor resources without destroying them (aliases); is setting up secrets or config; or is configuring a pulumi preview/up CI workflow. Also load for questions about resource dependency order, parent/child resource relationships, or pulumi.interpolate.
---

# Pulumi Best Practices

## When to Use This Skill

Invoke this skill when:

- Writing new Pulumi programs or components
- Reviewing Pulumi code for correctness
- Refactoring existing Pulumi infrastructure
- Debugging resource dependency issues
- Setting up configuration and secrets

## Practices

### 1. Never Create Resources Inside `apply()`

**Why**: Resources created inside `apply()` don't appear in `pulumi preview`, making changes unpredictable. Pulumi cannot properly track dependencies, leading to race conditions and deployment failures.

**Detection signals**:

- `new aws.` or other resource constructors inside `.apply()` callbacks
- Resource creation inside `pulumi.all([...]).apply()`
- Dynamic resource counts determined at runtime inside apply

Related