pulumi-terraform-to-pulumi
Migrate Terraform projects to Pulumi. Use when users need to move infrastructure from Terraform to Pulumi, translate HCL configurations, or convert Terraform modules to Pulumi components.
Install with Tessl CLI
npx tessl i github:pulumi/agent-skills --skill pulumi-terraform-to-pulumi97
Does it follow best practices?
Validation for skill structure
Discovery
89%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 a well-crafted skill description with strong completeness and distinctiveness. It clearly identifies the migration use case and includes explicit 'Use when' guidance with relevant trigger terms. The main weakness is that the specific capabilities could be more detailed (e.g., state handling, provider conversion, resource mapping).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Terraform to Pulumi migration) and some actions ('migrate', 'translate HCL configurations', 'convert Terraform modules'), but doesn't list comprehensive specific actions like handling state migration, provider mapping, or resource conversion details. | 2 / 3 |
Completeness | Clearly answers both what ('Migrate Terraform projects to Pulumi') and when ('Use when users need to move infrastructure from Terraform to Pulumi, translate HCL configurations, or convert Terraform modules to Pulumi components') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Terraform', 'Pulumi', 'HCL configurations', 'Terraform modules', 'Pulumi components', 'migrate', 'convert', 'translate'. These cover the main terms someone would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche targeting specifically Terraform-to-Pulumi migration. The combination of both tool names and migration-specific language makes it highly unlikely to conflict with general IaC skills or other migration tools. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%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 clear, actionable guidance for Terraform-to-Pulumi migration. It establishes scope upfront, provides concrete commands for all steps, includes validation checkpoints (pulumi_up before proceeding, iterate until preview is clean), and ends with clear anti-patterns in the IMPORTANT section. The skill respects Claude's intelligence while providing the specific, non-obvious details needed for this complex migration workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence with Terraform and Pulumi. No unnecessary explanations of what these tools are or how they work—it jumps straight into actionable steps. | 3 / 3 |
Actionability | Provides concrete, executable commands for each step including exact CLI syntax, language-specific package manager commands with version pinning, and specific file paths. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Clear sequential workflow with explicit checkpoints: confirm plan with user, ensure initial stack state is written before proceeding, iterate until preview shows no changes, and explicit validation via pulumi_preview. Includes error recovery guidance for terraform-migrate failures. | 3 / 3 |
Progressive Disclosure | Appropriately structured as a single comprehensive guide without unnecessary external references. The content length (~60 lines) is appropriate for inline presentation, and the workflow is logically organized with clear sections. | 3 / 3 |
Total | 12 / 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.
- 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.