CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a well-structured router: it stays lean, gives concrete routing and decision guidance, sequences the read-then-execute workflow, and uses a verified one-level-deep reference table for progressive disclosure. It reaches the top anchor on all four content dimensions.

DimensionReasoningScore

Conciseness

The body is dense and high-signal with no padding — it assumes Claude's AWS knowledge and avoids explaining what a transit gateway is; every section (routing notes, security considerations) earns its tokens.

3 / 3

Actionability

Provides concrete decision rules (disable default association/propagation up front; GWLB recommended for new designs; appliance mode required for stateful cross-AZ inspection with a stated failover tradeoff) plus specific credential and Region guidance; as an instruction-only router it delegates executable code to the per-task references, which the scoring notes do not penalize when guidance is actionable.

3 / 3

Workflow Clarity

Sequences the router workflow clearly — identify the task via the goal-to-reference table, read the matching reference in full before acting, follow its constraints, execute via MCP/CLI with least-privilege credentials in the hub's Region — with the table acting as an explicit decision checkpoint.

3 / 3

Progressive Disclosure

A clear overview points to eight well-signaled one-level-deep reference files via a goal-to-link table, and all referenced paths were verified to exist in references/, giving clean navigation with no nested indirection.

3 / 3

Total

12

/

12

Passed

Description

100%

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

The description is exemplary: third-person, specific, and concise, with an explicit 'Applicable when' trigger clause and a 'Not applicable for' boundary that names adjacent skills to avoid conflicts. It scores at the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists many concrete actions — 'creating a hub and attaching VPCs, segmenting traffic with route tables, centralizing egress and inspection... forcing east-west traffic between VPCs through AWS Network Firewall', plus ECMP bandwidth aggregation, inter-Region peering, and multicast — rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' (the capability list) and 'when' via the 'Applicable when...' clause, and adds a 'Not applicable for...' boundary, satisfying the explicit-trigger requirement for the top anchor.

3 / 3

Trigger Term Quality

Covers natural terms users would actually say — 'transit gateway', 'connecting many VPCs', 'isolating environments', 'VPC-to-VPC traffic', 'on-premises', 'linking Regions', 'peering mesh' — not just internal jargon.

3 / 3

Distinctiveness Conflict Risk

Has a clear AWS Transit Gateway niche and explicitly disambiguates against the vpcpeering skill, directconnect skill, and Route 53 DNS work, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.