SKILLEMALL.ai

BF transitgateway

Configures AWS Transit Gateway: creating a hub and attaching VPCs, segmenting traffic with route tables, centralizing egress and inspection through a hub (appliances or a Gateway Load Balancer endpoint), forcing east-west traffic between VPCs through AWS Network Firewall, connecting on-premises networks over the transit-gateway side of a Site-to-Site VPN or Direct Connect attachment (including ECMP to aggregate bandwidth across multiple VPN tunnels), peering transit gateways across Regions, migrating from a VPC peering mesh, and routing IP multicast. Applicable when connecting many VPCs through one router, isolating environments, forcing VPC-to-VPC traffic through a central Network Firewall, reaching on-premises over the hub, linking Regions, or moving off a peering mesh. Not applicable for single-VPC routing, VPC peering between two VPCs (vpcpeering skill), Direct Connect gateway or virtual interface setup (directconnect skill), or Route 53 DNS work.

ClawHub Agent Skills author: Amazon Web Services 1 file body ≈ 1 692 tokens Open the sourceclawhub.ai analyzed 2 d ago

Configures AWS Transit Gateway: creating a hub and attaching VPCs, segmenting traffic with route tables, centralizing egress and inspection through a hub…

As a process F 40/100 · Will not run — References files that are not bundled: references/creating-a-transit-gateway-and-attaching-vpcs.md, references/segmenting-traffic-with-route-tables.md, references/centralizing-egress-and-inspection.md

IntegrationAWSInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
F
40/100
Will not run
References files that are not bundled: references/creating-a-transit-gateway-and-attaching-vpcs.md, references/segmenting-traffic-with-route-tables.md, references/centralizing-egress-and-inspection.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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-ref reference to a missing file: references/creating-a-transit-gateway-and-attaching-vpcs.md
  • warning missing-ref reference to a missing file: references/segmenting-traffic-with-route-tables.md
  • warning missing-ref reference to a missing file: references/centralizing-egress-and-inspection.md
  • warning missing-ref reference to a missing file: references/inspecting-east-west-traffic-with-network-firewall.md
  • warning missing-ref reference to a missing file: references/connecting-on-premises-networks.md
  • warning missing-ref reference to a missing file: references/peering-transit-gateways-across-regions.md
  • warning missing-ref reference to a missing file: references/migrating-from-vpc-peering.md
  • warning missing-ref reference to a missing file: references/routing-multicast-traffic.md

Process rating: all ten parameters 40/100

Will not run. References files that are not bundled: references/creating-a-transit-gateway-and-attaching-vpcs.md, references/segmenting-traffic-with-route-tables.md, references/centralizing-egress-and-inspection.md
  • 0Tools and files. 8 referenced file(s) missing: references/creating-a-transit-gateway-and-attaching-vpcs.md, references/segmenting-traffic-with-route-tables.md, references/centralizing-egress-and-inspection.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 5 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 14 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1692 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)
  • +3Description length 965: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 14 items
  • +4Has examples (0 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.