pulumi-arm-to-pulumi
Convert or migrate Azure ARM (Azure Resource Manager) templates, Bicep templates, or code to Pulumi, including importing existing Azure resources. This skill MUST be loaded whenever a user requests migration, conversion, or import of ARM templates, Bicep templates, ARM code, Bicep code, or Azure resources to Pulumi.
72
88%
Does it follow best practices?
Impact
—
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 a strong skill description that clearly defines its scope (ARM/Bicep to Pulumi conversion and Azure resource import), includes comprehensive trigger terms covering natural user language variations, and explicitly states when it should be activated. The only minor note is the use of 'MUST be loaded' which is slightly prescriptive but still effective as trigger guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Convert or migrate Azure ARM templates, Bicep templates, or code to Pulumi' and 'importing existing Azure resources'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (convert/migrate ARM/Bicep templates to Pulumi, import Azure resources) and 'when' ('MUST be loaded whenever a user requests migration, conversion, or import of ARM templates, Bicep templates, ARM code, Bicep code, or Azure resources to Pulumi'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'ARM templates', 'Bicep templates', 'Azure Resource Manager', 'ARM code', 'Bicep code', 'Azure resources', 'Pulumi', 'migration', 'conversion', 'import'. These are all terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: the combination of ARM/Bicep-to-Pulumi conversion is highly specific and unlikely to conflict with other skills. The trigger terms are narrowly scoped to this particular migration path. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured migration skill with strong workflow clarity and actionability. The numbered workflow with explicit validation checkpoints and zero-diff requirements demonstrates mature process design. The main weaknesses are moderate verbosity (explaining things Claude already knows like language options) and the inability to verify referenced bundle files, though the progressive disclosure pattern is sound in design.
Suggestions
Remove the language support enumeration in section 2 — Claude knows Pulumi's supported languages. Replace with a single line like 'Choose language based on user preference or existing codebase.'
Trim the OUTPUT FORMAT section by converting it to a compact checklist rather than a detailed numbered list with sub-bullets, as Claude can infer appropriate formatting from a concise template.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity, such as the language support list (Claude knows what languages Pulumi supports), the explanation of ARM template structure concepts, and the repeated summaries of what referenced files contain. The OUTPUT FORMAT section is quite lengthy and could be more concise. | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout — Azure CLI queries with specific flags, jq commands for template analysis, pulumi config set examples, and clear validation commands. The guidance is specific and copy-paste ready for each step of the workflow. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (1→2→3→4→5) with explicit validation checkpoints including zero-diff validation requirements, preview resolution feedback loops, and clear criteria for success. The 'CRITICAL SUCCESS REQUIREMENTS' section establishes clear validation gates, and the import workflow includes explicit error recovery via the Preview Resolution Workflow. | 3 / 3 |
Progressive Disclosure | The skill references arm-import.md and arm-conversion-patterns.md with clear descriptions of what each contains, and references the pulumi-esc skill appropriately. However, no bundle files were provided to verify these references exist, and the main SKILL.md itself is quite long with the full OUTPUT FORMAT section and detailed inline content that could potentially be split out. The inline summaries of what referenced files contain is a nice touch but adds to length. | 2 / 3 |
Total | 10 / 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
f810e50
- 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.