CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fastly

Configures, manages, and debugs the Fastly CDN platform — covering service and backend setup, caching and VCL, security features like DDoS/WAF/NGWAF/rate limiting/bot management, TLS certificates and cache purging, the Compute platform, and the REST API. Use when working with Fastly services or domains, setting up edge caching or origin shielding, configuring security features, making Fastly API calls, enabling products, or looking up Fastly documentation. Also applies when troubleshooting 503 errors or SSL/TLS certificate mismatches on Fastly, and for configuring logging endpoints, load balancing, ACLs, or edge dictionaries. Read the relevant reference file before writing any Fastly API call or curl command — request field names (e.g. the backend fields override_host, ssl_cert_hostname, ssl_sni_hostname, use_ssl) are easy to misremember, and a wrong name causes a silent 503 instead of an error, so do not rely on training-knowledge field names.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 strong overview body: executable pre-flight checks and VCL recipes, crisp navigation to a well-organized reference bundle, and explicit guardrails against common errors. The main gaps are the delegation of the core service-creation workflow to a sibling skill without a summary sequence, and a few passages that could be tightened further.

Suggestions

Add a brief inline outline of the create-service → add-domain → add-backend → activate sequence in the Quick Start (even 4 numbered steps with the CLI commands), keeping the fastly-cli reference for full detail.

Tighten the cookie subfield() explanation to one sentence plus the code line — the substring false-match example can be cut to 'regex substring-matches name_v2=X' without losing the lesson.

Include a post-activation verification step (e.g. curl the service domain and check the X-Cache header set up in the Cache Status Headers recipe) to close the workflow loop.

DimensionReasoningScore

Conciseness

The body is efficient — a terse topics table, one-line framing ("Your training knowledge of Fastly is likely out of date"), and lean recipes with warnings only where mistakes are likely. Minor over-explanation exists, e.g. the cookie section spells out the substring false-match example ("if the cookie header is name_v2=X, the regex... still matches") at slightly more length than needed. Not 5 because a few passages could be trimmed; not 3 because there is no real padding or explanation of concepts Claude already knows.

4 / 5

Actionability

Fully executable throughout: copy-paste curl/openssl pre-flight commands ("curl -sI -H 'Host: DESIRED_HOST' https://ORIGIN_ADDRESS/"), complete VCL code blocks for six common patterns, a concrete mistakes list with correct alternatives ("set beresp.ttl = 86400 is a type error — needs the s suffix: 86400s"), and exact doc-fetch instructions with URL and Accept header. Covers the common cases with exact syntax. Not 4: no gaps between guidance and execution.

5 / 5

Workflow Clarity

The Quick Start leads with explicit pre-flight validation (verify origin responds, check TLS certificate SANs) including commands and an error-recovery branch ("If HTTPS cert validation cannot be made correct but HTTP with the intended Host works, use an HTTP backend or fix the origin cert; never disable backend cert verification"). However, the core multi-step sequence (create service, add domain, add backend, activate) is delegated to the fastly-cli skill's services.md reference rather than sequenced inline, and post-change verification of the deployed service is not covered. Not 5 because the primary workflow's steps and checkpoints live outside this file; not 3 because validation before changes is explicit and command-backed.

4 / 5

Progressive Disclosure

Model progressive disclosure: a topics table routes to 21 one-level-deep reference files (all verified present in ./references/), each row carrying a 'Use when...' column for discovery; a scope boundary note explicitly excludes traffic stats (routed to the fastly-stats skill); only the single most common task (caching proxy setup) is inlined. The Fetching Documentation section adds a further escape hatch via docs-navigation.md. Not 4: structure, signaling, and content split are all clean with no organization gaps.

5 / 5

Total

18

/

20

Passed

Description

96%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.

An excellent description: concrete, comprehensive capability statements paired with an explicit and richly varied 'Use when' clause covering setup, configuration, API, and troubleshooting triggers. The only weakness is the absence of an explicit boundary against the closely related fastly-stats and fastly-cli sibling skills.

DimensionReasoningScore

Specificity

Uses concrete verbs ("Configures, manages, and debugs") and enumerates comprehensive platform coverage: "service and backend setup, caching and VCL, security features like DDoS/WAF/NGWAF/rate limiting/bot management, TLS certificates and cache purging, the Compute platform, and the REST API". This matches the comprehensive-coverage anchor; not 4 because the feature-area coverage has no notable gaps.

5 / 5

Completeness

Explicitly answers both: what ("Configures, manages, and debugs the Fastly CDN platform — covering...") and when ("Use when working with Fastly services or domains... Also applies when troubleshooting 503 errors..."). Concrete trigger phrases accompany both, matching the top anchor. Not 4: the 'when' is fully explicit with multiple specific triggers, not merely present.

5 / 5

Trigger Term Quality

Covers natural user phrasing broadly: "working with Fastly services or domains, setting up edge caching or origin shielding", "troubleshooting 503 errors or SSL/TLS certificate mismatches", "logging endpoints, load balancing, ACLs, or edge dictionaries". These are exactly the words a user with a Fastly task would say, including troubleshooting vocabulary. Not 4: no common synonym family for the domain is missing.

5 / 5

Distinctiveness Conflict Risk

Clear Fastly-specific niche with distinct triggers; minimal conflict with unrelated skills. However, sibling skills exist (fastly-cli, fastly-stats), and the description does not disambiguate traffic/stats requests (e.g. "cache hit ratio", "bandwidth") which the body routes to fastly-stats — a minor overlap risk with closely related skills. Not 5 for this unstated boundary; not 3 since the niche is unambiguous outside the sibling skills.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fastly/fastly-agent-toolkit

Path

skills/fastly/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.