Name: zamzar
Rating: 52 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zamzar

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

Quality

58%

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

Quality

Content

67%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 well-structured, mostly executable guide to driving Zamzar through the Membrane CLI, with a clear connection-state workflow and a useful proxy reference. Its main weaknesses are some introductory padding, duplicated action-list examples, and broken step cross-references ('Step 2', '1b').

Suggestions

Remove the introductory paragraph explaining what Zamzar is and who uses it; assume Claude's knowledge and lead with the integration mechanics.

Consolidate the duplicated 'membrane action list' examples in 'Searching for actions' and 'Popular actions' into a single section.

Fix the workflow cross-references: define 'Step 2' (or relabel it) and renumber '1b' so the connection sequence is internally consistent.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational and command-driven, but the opening paragraph explaining what Zamzar is and who uses it ('used by individuals and businesses who need to convert files without installing software') is unnecessary padding, and the 'membrane action list' command is demonstrated twice (lines 103 and 112). It is mostly efficient with some trimming possible, matching the 3 anchor.	3 / 5
Actionability	Concrete, executable commands are provided throughout (install, login, connection ensure, action run, request) plus a full proxy flag table, covering the common cases. It is not a 5 because some commands rely on placeholders (CONNECTION_ID, actionId) and the action-discovery examples are duplicated rather than consolidated, leaving minor gaps.	4 / 5
Workflow Clarity	The connection setup flow is sequenced with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a polling loop with --wait, giving clear validation. It is not a 5 because the referenced 'Step 2' is never defined and '1b' appears without a '1a', leaving the cross-reference structure slightly broken.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clear, well-labeled sections (Overview, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references. It is not a 5 because the 'Searching for actions' and 'Popular actions' sections overlap redundantly, a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

48%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 uses third-person voice and includes a 'Use when' trigger, but it is generic and omits the skill's core purpose (file conversion), relying on vague 'manage data, records, and automate workflows' phrasing. Brand-name specificity helps distinctiveness, yet the missing concrete capabilities and conversion keywords weaken it.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete conversion actions, e.g. 'Convert files between document, image, audio, and video formats via Zamzar.'

Add natural trigger keywords and file extensions, e.g. 'Use when the user wants to convert files or transform file formats (e.g. .docx to .pdf).'

State the actual 'what' explicitly so the description answers what the skill does, not just that it integrates with Zamzar.

Dimension	Reasoning	Score
Specificity	The description only offers generic actions ('Manage data, records, and automate workflows') and never states the skill's actual purpose — file format conversion — so it names a domain label ('Zamzar integration') without concrete actions. It is below the 3 anchor because it lists no specific, real capability.	2 / 5
Completeness	A 'when' clause is present ('Use when the user wants to interact with Zamzar data'), but the 'what' is vague ('Manage data, records, and automate workflows') and does not describe the actual conversion functionality. This sits between the vague-what (2) and explicit-what-and-when (4) anchors, so 3.	3 / 5
Trigger Term Quality	The brand term 'Zamzar' and the phrase 'interact with Zamzar data' are natural, but no conversion-related keywords ('convert files', 'file formats', 'transform') or file extensions appear. It misses the common variations users would say, fitting the 3 anchor better than 4.	3 / 5
Distinctiveness Conflict Risk	The 'Zamzar' brand name makes the trigger fairly distinct and unlikely to fire for unrelated skills, though the generic 'manage data/records/workflows' wording leaves minor overlap risk. It is mostly distinct with minor overlap, matching the 4 anchor rather than the fully-niched 5.	4 / 5
	Total	12 / 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/zamzar/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.