aws-cdk

Authors, deploys, and troubleshoots AWS infrastructure using CDK with TypeScript or Python. Covers best practices, stack architecture, and construct patterns. Always use when writing CDK constructs, bootstrapping environments, running cdk deploy/synth/diff, fixing CDK or CloudFormation errors, planning stack structure, importing existing resources, resolving drift, or refactoring stacks without resource replacement.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, command-oriented body that assumes Claude's competence and offloads detail to a well-structured set of one-level-deep reference files. The only gap is that feedback loops for destructive operations are implied via the troubleshooting table rather than made explicit.

Suggestions

For destructive operations (cdk rollback --orphan, removalPolicy: DESTROY + autoDeleteObjects, cdk refactor), add an explicit validate→fix→retry loop, e.g. 'cdk diff → review replacements → deploy → verify resource still exists'.

Add an explicit post-action verification step after destructive commands (e.g., confirm the orphaned resource state with aws cloudformation describe-stack-resources after cdk rollback --orphan).

Promote the error→diagnose→fix pattern in the Troubleshooting table into a short stated loop ('diagnose → fix root cause → re-deploy → confirm resolved') so the feedback loop is explicit rather than inferred.

Dimension	Reasoning	Score
Conciseness	Lean and command-dense throughout — tables pack a quick command plus a reference link, Critical Warnings give terse cause→fix with exact commands, and no space is spent explaining what CDK or CloudFormation is. Every token earns its place.	5 / 5
Actionability	Copy-paste-ready commands and code abound: 'cdk bootstrap aws://$ACCOUNT/$REGION', 'cdk synth --strict → cdk diff → cdk deploy', 'cdk rollback $STACK --orphan <LogicalId>', and 'CrossStackReferences.of($RESOURCE).produce(ReferenceStrength.BOTH)'. The troubleshooting table gives a concrete fix command per error.	5 / 5
Workflow Clarity	Sequenced workflows with validation checkpoints are present ('cdk synth --strict → cdk diff → cdk deploy', 'Always diff before deploy to prod', drift '--fail in CI'), and the deadly-embrace fix is a three-deploy sequence — but feedback loops for destructive ops (rollback --orphan, autoDeleteObjects) are implied via the troubleshooting table rather than stated as explicit validate→fix→retry loops, and a few destructive commands lack an explicit post-action verify step.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-organized sections (Overview, Critical Warnings, Common Workflows, Troubleshooting, Construct Patterns, Security), and detail is offloaded one level deep to 9 real, clearly-signaled reference files — all referenced paths verified to exist in references/.	5 / 5
	Total	19 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: third-person, concise yet comprehensive, with concrete actions and an explicit 'Always use when...' trigger clause covering the full range of CDK tasks. It clearly distinguishes itself from neighboring IaC tools.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Authors, deploys, and troubleshoots', 'writing CDK constructs, bootstrapping environments, running cdk deploy/synth/diff, fixing CDK or CloudFormation errors, planning stack structure, importing existing resources, resolving drift, or refactoring stacks without resource replacement' — with comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers both 'what' ('Authors, deploys, and troubleshoots AWS infrastructure using CDK with TypeScript or Python') and 'when' ('Always use when writing CDK constructs, bootstrapping environments, running cdk deploy/synth/diff, ...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger terms match what users say, including the actual CLI subcommands 'cdk deploy/synth/diff', plus 'bootstrapping', 'CloudFormation errors', 'drift', 'importing existing resources', and 'refactoring stacks' — comprehensive coverage with synonyms.	5 / 5
Distinctiveness Conflict Risk	Niche is clearly scoped to AWS CDK with TypeScript or Python, naming the specific framework and languages; minimal overlap risk with adjacent IaC skills. Voice is third person ('Authors, deploys, and troubleshoots'), so no specificity penalty applies.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: aws/agent-toolkit-for-aws
Path: skills/core-skills/aws-cdk/SKILL.md
Commit: d6ad2e4

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.