Skills cdk-patterns
📦
cdk-patterns
Content revision r1 Safe ⚡ Contains scripts⚙️ External commands
Build Reusable AWS CDK Patterns
Reusable cloud infrastructure is hard to standardize across teams. This skill guides AWS CDK patterns, L2 constructs, IAM, monitoring, tagging, and stack boundaries.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "cdk-patterns" from https://skillstore.io/skills/sickn33-cdk-patterns.md and its manifest at https://skillstore.io/api/skills/sickn33-cdk-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "cdk-patterns". Design a reusable serverless API pattern for AWS CDK.
Expected outcome:
- The skill would recommend separate data and service stacks.
- It would include API Gateway, Lambda, DynamoDB, tracing, alarms, tagging, and least privilege permissions.
- It would call out deployment checks such as synthesizing and reviewing the infrastructure diff.
Using "cdk-patterns". Review my CDK construct for production readiness.
Expected outcome:
- The skill would flag overly broad IAM permissions, missing tags, missing monitoring, and weak removal policies.
- It would suggest L2 constructs where they provide safer defaults.
- It would recommend clearer boundaries between persistent resources and deployable service resources.
Using "cdk-patterns". Plan shared CDK patterns for a platform team.
Expected outcome:
- The skill would identify reusable constructs for common service types.
- It would suggest consistent tagging, observability, and account or region configuration practices.
- It would describe how teams can adapt the patterns without duplicating infrastructure logic.
Security Audit
Safev4 • 7/6/2026 Open versioned report
All static findings are false positives caused by markdown code fences, inline code formatting, or AWS CDK class names in SKILL.md. No prompt injection, data exfiltration intent, or unsafe execution instruction was found in the reviewed file.
1
Files scanned
80
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚡ Contains scripts (1)
⚙️ External commands (6)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-cdk-patterns/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-cdk-patterns?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-cdk-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-cdk-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-cdk-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). cdk-patterns security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-cdk-patterns/audits/4BibTeX citation
@techreport{sickn33-sickn33-cdk-patterns-2026,
author = {sickn33},
title = {cdk-patterns security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-cdk-patterns/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "cdk-patterns security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sickn33-cdk-patterns/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-cdk-patterns:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance
What You Can Build
Standardize Service Infrastructure
Create repeatable CDK patterns for APIs, compute, storage, and shared resources.
Review CDK Stack Quality
Check construct choices, IAM scope, stack boundaries, tagging, monitoring, and deployment readiness.
Design Production Serverless Apps
Plan API Gateway, Lambda, DynamoDB, tracing, alarms, and retention settings as one reusable pattern.
Try These Prompts
Choose a CDK Pattern
I need to build an AWS service with CDK. Ask me the key questions, then recommend a reusable pattern and stack structure.
Design a Serverless API
Design a reusable CDK serverless API pattern with API Gateway, Lambda, DynamoDB, tracing, alarms, tags, and least privilege IAM.
Review an Existing Stack
Review this CDK stack for L1 construct use, IAM scope, removal policies, tags, monitoring, and stateful versus stateless separation.
Create a Multi-Stack Architecture
Propose a multi-stack CDK architecture for a production application with shared stateful resources, stateless services, observability, and deployment guardrails.
Best Practices
- Prefer L2 constructs because they usually provide clearer interfaces and safer defaults.
- Separate persistent resources from stateless service resources to reduce deployment risk.
- Review generated infrastructure changes before deployment and apply least privilege permissions.
Avoid
- Using low-level constructs when maintained L2 constructs meet the requirement.
- Combining databases, queues, compute, and APIs into one tightly coupled stack.
- Hardcoding accounts, regions, names, or broad IAM permissions in reusable constructs.
Frequently Asked Questions
What does this skill help build?
It helps design reusable AWS CDK patterns, stacks, and constructs for common cloud infrastructure needs.
Which CDK languages does it mention?
The skill description mentions TypeScript, Python, and Java.
Does it support Terraform?
No. The skill states that Terraform-specific tasks are outside its scope.
Can it review existing CDK code?
Yes. It can guide reviews for CDK best practices, anti-patterns, IAM scope, monitoring, and stack structure.
Does it deploy infrastructure automatically?
No. It provides design and review guidance. Users should run their normal synthesis, diff, testing, and deployment workflow.
Is it suitable for production systems?
It includes production-oriented guidance such as least privilege IAM, monitoring, tracing, tags, and removal policies.