Labsco
Labsco/Repos/zxkane/aws-skills
REPO PACKAGE

zxkane aws-skills

COMMUNITY
zxkane · publisher327 repository starsMIT · Freegithub.com/zxkane/aws-skills
6skills
0ready to use

The six split as: aws-mcp-setup (the shared dependency, configuring AWS Documentation MCP access for the others), aws-cdk-development and aws-sst-development (two competing infrastructure-as-code paths, CDK or SST/Ion, each one telling an agent explicitly not to use the other's approach), aws-cost-operations (billing estimates, CloudWatch alarms, CloudTrail audits), aws-serverless-eda (Lambda, API Gateway, Step Functions, EventBridge patterns), and aws-agentic-ai (deploying and monitoring agents on Bedrock AgentCore's Gateway, Runtime, Memory, and Identity services). All six are mcp_service in our dependency check — none is a self-contained guide the way a pure-text skill would be.

This is for a team already building on AWS through Claude Code who wants per-domain expertise wired to the matching MCP servers — AWS Pricing, Cost Explorer, CloudWatch, the CDK MCP, Bedrock AgentCore's own services — rather than a general AWS reference. The README is explicit that aws-common (aws-mcp-setup) installs first as a dependency of the other plugins; skipping that order isn't documented as an option.

READ THE FULL ANALYSIS

The MCP server names are truncated to fit inside Bedrock's tool-name limit. The README's own naming scheme, mcp__plugin_{plugin}_{server}__{tool} with short IDs like cw for CloudWatch and sfn for Step Functions, exists because Bedrock caps a tool name at 64 characters — one sign of how many separate servers zxkane/aws-skills is wiring together under one set of plugins.

327Stars on the GitHub repository, at last check.