CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/cdk-patterns/SKILL.md

The canonical home for this skill is cdk-patterns in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 compact, well-structured skill body with executable CDK guidance and clear sections. It is held just below top marks by a missing import in the example, a lightly over-explained opener, and validation checkpoints that are implicit in the main flow.

Suggestions

Fix the example's missing cdk import (add `import * as cdk from 'aws-cdk-lib'`) so the code is copy-paste runnable.

Trim or remove the 'You are an expert in AWS CDK...' opener to improve token efficiency.

Add an explicit validation checkpoint into the Instructions flow (e.g., run `cdk diff` and confirm before synth/deploy) rather than only mentioning it under Best Practices.

DimensionReasoningScore

Conciseness

The body is mostly lean—bulleted use/don't-use lists, a numbered instruction set, and a focused example with no padding about what CDK is—but the opening 'You are an expert in AWS CDK...' role line is mild over-explanation that could be trimmed.

4 / 5

Actionability

It provides a concrete TypeScript L3-construct example plus specific API guidance (cdk.Tags.of, RemovalPolicy, cdk diff), but the example references cdk.RemovalPolicy without importing cdk, a minor gap keeping it from copy-paste-ready.

4 / 5

Workflow Clarity

The numbered Instructions give a clear design sequence and 'cdk diff before every deploy' supplies a validation checkpoint, though the main flow does not inline validate->fix->retry loops for the deployment step.

4 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections (Use / Do not use / Instructions / Examples / Best Practices / Troubleshooting) with no external references needed, though the inline example is sizeable enough that splitting examples into a reference file would marginally improve it.

4 / 5

Total

16

/

20

Passed

Description

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

A solid, third-person description that clearly states both capability and an explicit trigger, with good natural keyword coverage. It could be raised by adding more concrete verbs and a broader set of trigger phrases including IaC synonyms.

Suggestions

Add more concrete actions to the 'what' clause (e.g., 'scaffold multi-stack apps, wire IAM least-privilege, configure RemovalPolicy and tagging') to lift specificity.

Broaden the 'Use when' trigger with additional natural phrases such as 'AWS infrastructure as code', 'IaC', or 'provisioning AWS resources with CDK'.

Include a disambiguating clause noting it is distinct from raw CloudFormation or Terraform to further reduce conflict risk.

DimensionReasoningScore

Specificity

It names the domain ('AWS CDK patterns and constructs') and a couple of actions ('building cloud infrastructure', 'designing reusable CDK stacks and L3 constructs'), but the verbs stay at an abstract design level rather than enumerating concrete operations, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Both 'what' ('patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java') and 'when' ('Use when designing reusable CDK stacks and L3 constructs') are present and explicit, but the 'when' clause is a single condition rather than the multiple concrete trigger phrases of the top anchor.

4 / 5

Trigger Term Quality

It surfaces natural terms a user would say ('CDK', 'AWS CDK', 'reusable CDK stacks', 'L3 constructs', 'cloud infrastructure') with an explicit 'Use when designing' trigger, though synonyms like 'IaC' or 'infrastructure as code' are absent.

4 / 5

Distinctiveness Conflict Risk

The CDK-specific niche ('L3 constructs', 'CDK stacks') is clearly distinguishable from most skills, with only minor overlap risk against generic AWS or infrastructure-as-code skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.