CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

84%

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

The canonical home for this skill is routing-traffic-with-route53-and-cloudfront in aws/agent-toolkit-for-aws

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

A well-structured, concise body that delegates the detailed procedure to a genuine reference file and keeps actionable troubleshooting inline. The main gaps are mild redundancy with the frontmatter description and thin in-body validation checkpoints.

DimensionReasoningScore

Conciseness

Lean overall with no explanations of concepts Claude already knows, but the Overview paragraph largely restates the frontmatter description and the 'The procedure covers:' bullet list previews content already in the reference file — minor instances that could be trimmed.

4 / 5

Actionability

Mostly executable guidance for an instruction-only skill: concrete specifics like 'ACM certificates for CloudFront must be in us-east-1', 'Use nslookup or dig to verify', and a real 282-line reference procedure. Not a 5 because the body itself contains no AWS CLI commands and the main workflow is delegated via a pointer.

4 / 5

Workflow Clarity

The bullets present a clear ordered sequence (verify distribution and CNAMEs, request and validate ACM certificate, create hosted zone, create alias A/AAAA records, monitor propagation) and the Troubleshooting section gives error recovery for four failure modes, but validation checkpoints in the body itself are thin — only 'Monitoring DNS propagation' — leaving minor validation gaps.

4 / 5

Progressive Disclosure

Clear overview inline, the full procedure appropriately split into a well-signaled, one-level-deep, verified-real reference file, and troubleshooting kept inline where it belongs; navigation is easy.

5 / 5

Total

17

/

20

Passed

Description

87%Weight 40%Scale 1-5

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

A strong description: third-person voice, concrete capabilities, and an explicit 'Use when...' clause with specific trigger terms. Its only weaknesses are minor — the action list could be more granular and a few natural synonyms (e.g., 'hosted zone', 'point domain to CloudFront') are absent.

DimensionReasoningScore

Specificity

Enumerates several concrete configuration items ('DNS alias records, alternate domain names (CNAMEs), ACM certificates for HTTPS, and IPv6 support'), but the primary action is a single composite verb ('Configures Amazon Route 53 to route traffic to a CloudFront distribution'), not the multiple distinct concrete actions of the score-5 anchor.

4 / 5

Completeness

Explicitly answers both 'what' ('Configures Amazon Route 53 to route traffic to a CloudFront distribution using a custom domain') and 'when' ('Use when setting up DNS alias records, alternate domain names (CNAMEs), ACM certificates for HTTPS, and IPv6 support') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('Route 53', 'CloudFront', 'custom domain', 'CNAMEs', 'ACM certificates', 'IPv6') but misses common variations like 'hosted zone', 'DNS setup', or 'point my domain to CloudFront', falling short of the score-5 comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Names both services explicitly and pins a clear niche (Route 53 alias routing to CloudFront), giving distinct triggers and minimal conflict risk with generic DNS or certificate skills.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

mreferre/aws-agent-toolkit-skills

Path

.kiro/skills/routing-traffic-with-route53-and-cloudfront/SKILL.md

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.