cloudformation-to-pulumi
Convert an AWS CloudFormation stack or template to Pulumi. This skill MUST be loaded whenever a user requests migration or conversion of CloudFormation to Pulumi.
Install with Tessl CLI
npx tessl i github:pulumi/agent-skills --skill cloudformation-to-pulumi90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation 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 solid skill description with excellent trigger terms and completeness. The explicit 'when' clause and specific technology names (CloudFormation, Pulumi) make it highly distinctive. The main weakness is that it could be more specific about the concrete actions performed during conversion.
Suggestions
Add specific concrete actions like 'parses CloudFormation YAML/JSON templates, maps AWS resources to Pulumi equivalents, generates TypeScript/Python Pulumi code'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AWS CloudFormation to Pulumi conversion) and the general action (convert/migrate), but doesn't list specific concrete actions like 'parse templates', 'map resources', 'generate Pulumi code', or 'handle nested stacks'. | 2 / 3 |
Completeness | Clearly answers both what ('Convert an AWS CloudFormation stack or template to Pulumi') and when ('whenever a user requests migration or conversion of CloudFormation to Pulumi') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'CloudFormation', 'Pulumi', 'migration', 'conversion', 'stack', 'template'. These are the exact terms users would use when requesting this task. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining CloudFormation and Pulumi - unlikely to conflict with other skills. The combination of these two specific technologies creates a clear, distinct trigger. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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 with excellent actionability and workflow clarity. It provides concrete, executable guidance with proper validation checkpoints for a complex migration process. The main weakness is moderate verbosity - some concepts are repeated multiple times and certain explanations (like intrinsic function mappings) could be more condensed given Claude's existing knowledge.
Suggestions
Consolidate the repeated emphasis on CloudFormation Logical ID naming convention into a single prominent callout rather than restating it in multiple sections
Consider moving the intrinsic functions mapping table to a separate reference file since Claude understands these concepts and can reference them when needed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeating the critical naming convention multiple times, explaining basic concepts like intrinsic functions that Claude likely knows). The content could be tightened while preserving clarity. | 2 / 3 |
Actionability | Provides fully executable code examples, specific CLI commands, clear mapping tables for intrinsic functions, and concrete TypeScript patterns. Every section includes copy-paste ready examples with correct/incorrect comparisons. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with numbered phases, explicit validation checkpoints (pre-import validation, zero-diff preview requirement), and clear feedback loops (if errors, investigate and update until clean). The workflow is sequential and unambiguous. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate references to external files (cfn-importer.md, cloudformation-id-lookup.md) that are one level deep and clearly signaled. Content is organized logically from information gathering through output format. | 3 / 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.
- 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.