Critical constraints — read before acting:
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionpulumi-terraform-to-pulumiExecute the skills CLI command in your project's root directory to begin installation:
Fetches pulumi-terraform-to-pulumi from pulumi/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate pulumi-terraform-to-pulumi. Access via /pulumi-terraform-to-pulumi in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
34
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
34
stars
Critical constraints — read before acting:
- Do NOT run
pulumi convert— use the terraform-migrate plugin instead, which preserves state mapping.- Do NOT run
pulumi package add terraform-module— this is for a different workflow.- Do NOT create the Pulumi project under
/workspace— create it inside the checked-out repo.- Replace
${terraform_dir}and${pulumi_dir}below with the actual paths confirmed with the user.
First establish scope and plan the migration by working out with the user:
${terraform_dir})${pulumi_dir})Confirm the plan with the user before proceeding.
Create a new Pulumi project in ${pulumi_dir} in the chosen language. Edit sources to be empty and not declare any
resources. Ensure a Pulumi stack exists.
You must run pulumi_up tool before proceeding to ensure initial stack state is written.
If no local .tfstate file exists in ${terraform_dir}, the state may be in a remote backend (S3, Pulumi Cloud, Terraform Cloud, etc.). Pull it before proceeding:
cd ${terraform_dir} && terraform state pull > terraform.tfstate
This works for all backends, including Pulumi Cloud. If terraform is not available, try tofu state pull instead.
Now produce a draft Pulumi state translation:
pulumi plugin run terraform-migrate -- stack \
--from ${terraform_dir} \
--to ${pulumi_dir} \
--out /tmp/pulumi-state.json \
--plugins /tmp/required-providers.json
Do NOT install the plugin as it will auto-install as needed.
Sometimes terraform-migrate plugin fails because tofu refresh is not authorized. DO NOT skip this step. Work with the
user to find or build a Pulumi ESC environment that provides the necessary credentials so the command can succeed. If setting up an ESC environment is not feasible, inform the user that the migration cannot proceed automatically.
Read the generated /tmp/required-providers.json and install all these Pulumi providers into the new project,
respecting the suggested versions even if they downgrade an already installed provider. The file will contain records
such as [{"name":"aws","version":"7.12.0"}].
Install providers as project dependencies using the language-specific package manager (NOT pulumi plugin install,
which only downloads plugins without adding dependencies):
# TypeScript/JavaScript
npm install @pulumi/[email protected]
# Python
pip install pulumi_aws==7.12.0
# Go
go get github.com/pulumi/pulumi-aws/sdk/[email protected]
# C#
dotnet add package Pulumi.Aws --version 7.12.0
Import the translated state draft (/tmp/pulumi-state.json) into the Pulumi stack:
pulumi stack import --file /tmp/pulumi-state.json
Translate source code to match both the Terraform source and the translated state. Aim for exact match. You can consult
the state draft /tmp/pulumi-state.json for Pulumi resource types and names to use.
Iterate on fixing the source code until pulumi_preview tool confirms that there are no changes to make and the diff
is empty or almost empty. Provider diffs or diffs on tags may be OK.
Offer the user to link an ESC environment to the stack so that each Pulumi stack can seamlessly have access to the provider credentials it needs.
When all looks good, create a Pull Request with the migrated source code.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
pulumi/agent-skills
antonbabenko/terraform-skill
sickn33/antigravity-awesome-skills
davila7/claude-code-templates
wshobson/agents
jeffallan/claude-skills
pulumi-terraform-to-pulumi fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend pulumi-terraform-to-pulumi for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
pulumi-terraform-to-pulumi is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: pulumi-terraform-to-pulumi is focused, and the summary matches what you get after install.
Registry listing for pulumi-terraform-to-pulumi matched our evaluation — installs cleanly and behaves as described in the markdown.
pulumi-terraform-to-pulumi reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for pulumi-terraform-to-pulumi matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: pulumi-terraform-to-pulumi is the kind of skill you can hand to a new teammate without a long onboarding doc.
pulumi-terraform-to-pulumi has been reliable in day-to-day use. Documentation quality is above average for community skills.
pulumi-terraform-to-pulumi reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 46