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 terms, clear activation criteria, and explicit negative boundaries that reduce conflict risk. Its main weakness is that the 'what it does' portion focuses on synonyms for migration rather than listing distinct concrete capabilities (e.g., code generation, construct mapping, template conversion). The description also uses appropriate imperative/third-person framing rather than first or second person.
Suggestions
Add specific concrete actions beyond migration synonyms, e.g., 'Generates equivalent Pulumi code, maps CDK constructs to Pulumi resources, 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 TypeScript/Python code', 'converts CloudFormation templates', or 'maps CDK constructs to Pulumi resources'. 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 plus negative boundaries for when NOT to load). The 'Load this skill when...' clause and the 'Do NOT load for...' exclusions make the activation criteria very explicit. | 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 | Highly distinctive with a very specific niche (CDK-to-Pulumi migration). The explicit exclusion of general CDK questions, CDK-only help, and comparison scenarios further reduces conflict risk with other potential skills covering CDK or Pulumi independently. | 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, comprehensive migration skill that provides a clear end-to-end workflow with concrete commands, validation checkpoints, and well-organized progressive disclosure. The actionability is excellent with executable examples, lookup tables, and specific tool references. Minor verbosity in some sections (bundling options template, output format specification) prevents a perfect conciseness score, but the complexity of CDK-to-Pulumi migration largely justifies the length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly efficient and avoids explaining basic concepts Claude already knows, but some sections are verbose—particularly the bundling user message template, the full output format specification, and the custom resources table could be tighter. The overall length is justified by the complexity of the migration task, but there's room to trim. | 2 / 3 |
Actionability | The skill provides concrete, executable bash commands (jq queries, aws CLI, pulumi config), specific TypeScript code examples with correct/incorrect patterns, detailed lookup tables for custom resource handlers, and references to companion tool documentation. Guidance is copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (Information Gathering → Code Conversion → Resource Import) with numbered sub-steps. Validation checkpoints are explicit—step 3.1 requires running `pulumi preview` and specifies the exact success criteria (no updates, replaces, creates, or deletes), with a feedback loop to fix issues. The critical success requirements at the top set clear acceptance criteria. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to companion files (cdk-convert.md, cdk-importer.md, cloudformation-id-lookup.md) and external Pulumi documentation URLs. Detailed conversion logic is appropriately delegated to these references while the main skill retains the workflow and decision-making guidance. | 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
b6214ca
- 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.