cdk-patterns

Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 constructs.

Quality

57%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/cdk-patterns/SKILL.md

Quality

Content

57%Scale 1-5

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

This skill provides a solid starting point with a concrete TypeScript example and useful best practices, but it reads more like a general advisory guide than a precise, actionable skill. The instructions are design principles rather than executable steps, the workflow lacks validation checkpoints important for CDK deployments, and the content could be more concise by removing guidance Claude already knows (least privilege, L2 vs L1 preference). Only one of the four claimed patterns is actually demonstrated.

Suggestions

Add an explicit deployment workflow with validation steps: cdk synth → cdk diff → review changes → cdk deploy, with error recovery guidance for failed deployments.

Remove or significantly compress general AWS/CDK advice Claude already knows (least privilege, L2 vs L1 preference, tagging) and focus on project-specific conventions or non-obvious patterns.

Either provide examples for the other claimed patterns (ECS, static sites, data pipelines) in separate referenced files, or narrow the skill's scope to match what's actually covered.

Add Python or Java examples if multi-language support is part of the skill's purpose, or remove the multi-language claim from the description.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections add moderate overhead that Claude could infer. The instructions section contains some general advice (e.g., 'Apply the principle of least privilege') that Claude already knows well. The code example and best practices are reasonably tight, but overall there's room to trim.	3 / 5
Actionability	The TypeScript example is concrete and executable, demonstrating a real L3 construct pattern with proper imports and structure. However, only one example is provided despite claiming multi-language support (Python, Java), and the instructions section is more advisory than step-by-step executable guidance. The best practices are concrete but brief.	4 / 5
Workflow Clarity	The instructions list 6 steps but they read more like design principles than a sequenced workflow. There's no validation checkpoint — notably, 'Use cdk diff before every deploy' is buried in best practices rather than integrated into a deployment workflow with explicit verification steps. For CDK deployments (which can be destructive), the lack of a validate-then-deploy feedback loop is a gap.	3 / 5
Progressive Disclosure	The content is reasonably structured with clear sections (instructions, examples, best practices, troubleshooting), but everything is inlined in a single file. For a skill covering multiple patterns (serverless API, container service, data pipeline, static sites), the additional patterns should be in separate referenced files. No bundle files exist to support this.	3 / 5
	Total	13 / 20 Passed

Description

57%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.

The description identifies a clear domain (AWS CDK) and includes a 'Use when' clause, which is good. However, it lacks concrete actions—it doesn't specify what patterns or constructs it covers (e.g., VPC setups, Lambda deployments, API Gateway configurations). The trigger terms are adequate but miss common synonyms and related terms users might naturally use.

Suggestions

Add specific concrete actions such as 'define VPC configurations, set up Lambda functions, create API Gateway routes, configure S3 buckets' to improve specificity.

Expand trigger terms to include natural synonyms like 'infrastructure as code,' 'IaC,' 'CloudFormation,' 'deploy AWS resources,' and specific AWS service names.

Broaden the 'Use when' clause to cover more scenarios, e.g., 'Use when the user asks about AWS CDK patterns, building cloud infrastructure with CDK, or creating reusable constructs and stacks.'

Dimension	Reasoning	Score
Specificity	Names the domain (AWS CDK) and mentions 'patterns and constructs' and 'reusable CDK stacks and L3 constructs,' but does not list concrete actions like 'create VPC configurations,' 'set up Lambda functions,' or 'define API Gateway routes.' The actions remain generic.	2 / 5
Completeness	It answers 'what' (common AWS CDK patterns and constructs for building cloud infrastructure) and includes a 'when' clause ('Use when designing reusable CDK stacks and L3 constructs'). However, the 'when' is narrow—it only mentions designing reusable stacks and L3 constructs, missing broader triggers like 'when the user asks about CDK best practices' or 'when setting up AWS infrastructure.'	4 / 5
Trigger Term Quality	Includes relevant keywords like 'AWS CDK,' 'cloud infrastructure,' 'TypeScript,' 'Python,' 'Java,' 'CDK stacks,' and 'L3 constructs.' However, it misses common natural phrases users might say such as 'CloudFormation,' 'IaC,' 'infrastructure as code,' 'deploy,' 'provision,' or specific service names like 'S3,' 'Lambda,' 'EC2.'	3 / 5
Distinctiveness Conflict Risk	AWS CDK is a fairly specific domain, and the mention of L3 constructs and specific languages helps distinguish it. There could be minor overlap with general AWS or CloudFormation skills, but the CDK focus is clear enough to reduce most conflict risk.	4 / 5
	Total	13 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/cdk-patterns/SKILL.md
Commit: fbdfd63

Reviewed: about 18 hours 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.