BF 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.
Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size.
As a process F 56/100 · Will not run — References files that are not bundled: scripts/Dockerfile, scripts/fargate_processor.py, references/iam-roles.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/Dockerfile - warning
missing-refreference to a missing file: scripts/fargate_processor.py - warning
missing-refreference to a missing file: references/iam-roles.md - warning
missing-refreference to a missing file: scripts/lambda_function.py - warning
missing-refreference to a missing file: references/ecs-task-definition.md - warning
missing-refreference to a missing file: scripts/statemachine.asl.json
Process rating: all ten parameters 56/100
- 0Tools and files. 6 referenced file(s) missing: scripts/Dockerfile, scripts/fargate_processor.py, references/iam-roles.md
- 0Result and completion. Does not say what the result is
- 30Running it twice. 40 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 100 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3819 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 483: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 100 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.