Name: volterra
Rating: 51.2 (1 reviews)
Author: membranedev

volterra

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

Quality

56%

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/volterra/SKILL.md

Quality

Content

56%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 CLI usage guidance is executable and well-sequenced with a solid connection state machine, but the body is dominated by an unexplained ~175-item resource list and a truncated intro sentence that waste context. Moving the resource catalog to a separate reference file would improve both conciseness and progressive disclosure.

Suggestions

Move the ~175-item resource catalog into a separate references file (e.g. RESOURCES.md) and link to it from the overview instead of inlining every name.

Complete or remove the broken sentence "Volterra provides a distributed" so the overview opens with a coherent purpose statement.

Add a brief validation/feedback step after running actions (e.g. check the `output`/`error` fields and retry on failure) to strengthen error recovery in the workflow.

Dimension	Reasoning	Score
Conciseness	A ~175-line inlined list of bare resource names and a broken introductory sentence ("Volterra provides a distributed") are significant padding that does not earn its tokens, while the CLI section is reasonably efficient, landing noticeably verbose overall.	2 / 5
Actionability	The Membrane section gives concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a flags table, with only minor gaps like unresolved placeholders (CONNECTION_ID, actionId).	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling guidance, though error recovery is limited to "check the error field".	4 / 5
Progressive Disclosure	Section headers provide some structure, but the large resource-name dump clearly belongs in a separate reference file and is inlined, with no bundle files or one-level-deep references to offload it.	3 / 5
	Total	13 / 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 pairs a third-person what statement with an explicit "Use when" trigger and targets a distinct platform, but its capability verbs are too generic to be specific or comprehensive. Tightening "Manage data, records, and automate workflows" into concrete Volterra operations would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Volterra operations, e.g. "Manage Volterra sites, origin pools, virtual hosts, and WAF policies; automate fleet workflows."

Add natural trigger synonyms users actually say, such as "Volterra", "F5 Distributed Cloud", "VoltDB site", or "CE/RE sites".

Keep the "Use when…" clause but tie it to concrete intents, e.g. "Use when the user wants to configure Volterra load balancing, networking, or security policies."

Dimension	Reasoning	Score
Specificity	The description names the Volterra domain but its actions—"Manage data, records, and automate workflows"—are generic verbs with no concrete operations, matching the anchor where actions are minimal or generic.	2 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Volterra data"), though the what is vague, matching the anchor with both present but the when slightly improvable.	4 / 5
Trigger Term Quality	"Volterra data" and "interact with Volterra" provide a relevant keyword, but natural synonyms and variations users might say are missing, fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Volterra is a specific named platform giving it a clear niche with minimal conflict risk, though the generic action phrasing leaves minor overlap with broad data-management skills.	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/volterra/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.