processing-s3-uploads-with-step-functions

Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size. Uses EventBridge to trigger a Step Functions state machine when objects are uploaded to S3. Small files are processed by Lambda, large files by a Fargate task. Includes VPC, ECR repository, ECS cluster, and scoped IAM roles. Trigger keywords: Step Functions, Fargate, Lambda, S3 event, EventBridge, ECS, ECR, file processing, workflow orchestration, serverless.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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, highly executable deployment skill with a clear validated workflow and appropriate use of reference files to keep the main body navigable. The only weakness is repetition of a few command blocks and MUST-process boilerplate that slightly inflates the token budget.

Suggestions

De-duplicate the security-group egress and S3 encryption command blocks that appear in both the procedure steps and the Security Considerations section by cross-referencing one from the other.

Tighten the repeated 'You MUST explain to the customer...' process boilerplate into a single upfront constraint rather than restating it per step.

Move the duplicated DLQ/CloudWatch-alarm setup guidance into a single location and reference it from the other, since the same commands appear in Step 12 and Security Considerations.

Dimension	Reasoning	Score
Conciseness	The body is dense and largely actionable with concrete CLI commands, but repeats several command blocks verbatim across Step 2 and the Security Considerations section (security-group egress, bucket encryption) and carries MUST-boilerplate that could be tightened, matching the efficient-with-minor-trim anchor.	4 / 5
Actionability	Provides copy-paste-ready AWS CLI commands with placeholders, a concrete Lambda packaging one-liner, and a sed substitution block; only Steps 5 and 8 delegate to existing reference files, fitting the fully-executable anchor.	5 / 5
Workflow Clarity	Presents a clearly sequenced Step 0–13 workflow with explicit validation checkpoints (dependency check, credential abort, function verification, a dedicated Validate step with a test upload and execution check) and a troubleshooting section for error recovery.	5 / 5
Progressive Disclosure	SKILL.md serves as an overview that clearly signals one-level-deep references to references/iam-roles.md and references/ecs-task-definition.md (both verified present), with bulky IAM/ECS detail appropriately split out and scripts kept separate.	5 / 5
	Total	19 / 20 Passed

Description

91%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.

A strong, specific description that names concrete actions, components, and a comprehensive trigger-keyword set. Its only gap is relying on a keyword list rather than an explicit scenario-based 'Use when...' clause, which leaves completeness just short of a perfect score.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions and architectural components ('routes S3 uploads to either Lambda or Fargate via Step Functions based on file size', 'Uses EventBridge to trigger a Step Functions state machine', 'Includes VPC, ECR repository, ECS cluster, and scoped IAM roles'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Clearly states the 'what' and provides explicit trigger guidance via the 'Trigger keywords:' clause, but lacks a scenario-based 'Use when...' formulation, so the 'when' is concrete but less fully spelled out than the score-5 anchor.	4 / 5
Trigger Term Quality	Provides an exhaustive keyword list ('Step Functions, Fargate, Lambda, S3 event, EventBridge, ECS, ECR, file processing, workflow orchestration, serverless') covering the natural service terms users would say.	5 / 5
Distinctiveness Conflict Risk	Describes a specific niche (file-size-based S3 routing through Step Functions to Lambda/Fargate) with distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: aws/agent-toolkit-for-aws
Path: skills/specialized-skills/serverless-skills/processing-s3-uploads-with-step-functions/SKILL.md
Commit: d6ad2e4

Reviewed: about 3 hours 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.