Name: akamai
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

akamai

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

61%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 body is actionable and reasonably well-structured, but it spends tokens explaining what Akamai/CDN is and its multi-step connection workflow has broken step references that hurt clarity.

Suggestions

Remove the CDN explanation paragraph ("Akamai is a content delivery network..."); Claude already knows this and it adds no integration value.

Fix the step numbering: replace the dangling "Step 2" references and "1b" label with a coherent numbered sequence (1. Install, 2. Authenticate, 3. Connect, 4. Discover actions, 5. Run).

Trim editorial padding such as "so you can focus on the integration logic rather than auth plumbing" to keep the body lean.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but includes unnecessary explanation Claude already knows ("Akamai is a content delivery network (CDN)...") and padded phrasing ("so you can focus on the integration logic rather than auth plumbing").	3 / 5
Actionability	Provides concrete, copy-paste-ready commands (login, connection ensure, action run, request) plus a flags table, with only minor gaps such as unresolved CONNECTION_ID/actionId placeholders.	4 / 5
Workflow Clarity	A rough sequence exists with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but references to a non-existent "Step 2" and a "1b" label without a "1a" make the flow incoherent in places.	3 / 5
Progressive Disclosure	Single well-organized SKILL.md with clear sections (Overview, Working with Akamai, Popular actions, Best practices) and a reference table; no external files are needed so structure alone earns this.	4 / 5
	Total	14 / 20 Passed

Description

62%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 answers both what and when with a clear Akamai-specific trigger, but its action list is generic and it lacks the natural vocabulary (CDN, DNS, certificates) users actually invoke.

Suggestions

Replace generic verbs with concrete Akamai actions, e.g. "Manage DNS zones and records, traffic management properties, certificates, and security policies."

Add natural trigger terms users would say, such as "CDN", "DNS zone", "traffic management", or "edge security".

Sharpen the 'Use when' clause to name specific intents, e.g. "Use when the user wants to manage Akamai DNS, certificates, or traffic management."

Dimension	Reasoning	Score
Specificity	Names the domain ("Akamai integration") and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete Akamai operations like DNS record management or certificate provisioning.	3 / 5
Completeness	Clearly states what ("Akamai integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Akamai data"), though the trigger could be more specific.	4 / 5
Trigger Term Quality	"Akamai" and "data"/"records" are relevant keywords, but common natural variations a user would say (e.g., CDN, DNS zones, traffic management, certificates) are absent.	3 / 5
Distinctiveness Conflict Risk	"Akamai integration" carves a clear niche with a distinct trigger ("interact with Akamai data"), with only minor overlap risk against generic data-management skills.	4 / 5
	Total	14 / 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/akamai/SKILL.md
Commit: f484c82

Reviewed: 3 days 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.