Name: fastly
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

fastly

Fastly integration. Manage data, records, and automate workflows. Use when the user wants to interact with Fastly data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/fastly/SKILL.md

Quality

Content

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

The content is a strong, executable CLI integration guide with concrete commands, a well-sequenced connection state machine, and clean sectioning. Its main weaknesses are an unnecessary CDN explainer at the top and some redundancy between the action-discovery sections.

Suggestions

Cut or compress the opening paragraph explaining what a CDN/Fastly is; Claude already knows this and it costs context tokens.

Merge the overlapping 'Searching for actions' and 'Popular actions' sections, which both demonstrate `membrane action list --intent`, into a single action-discovery section.

Fix the step numbering in the connection flow by labeling 'Step 1' (ensure) and the referenced 'Step 2' so the 'skip to Step 2' and '1b' references resolve clearly.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but it opens by explaining what a CDN is ('Fastly is a content delivery network (CDN) that provides edge cloud services...') which Claude already knows, and the 'Searching for actions' and 'Popular actions' sections restate the same action-list command, fitting the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	The body provides copy-paste-ready commands for the common flows (install, login, connection ensure/get, action list/run, request proxy) with real flags and a flag reference table, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state validation (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but the step numbering is slightly inconsistent (a '1b' and a referenced 'Step 2' without a matching labeled step), leaving minor gaps.	4 / 5
Progressive Disclosure	The skill is organized into well-labeled sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy requests, Best practices) with no nested references and no bundle files present, but the minor redundancy between the two action-discovery sections keeps it just below fully clean organization.	4 / 5
	Total	16 / 20 Passed

Description

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

The description correctly includes both a capability statement and a 'Use when' trigger anchored to the Fastly brand, but relies on generic 'manage data and workflows' language rather than concrete Fastly-specific actions. Tightening the action list and adding task-level trigger terms would meaningfully raise specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Fastly actions such as 'purge cache, manage services and backends, configure VCL, and inspect logs'.

Add natural task trigger terms users actually say, e.g. 'Use when the user wants to purge the Fastly cache, manage a service version, or inspect edge/realtime metrics'.

Mention the CDN/edge context as a trigger synonym so the skill surfaces for 'CDN' or 'edge' requests, not just literal 'Fastly' mentions.

Dimension	Reasoning	Score
Specificity	The description names the Fastly domain but its actions are generic boilerplate ('Manage data, records, and automate workflows') rather than concrete Fastly operations like purging cache or managing services, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Fastly data') are present, but the 'when' could be more specific, matching the anchor for both present with room to sharpen.	4 / 5
Trigger Term Quality	The brand keyword 'Fastly' is a natural term users would say, but the description misses common task synonyms and variations (CDN, cache, edge, purge, VCL), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The explicit 'Fastly' brand name gives a clear niche with minimal conflict risk, though the generic 'manage data, records, automate workflows' phrasing is shared across many integration skills, leaving minor overlap risk.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/fastly/SKILL.md
Commit: f484c82

Reviewed: ~19 hours ago

Table of Contents

Discovery Implementation Validation

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.