pulumi-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.
97
96%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope, includes rich natural trigger terms, and explicitly states both when to use and when NOT to use the skill. The inclusion of specific actions (translating HCL, importing tfstate) and the negative trigger boundary make this highly effective for skill selection among a large pool of skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'translating HCL source code' and 'importing Terraform state into a Pulumi stack'. Also specifies the domain clearly as Terraform/OpenTofu to Pulumi migration. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate Terraform/OpenTofu projects to Pulumi, translate HCL, import state) and 'when' (explicit 'Use when...' clause with trigger scenarios). Additionally includes a 'Do NOT trigger' clause that further clarifies boundaries, which is excellent. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Terraform', 'OpenTofu', 'Pulumi', 'HCL', 'convert Terraform to Pulumi', 'migrate from HCL', 'import tfstate', 'Terraform state'. These are all terms a user would naturally use when requesting this kind of migration. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (Terraform-to-Pulumi migration specifically). The explicit 'Do NOT trigger' clause for general comparisons or side-by-side usage questions further reduces conflict risk with other IaC-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides a clear, actionable migration workflow from Terraform to Pulumi. The critical constraints box at the top prevents common mistakes, the commands are concrete and executable, and the workflow includes proper validation checkpoints (initial pulumi_up, iterative pulumi_preview). Minor improvement could come from splitting language-specific installation examples into a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose—critical constraints, scoping, and step-by-step commands. There's no explanation of what Terraform or Pulumi are, no unnecessary background. The constraints box at the top is essential and well-justified. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready commands for each step including the terraform-migrate plugin invocation, state pull, provider installation across four languages, and stack import. Specific file paths and tool names are given throughout. | 3 / 3 |
Workflow Clarity | The multi-step migration process is clearly sequenced: scope → create project → initial pulumi_up → pull state → run terraform-migrate → install providers → import state → translate source → iterate with pulumi_preview → PR. Includes explicit validation checkpoints (pulumi_up before proceeding, pulumi_preview iteration loop until diff is empty) and error recovery guidance (ESC environment for auth failures). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical flow, but it's a single monolithic file. The provider installation examples for four languages could be referenced from a separate file. For a skill of this complexity, some content splitting would improve navigation, though the current length is manageable. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- pulumi/agent-skills
- Commit
b6214ca
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.