CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, highly actionable migration runbook with copy-paste commands, explicit validation checkpoints, and a feedback loop — it assumes Claude's competence and avoids concept padding. Structure is solid; the only opportunity is optionally externalizing the per-language provider-install specifics.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanation of what Terraform/HCL/Pulumi are), but a few prose asides like 'This works for all backends, including Pulumi Cloud' could be trimmed.

4 / 5

Actionability

Fully executable commands throughout — `terraform state pull`, the full `pulumi plugin run terraform-migrate` invocation, and copy-paste provider-install commands covering TypeScript/Python/Go/C#, with explicit placeholder-substitution guidance.

5 / 5

Workflow Clarity

A clearly sequenced migration workflow with explicit validation checkpoints ('Confirm the plan with the user before proceeding', 'You must run pulumi_up tool before proceeding') and a feedback loop ('Iterate... until pulumi_preview tool confirms that there are no changes').

5 / 5

Progressive Disclosure

Well-organized self-contained workflow with a clear critical-constraints blockquote and logical step ordering; no external references are needed, though the multi-language provider-install block could optionally live in a reference file.

4 / 5

Total

18

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person, concrete, and clearly scoped with explicit trigger phrases and a negative boundary that sharply reduces conflict risk. The only gaps are slightly limited action breadth and the absence of file-extension triggers.

DimensionReasoningScore

Specificity

Names the domain and concrete actions — 'translating HCL source code' and 'importing Terraform state into a Pulumi stack' — but these are the two core actions rather than a broader list, leaving minor coverage gaps relative to the anchor-5 example.

4 / 5

Completeness

Explicitly states what it does ('Migrate Terraform/OpenTofu projects to Pulumi, including translating HCL... and/or importing Terraform state') and when to trigger ('Use when a user wants to convert...'), plus a concrete do-not-trigger boundary.

5 / 5

Trigger Term Quality

Strong natural triggers users would say ('convert Terraform to Pulumi', 'migrate from HCL', 'import tfstate') with synonyms (Terraform/OpenTofu, HCL, tfstate), but file extensions like .tf or .tfstate are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Terraform-to-Pulumi migration) with distinct triggers and an explicit 'Do NOT trigger for general Terraform-vs-Pulumi comparisons' boundary, minimizing conflict risk.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
pulumi/agent-skills
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.