aws-specialist

5 stars 1 forks

AWS cloud specialist for infrastructure as code with CloudFormation/CDK, serverless with Lambda, container orchestration with ECS/Fargate, database management with RDS, storage with S3/CloudFront CDN, and deployment automation. Use when deploying to AWS, optimizing cloud costs, implementing auto-scaling, or requiring AWS-specific best practices. Handles IAM policies, VPC networking, monitoring with CloudWatch, and multi-region deployments.

Marketplace

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 →

Claude Code (CLI) Fast

skilz install DNYoussef/context-cascade/aws-specialist

OpenCode (CLI) Fast

skilz install DNYoussef/context-cascade/aws-specialist --agent opencode

OpenAI Codex (CLI) Native

skilz install DNYoussef/context-cascade/aws-specialist --agent codex

Gemini CLI (Project) Project

skilz install DNYoussef/context-cascade/aws-specialist --agent gemini

First time? Install Skilz: pip install skilz

Works with 14 AI coding assistants

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

View All Agents

For Claude Desktop Easy

Download Agent Skill ZIP

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

Manual Installation

1. Clone the repository:

git clone https://github.com/DNYoussef/context-cascade

2. Copy the agent skill directory:

cp -r context-cascade/skills/operations/cloud-platforms/aws-specialist ~/.claude/skills/

Owner: DNYoussef (GitHub)
Repository: context-cascade
Stars: 5
Forks: 1
Type: Technical
Meta-Domain: cloud infrastructure
Primary Domain: aws
Market Score: 46

Agentic Skill Grades →

Agent Skill Grade

Score: 46/100 Click to see breakdown

Score Breakdown

Spec Compliance

0/15

PDA Architecture

9/30

Ease of Use

20/25

Writing Style

6/10

Utility

16/20

Modifiers: -5

Areas to Improve

Invalid or incomplete frontmatter
Excessive metadata annotations
Name convention violations

Recommendations

Focus on improving Spec Compliance (currently 0/15)
Focus on improving Pda (currently 9/30)
Address 5 high-severity issues first

Graded: 2026-01-19

Developer Feedback

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

Links:

The TL;DR

You're at 46/100, which puts you in F territory. The good news? You've got solid foundations in Ease of Use (20/25) and Utility (16/20), meaning the skill itself is practical and discoverable. The bad news is that Spec Compliance is completely broken at 0/15, and Progressive Disclosure Architecture needs work at 9/30. This is fixable, but there are some structural issues to address.

What's Working Well

Strong metadata game: Your name and description follow conventions well, with clear triggers that tell users exactly when to invoke this skill
Solid example templates: The CDK and ECS deployment code samples are genuinely useful and well-structured
Addresses real AWS pain points: You're tackling actual deployment challenges that developers face, which gives this utility value

The Big One: Missing Frontmatter

Here's the thing—your skill file is missing YAML frontmatter entirely. This isn't optional; it's how the skill system recognizes and activates your skill. Right now, the parser sees nothing.

What you need:

Create a frontmatter block at the very top of your SKILL.md file:

---
name: aws-specialist
description: Provides AWS operations guidance. Use when asked to "aws specialist", "deploy to aws", "aws infrastructure", or "aws help".
---

This alone bumps you from 0/15 to ~5/15 on Spec Compliance. Then update your actual description field in the frontmatter to include all your trigger phrases.

Impact: +5 points immediately.

Other Things Worth Fixing

Strip the metadata annotations - Those [ground:given] [conf:0.95] tags ...

Browse Category

More cloud infrastructure Agentic Skills

Report Security Issue

Found a security vulnerability in this agent skill?