aws-deployment

Configures CI/CD pipelines using AWS CodePipeline, CodeBuild, CodeDeploy, CodeConnections, and CodeArtifact. Covers CodePipeline V2 (triggers, variables, execution modes, cross-account), buildspec.yml (caching, VPC, Docker), CodeDeploy strategies (blue/green, canary, linear), CodeArtifact (private package registries, auth tokens, cross-account), and source connections (GitHub, GitLab, Bitbucket). Applies when CodePipeline, CodeBuild, CodeDeploy, CodeConnections, CodeArtifact, buildspec.yml, appspec.yml, or CI/CD pipeline orchestration is referenced. Does NOT cover: ECS Fargate services or task definitions (use aws-containers), CDK Pipelines or cdk deploy (use aws-cdk), sam deploy (use aws-serverless), Amplify deployments (use aws-amplify), or GitHub Actions/GitLab CI.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is aws-deployment in aws/agent-toolkit-for-aws

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured hub skill: dense non-obvious warnings, service-composition map, error→fix tables, and clean one-level-deep disclosure to six verified reference files. The only gaps are that complete executable commands and explicit validation checkpoints live in the references rather than the body.

Suggestions

Include one complete copy-paste-ready example command in the body for the most common workflow (e.g., the full 'aws deploy create-deployment' or pipeline-creation command) so the highest-frequency actions are executable without opening a reference file.

Add explicit verification checkpoints to the Common Workflows entries (e.g., 'Pipeline from GitHub to ECS: create connection → verify connection status is AVAILABLE → ...') so validation is inline, not only in references.

In the Cross-account triple requirement warning, show the minimal KMS key policy or trust-policy snippet (or a one-line pointer to the exact section in codepipeline.md) so users can verify all three requirements concretely.

Dimension	Reasoning	Score
Conciseness	The body is dense and entirely operational — critical warnings like 'Connections created via CLI/CloudFormation remain PENDING indefinitely — MUST complete OAuth in the AWS Console' deliver non-obvious gotchas with zero padding, and nothing explains concepts Claude already knows.	5 / 5
Actionability	Concrete flags and config keys appear throughout (--ignore-application-stop-failures, stop-deployment --auto-rollback-enabled, privilegedMode: true, file_exists_behavior: OVERWRITE, type: SECRETS_MANAGER), but the body contains no complete copy-paste-ready commands — full CLI commands are deferred to references, leaving minor gaps.	4 / 5
Workflow Clarity	The Common Workflows table gives sequenced chains ('Create connection → CodeBuild Docker stage → CodeDeploy ECS blue/green') and the troubleshooting table provides error→cause→fix recovery loops, but explicit validation checkpoints within workflows are mostly delegated to the reference files rather than stated inline.	4 / 5
Progressive Disclosure	A ~90-line overview with a Quick Navigation table mapping each intent to a real one-level-deep reference file; all six referenced files exist, are substantive (116–351 lines), and contain no nested references, matching the well-signaled clear-overview anchor.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: it states concrete capabilities per service, provides an explicit trigger clause with file-name and synonym terms, and disambiguates against five sibling skills with an explicit not-covered list. It is detailed but not padded — every clause is load-bearing.

Dimension	Reasoning	Score
Specificity	Enumerates concrete capabilities per service — 'CodePipeline V2 (triggers, variables, execution modes, cross-account)', 'buildspec.yml (caching, VPC, Docker)', 'blue/green, canary, linear', 'private package registries, auth tokens, cross-account' — giving comprehensive, non-generic coverage of the domain's actions.	5 / 5
Completeness	Explicitly answers both 'what' (two capability sentences naming all five services and their sub-features) and 'when' ('Applies when CodePipeline, CodeBuild, ... or CI/CD pipeline orchestration is referenced') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'Applies when' clause covers natural trigger terms including file-name triggers (buildspec.yml, appspec.yml) and the synonym pair 'CI/CD pipeline orchestration', matching the comprehensive anchor's 'synonyms and file extensions' standard.	5 / 5
Distinctiveness Conflict Risk	A 'Does NOT cover' clause explicitly redirects overlapping topics to sibling skills (aws-containers, aws-cdk, aws-serverless, aws-amplify) and excludes GitHub Actions/GitLab CI, giving a clear niche with minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: aws/agent-toolkit-for-aws
Path: plugins/aws-core/skills/aws-deployment/SKILL.md
Commit: b8171ad

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.