BB AWS | Amazon Web Services
Architects, debugs, secures, and cost-optimizes AWS infrastructure — EC2, Lambda, RDS, VPC, IAM, ECS, CloudFront. Use when deploying or reviewing anything on AWS, when a bill jumps or spend has to come down, when an AccessDenied, throttle, timeout, 502/503/504, or unreachable-database error has no obvious cause, when choosing between Lambda, Fargate, EC2, RDS, DynamoDB, SQS, or EventBridge, when hardening IAM policies, S3 exposure, security groups, or secrets, when writing Terraform/CloudFormation/CDK against AWS, when auditing an account you inherited, or when a service quota, cold start, connection limit, or failover is the thing that broke. Covers VPC and subnet design, NAT versus VPC endpoints, Organizations and cross-account roles, backups and disaster recovery, and CLI/SSO profiles. Not for object-storage patterns in depth (`s3`), DynamoDB key modeling (`dynamodb`), Kubernetes manifest authoring (`k8s`), or Terraform language mechanics (`terraform`).
Architects, debugs, secures, and cost-optimizes AWS infrastructure — EC2, Lambda, RDS, VPC, IAM, ECS, CloudFront.
As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, consistency, running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-offensive-securityiam.md:5Offensive-security / dual-use content (legitimate for authorised testing; review intended use)**Contents:** [Evaluation Order (memorize this, it ends most arguments)](#evaluation-order-memorize-this-it-ends-most-arguments) · [Diagnosing a Denial](#diagnosing-a-denial) · [Trust Policy vs Permis
-
low Risky intent
intent-offensive-securityiam.md:44Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## iam:PassRole — The Privilege Escalation Nobody Reviews
Files scanned: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
body-longSKILL.md body ≈ 6396 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 23 mutating operations with no state check
- 40Consistency. Frontmatter name (AWS | Amazon Web Services) differs from the folder (aws)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 6396 tokens
- 100Steps. 37 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
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
- +3Description length 970: 120–800 characters recommended
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 15 headings
- +3Step-by-step instructions: 37 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.