devops-skills/aws-support-case/SKILL.md
This skill should be used when users need to manage AWS Support cases via CLI. It handles listing cases (recent 2 weeks, unresolved), viewing case details with bilingual display (English-Chinese line by line), creating new cases with auto-detected service/category, replying to cases, and attachment handling. Triggers on requests mentioning "AWS support", "support case", "工单", "support ticket", or AWS technical support inquiries.
npx skillsauth add oldwinter/skills aws-support-caseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Manage AWS Support cases through CLI with intelligent features: auto-detect service/category when creating cases, translate Chinese to English for submissions, and display case communications in bilingual format (English original followed by Chinese translation).
--region us-east-1 (Support API only available in this region)List recent 2 weeks cases:
aws support describe-cases \
--region us-east-1 \
--after-time "$(date -u -v-14d '+%Y-%m-%dT%H:%M:%SZ' 2>/dev/null || date -u -d '14 days ago' '+%Y-%m-%dT%H:%M:%SZ')" \
--include-resolved-cases \
--output json
List unresolved cases only:
aws support describe-cases \
--region us-east-1 \
--no-include-resolved-cases \
--output json
Display format: Present cases in a clear table with columns: Case ID | Subject | Status | Created | Severity
To view a case with communications:
aws support describe-communications \
--region us-east-1 \
--case-id "case-XXXXXXXX" \
--output json
Bilingual Display Format: When displaying case communications, format each message as follows:
---
[Sender] | [Timestamp]
---
> Original English text line 1
> 中文翻译第一行
> Original English text line 2
> 中文翻译第二行
---
Translation guidelines:
> prefix> prefixStep 1: Query available services and categories
aws support describe-services --region us-east-1 --output json
Step 2: Auto-detect service and category
Analyze the user's description (Chinese or English) to identify:
amazon-ec2, "S3存储桶" → amazon-s3)performance, "无法连接" → connectivity, "配额提升" → limits)Step 3: Translate and create
If user provides Chinese description:
aws support create-case \
--region us-east-1 \
--subject "Translated English subject" \
--communication-body "Translated English description with full details" \
--service-code "detected-service" \
--category-code "detected-category" \
--severity-code "low|normal|high|urgent|critical" \
--language "en"
Severity selection guide: | Severity | When to use | |----------|-------------| | low | General questions, non-urgent inquiries | | normal | Production system has minor issues | | high | Production system significantly impaired | | urgent | Production system severely impaired | | critical | Production system down (Enterprise only) |
Step 1: Translate if needed
If user provides Chinese reply, translate to professional English while preserving:
Step 2: Send reply
aws support add-communication-to-case \
--region us-east-1 \
--case-id "case-XXXXXXXX" \
--communication-body "Translated English reply"
Upload attachment:
# First, base64 encode the file
BASE64_DATA=$(base64 -i /path/to/file)
# Add to attachment set
aws support add-attachments-to-set \
--region us-east-1 \
--attachments fileName="filename.ext",data="$BASE64_DATA"
This returns an attachmentSetId to use when replying:
aws support add-communication-to-case \
--region us-east-1 \
--case-id "case-XXXXXXXX" \
--communication-body "Please see the attached file" \
--attachment-set-id "ATTACHMENT_SET_ID"
Download attachment:
aws support describe-attachment \
--region us-east-1 \
--attachment-id "attachment-id"
aws support resolve-case \
--region us-east-1 \
--case-id "case-XXXXXXXX"
| Keywords (CN/EN) | Service Code | |------------------|--------------| | EC2, 实例, 虚拟机 | amazon-ec2 | | S3, 存储桶, 对象存储 | amazon-s3 | | RDS, 数据库, MySQL, PostgreSQL | amazon-rds | | Lambda, 函数, 无服务器 | aws-lambda | | VPC, 网络, 子网, 安全组 | amazon-vpc | | ECS, 容器, Docker | amazon-ecs | | EKS, Kubernetes, K8s | amazon-eks | | CloudFront, CDN, 分发 | amazon-cloudfront | | Route53, DNS, 域名 | amazon-route53 | | IAM, 权限, 角色, 策略 | aws-iam | | 账单, 费用, billing | aws-billing | | 账户, 账号, account | account-management |
| Keywords (CN/EN) | Category Code | |------------------|---------------| | 咨询, 指导, 如何, how to | general-guidance | | 慢, 性能, 延迟, performance, latency | performance | | 连接, 访问, 超时, connect, timeout | connectivity | | 安全, 漏洞, security | security | | 配置, 设置, configuration | configuration | | 限额, 配额, 提升, limit, quota | limits |
Refer to references/aws-support-cli-reference.md for complete CLI command reference and additional options.
devops
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
testing
This skill should be used when users need to query AWS cost and usage details for a specific date. It supports querying costs at service level (e.g., EC2, S3, RDS) and drilling down to usage type level (e.g., instance types, storage classes, data transfer). Triggers on requests mentioning AWS costs, billing, spending, cost breakdown, or fee analysis.
tools
This skill should be used when users need to interact with AWS services via CLI. It covers all AWS services including EC2, ECS, EKS, Lambda, S3, RDS, DynamoDB, VPC, Route53, CloudFront, Bedrock, Support, Billing, and more. Supports querying, creating, modifying, deleting resources, monitoring, debugging, and cost analysis. Triggers on requests mentioning AWS, cloud resources, or specific AWS service names.
development
This skill should be used when the user requests to add a new third-party API service to the AWS billing/quota monitoring system. It handles the complete onboarding process including adapter creation, Lambda deployment, CloudWatch alarms, Dashboard updates, and verification. Triggers on requests mentioning "add service monitoring", "monitor API balance", "setup quota alerts", "add to billing dashboard", or similar service integration requests.