Skillzwave Logo
Skillzwave

mastering-aws-cdk

91
A

Guides AWS CDK v2 infrastructure-as-code development in TypeScript with patterns, troubleshooting, and deployment workflows. Use when creating or refactoring CDK stacks, debugging CloudFormation or CDK deploy errors, setting up CI/CD with GitHub Actions OIDC, or integrating AWS services (Lambda, API Gateway, ECS/Fargate, S3, DynamoDB, EventBridge, Aurora, MSK).

CommandsAgentsMarketplace
#references#GitHub Actions#codex#Guides AWS#agentic-skills#Mastering AWS#CDK#agentic-skill

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install SpillwaveSolutions/mastering-aws-cdk-plugin/mastering-aws-cdk
skilz install SpillwaveSolutions/mastering-aws-cdk-plugin/mastering-aws-cdk --agent opencode
skilz install SpillwaveSolutions/mastering-aws-cdk-plugin/mastering-aws-cdk --agent codex
skilz install SpillwaveSolutions/mastering-aws-cdk-plugin/mastering-aws-cdk --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/SpillwaveSolutions/mastering-aws-cdk-plugin
2. Copy the agent skill directory:
cp -r mastering-aws-cdk-plugin/skills/mastering-aws-cdk ~/.claude/skills/
View on GitHub

Need detailed installation help? Check our platform-specific guides:

Claude Desktop Guide Claude Code Guide Troubleshooting

Related Agentic Skills

automating-mail

by SpillwaveSolutions

Automates Apple Mail via JXA with AppleScript dictionary discovery. Use when asked to "automate email", "send mail via script", "JXA Mail automatio...

100
Marketplace

automating-reminders

by SpillwaveSolutions

Automates Apple Reminders using JavaScript for Automation (JXA). Use when asked to "create reminders programmatically", "automate reminder lists", ...

100
Marketplace

mastering-postgresql

by SpillwaveSolutions

PostgreSQL development for Python with full-text search (tsvector, tsquery, BM25 via pg_search), vector similarity (pgvector with HNSW/IVFFlat), JS...

100
Marketplace

automating-contacts

by SpillwaveSolutions

Automates macOS Contacts via JXA with AppleScript dictionary discovery. Use when asked to "automate contacts", "JXA contacts automation", "macOS ad...

99
Marketplace

Agentic Skill Details

Owner
SpillwaveSolutions (GitHub)
Repository
mastering-aws-cdk-plugin
Type
Other
Meta-Domain
Primary Domain
Market Score
91
Agentic Skill Grades →

Agent Skill Grade

A
Score: 91/100 Click to see breakdown

Score Breakdown

Spec Compliance
12/15
PDA Architecture
27/30
Ease of Use
22/25
Writing Style
9/10
Utility
18/20
Modifiers: +3

Areas to Improve

  • Minor redundancy in best practices
  • Workflow section could use explicit step numbers
  • Missing explicit version info in metadata

Recommendations

  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-19

Developer Feedback

I took a look at your mastering-aws-cdk skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 91/100, solid A territory. This is based on Anthropic's skill best practices rubric. Your strongest area is the architecture—the way you've structured the skill (main SKILL.md at ~130 lines delegating to 7 reference files) is exactly how Progressive Disclosure should work. Weakest area is Spec Compliance (12/15), mostly because you're only hitting 1-2 trigger phrases when you could expand that.

What's Working Well

  • Architecture is chef's kiss. You've nailed the layered structure—SKILL.md stays focused and delegates deep content to reference files. No nested rabbit holes. This is how token economy gets done right.
  • Actual troubleshooting teeth. The debugging checklist with copy-pasteable checkboxes is the kind of thing that saves people 30 minutes at 2am. That's real utility.
  • Service patterns are thorough. Lambda, DynamoDB, API Gateway sections cover the pain points people actually hit—not generic AWS docs regurgitation. The OIDC setup specifically? That's niche enough that it matters.
  • Consistent terminology throughout. L1/L2/L3 constructs, synth/diff/deploy workflow—you're not mixing metaphors. Developers can search and find stuff.

The Big One: Beef Up Your Trigger Phrases

Right now you've got maybe 1-2 trigger phrases in the description ("cdk deploy", "cdk synth"). You're leaving discoverability on the table. Expand that description to cover actual queries people type:

Current: "AWS CDK production patterns and best practices"

Better: "AWS CDK L2 constructs, production deployment patterns, OIDC federation, cdk-nag security scanning, troubleshooting CDK erro...

AI-Detected Topics

Extracted using NLP analysis

references GitHub Actions codex Guides AWS agentic-skills Mastering AWS CDK agentic-skill gemini opencode

Report Security Issue

Found a security vulnerability in this agent skill?