pulumi-cdk-to-pulumi
Load this skill when a user wants to migrate, convert, port, translate, or move an AWS CDK application (including CDK stacks, constructs, or CloudFormation-synthesized templates) to Pulumi. Phrases such as "convert CDK to Pulumi", "migrate CDK app", "port CDK stacks", "replace CDK with Pulumi", "stop using CDK". Do NOT load for general CDK questions, CDK-only help, or CDK vs Pulumi comparisons where no migration is requested.
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 strong skill description with excellent trigger term coverage and completeness, including both positive and negative trigger conditions. The main weakness is that the 'what' portion focuses on synonyms for migration rather than listing distinct concrete actions the skill performs (e.g., generating Pulumi code, mapping constructs, handling state). The explicit exclusion criteria are a notable strength for reducing false positives.
Suggestions
Add specific concrete actions beyond migration synonyms, such as 'generates equivalent Pulumi TypeScript/Python code', 'maps CDK constructs to Pulumi resources', or 'converts CloudFormation templates to Pulumi programs' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (AWS CDK to Pulumi migration) and some actions (migrate, convert, port, translate, move), but doesn't list specific concrete output actions like 'generates Pulumi code', 'maps CDK constructs to Pulumi resources', or 'converts CloudFormation templates'. The actions listed are mostly synonyms for the same thing rather than distinct capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (migrate/convert AWS CDK applications to Pulumi) and 'when' (explicit trigger phrases and a 'Load this skill when...' clause). It also includes explicit negative triggers ('Do NOT load for...'), which adds further clarity on when to use it. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'convert CDK to Pulumi', 'migrate CDK app', 'port CDK stacks', 'replace CDK with Pulumi', 'stop using CDK'. These are realistic phrases users would naturally use, and the description also includes technical terms like 'CDK stacks', 'constructs', 'CloudFormation-synthesized templates'. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — specifically CDK-to-Pulumi migration. The explicit exclusion of general CDK questions, CDK-only help, and CDK vs Pulumi comparisons significantly reduces conflict risk with other potential skills. | 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, well-structured migration skill that provides concrete, actionable guidance for a complex multi-step process. The workflow is clearly sequenced with validation checkpoints, the custom resource and asset handling tables are excellent reference material, and progressive disclosure is well-implemented through companion files. Minor verbosity in the output format section and bundling guidance templates slightly reduces token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and provides domain-specific knowledge Claude wouldn't inherently know (CDK custom resource handlers, asset migration strategies, provider choices). However, some sections are verbose—the output format section repeats information already covered in the workflow, and some explanations could be tightened (e.g., the bundling user message template is quite long). | 2 / 3 |
Actionability | The skill provides fully executable commands (jq queries, AWS CLI commands, bash commands), concrete code examples (TypeScript patterns for aws-native), specific migration strategy tables mapping CDK handlers to Pulumi replacements, and references to companion tools (cdk2pulumi, cdk-importer) with linked documentation. Guidance is copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced with numbered steps (1. Information Gathering → 2. Code Conversion → 3. Resource Import), includes explicit validation checkpoints (section 3.1 requires running `pulumi preview` and verifying zero changes), and has feedback loops (if preview shows changes, investigate and fix until clean). The credential verification step at the start and the requirement to confirm AWS region are good pre-flight checks. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview workflow in the main file while delegating detailed procedures to companion files (cdk-convert.md, cdk-importer.md, cloudformation-id-lookup.md) and external Pulumi documentation URLs. References are one level deep and clearly signaled with descriptive context about what each linked resource covers. | 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.
- Repository
- pulumi/agent-skills
- Commit
3ec9d51
- 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.