Cloudfront Distribution Setup - Auto-activating skill for AWS Skills. Triggers on: cloudfront distribution setup, cloudfront distribution setup Part of the AWS Skills skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/cloudfront-distribution-setup/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a very weak description that essentially just repeats the skill name without providing any meaningful detail about capabilities or usage triggers. It reads as auto-generated boilerplate with a duplicated trigger term, offering no concrete actions, no natural user keywords, and no explicit guidance on when Claude should select this skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures AWS CloudFront distributions, sets up origins, configures cache behaviors, manages SSL/TLS certificates, and creates invalidations.'
Add an explicit 'Use when...' clause with natural trigger terms like 'CDN setup', 'content delivery network', 'CloudFront', 'edge caching', 'static asset distribution', 'AWS CDN configuration'.
Remove the duplicated trigger term and replace with varied, natural phrases users would actually say when needing this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('cloudfront distribution setup') but does not describe any concrete actions like creating distributions, configuring origins, setting up cache behaviors, or managing SSL certificates. It's essentially just a title repeated. | 1 / 3 |
Completeness | The 'what' is extremely weak (just the skill name restated) and there is no explicit 'when' clause. The 'Triggers on' line just repeats the same phrase twice rather than providing meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'cloudfront distribution setup' repeated twice. It misses natural variations users would say like 'CDN', 'content delivery', 'CloudFront', 'cache invalidation', 'origin configuration', 'edge locations', or 'AWS CDN'. | 1 / 3 |
Distinctiveness Conflict Risk | CloudFront distribution setup is a fairly specific AWS service, which gives it some distinctiveness. However, the lack of detail about what specific aspects of CloudFront it handles means it could overlap with other AWS networking or CDN-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual content. It consists entirely of auto-generated boilerplate that describes what the skill would do without providing any real CloudFront distribution setup instructions, code, or configuration examples. It fails on every dimension because it contains no actionable, concrete, or useful information.
Suggestions
Add concrete AWS CLI commands or CloudFormation/CDK templates for creating a CloudFront distribution (e.g., `aws cloudfront create-distribution --distribution-config file://config.json` with an example config)
Include a step-by-step workflow covering origin setup, cache behavior configuration, SSL/TLS certificate attachment, and DNS configuration with validation checkpoints
Add specific code examples for common patterns: S3 origin with OAC, ALB origin, custom error pages, and cache invalidation commands
Replace all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') with actual technical content—the skill should teach, not describe itself
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual CloudFront distribution setup guidance. Every section describes the skill rather than teaching anything actionable. | 1 / 3 |
Actionability | There are zero concrete instructions, no CLI commands, no CloudFormation/Terraform snippets, no API calls, and no executable code. The content is purely descriptive with no actionable guidance for setting up a CloudFront distribution. | 1 / 3 |
Workflow Clarity | There is no workflow whatsoever—no steps, no sequence, no validation checkpoints. Claims to provide 'step-by-step guidance' but none is actually present in the content. | 1 / 3 |
Progressive Disclosure | No structure beyond boilerplate headings. No references to detailed guides, no links to related files, and no meaningful organization of content since there is no substantive content to organize. | 1 / 3 |
Total | 4 / 12 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
933cf26
Table of Contents
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.