pulumi-cdk-to-pulumi
Convert an AWS CDK application to Pulumi. This skill MUST be loaded whenever a user requests migration or conversion of a CDK application to Pulumi.
Install with Tessl CLI
npx tessl i github:pulumi/agent-skills --skill pulumi-cdk-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 'MUST be loaded whenever' clause provides clear activation guidance. The main weakness is the lack of specific concrete actions beyond the high-level 'convert' - it could benefit from listing specific conversion tasks.
Suggestions
Add specific concrete actions like 'translates CDK constructs to Pulumi resources, converts stack configurations, maps CDK patterns to Pulumi equivalents'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AWS CDK to Pulumi conversion) and the general action (convert/migrate), but lacks specific concrete actions like 'translate constructs', 'map resource definitions', or 'convert stack configurations'. | 2 / 3 |
Completeness | Clearly answers both what ('Convert an AWS CDK application to Pulumi') and when ('whenever a user requests migration or conversion of a CDK application to Pulumi') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'CDK', 'Pulumi', 'migration', 'conversion', 'CDK application'. These are the exact terms a user would use when requesting this task. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining AWS CDK 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 throughout the migration process. The progressive disclosure is well-implemented with appropriate references to supporting documentation. Minor verbosity in some sections prevents a perfect conciseness score.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeated mentions of validation, multiple references to the same documentation). The tables and structured content are efficient, but some sections could be tightened without losing clarity. | 2 / 3 |
Actionability | Provides fully executable commands (bash, jq queries, TypeScript examples), specific tool references (cdk2pulumi, cdk-importer), and concrete migration strategies with copy-paste ready code snippets and exact command syntax. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with numbered phases, explicit validation checkpoints (verify credentials, run preview after import, ensure no changes), clear sequencing, and feedback loops for error recovery (investigate and update until no changes). | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview sections, appropriately references external files (cdk-convert.md, cdk-importer.md, cloudformation-id-lookup.md) at one level deep, and provides external documentation links for advanced/deviation scenarios. | 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.