CtrlK
BlogDocsLog inGet started
Tessl Logo

routing-traffic-with-route53-and-cloudfront

Configures Amazon Route 53 to route traffic to a CloudFront distribution using a custom domain. Use when setting up DNS alias records, alternate domain names (CNAMEs), ACM certificates for HTTPS, and IPv6 support for CloudFront.

70

Quality

86%

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

72%

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

The body is well-structured and token-efficient with excellent progressive disclosure, but its actionability and workflow clarity are limited because the main procedure is offloaded to a reference file rather than presented inline with explicit validation checkpoints.

Suggestions

Add a short inline numbered summary of the core configuration steps with a validation checkpoint (e.g., confirm ACM certificate is 'ISSUED' before creating alias records) so the body is actionable without opening the reference.

Include one or two concrete commands in the body for the most error-prone step (e.g., the alias record creation via AWS CLI) rather than relying solely on the referenced procedure.

Add an explicit feedback loop for the DNS propagation step (verify with dig/nslookup, retry until resolved) to strengthen workflow clarity for the verification phase.

DimensionReasoningScore

Conciseness

The body is lean—an overview, a signaled reference pointer, a bullet summary, and targeted troubleshooting—with no padding or explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

Troubleshooting gives concrete specifics ("must be in us-east-1", "Use nslookup or dig", "60 seconds...48 hours"), but the core configuration procedure is delegated to the reference rather than providing inline executable steps, so guidance is incomplete in the body itself.

2 / 3

Workflow Clarity

A sequence is present (verify distribution, request ACM cert, create hosted zone, create alias records, monitor propagation) but validation checkpoints and error-recovery loops live in the referenced file, not in the body, so checkpoints are implicit here.

2 / 3

Progressive Disclosure

The body is a clear overview pointing to a single, clearly signaled one-level-deep reference (references/route53-cloudfront-routing.md) that exists and is well-organized, with content appropriately split and easy to navigate.

3 / 3

Total

10

/

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 concise, specific, and uses third person with an explicit 'Use when' trigger clause covering concrete actions and natural terms. It clearly communicates both capability and invocation context without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—"route traffic to a CloudFront distribution", "DNS alias records", "alternate domain names (CNAMEs)", "ACM certificates for HTTPS", and "IPv6 support"—matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly states what it does ("Configures Amazon Route 53 to route traffic...") and when to use it ("Use when setting up DNS alias records..."), satisfying both what and when with an explicit trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms users would say—"Route 53", "CloudFront", "custom domain", "DNS alias records", "CNAMEs", "ACM certificates", "HTTPS", "IPv6"—giving good coverage of natural vocabulary.

3 / 3

Distinctiveness Conflict Risk

The Route 53 + CloudFront custom-domain niche with specific triggers (alias records, ACM certs, IPv6) is clearly distinct and unlikely to fire for unrelated skills.

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.