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

panzura

Panzura integration. Manage data, records, and automate workflows. Use when the user wants to interact with Panzura 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/panzura/SKILL.md

Quality

Content

50%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 delivers strong, concrete CLI guidance for connecting to and acting on Panzura, with a useful connection-state polling loop. Its main weaknesses are a heavily padded duplicate entity list, missing validation for destructive operations, and no use of reference files to split out the catalog.

Suggestions

Collapse the duplicated entity list (every "Data Lake X" mirrors a top-level entry) into a single deduplicated catalog or move it to a references/ file linked from the overview.

Add a validation/verification step before running destructive actions or proxy DELETE/PUT requests, e.g. confirming the target id and checking the response state before proceeding.

Fix the dangling "skip to Step 2" reference by labeling the downstream section or rewording to "skip to Running actions."

Dimension	Reasoning	Score
Conciseness	The ~90-item entity list with near-complete "Data Lake X" duplication is heavy padding that adds little actionable value, matching the anchor for noticeably verbose padded sections. It is above 1 because the operational sections (install, auth, connection, proxy) are reasonably efficient.	2 / 5
Actionability	Provides concrete copy-pasteable commands (npm install, membrane login, connection ensure, action run, request) plus a proxy-flags table, matching the anchor for mostly executable guidance with minor gaps. Not a 5 because no real Panzura action id or input example is shown and the entity list only says "Use action names and parameters as needed."	4 / 5
Workflow Clarity	Sequences install → login → connect → search → run with a polling feedback loop for connection state, but offers no validation/verification for destructive action/proxy operations (a DELETE method is shown), capping it at 3 per the destructive-ops guideline. Also the "skip to Step 2" reference is dangling with no labeled Step 2.	3 / 5
Progressive Disclosure	Has clear section headers but no bundle reference files (references/scripts/assets are absent) and inlines the large entity catalog that would be better placed in a separate reference file, matching the anchor for some structure with content that should be separate kept inline. Not a 4 because no one-level-deep references are used to offload the catalog.	3 / 5
	Total	12 / 20 Passed

Description

66%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 clearly names the Panzura product and includes an explicit "Use when" trigger, giving it strong distinctiveness and decent completeness. It is held back by generic action verbs and limited trigger-term coverage that omit the file-system concepts users would naturally mention.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Panzura actions such as managing files, folders, shares, snapshots, and retention policies.

Broaden the trigger phrase to cover natural user language, e.g. "Use when the user wants to work with Panzura files, folders, shares, or distributed file-system data."

Mention file-system-specific terms (files, folders, shares, snapshots) so the description surfaces the capabilities the body actually exposes.

Dimension	Reasoning	Score
Specificity	Names the domain (Panzura) and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, matching the anchor that lists domain plus 1-2 actions without comprehensive coverage. It is below 4 because the verbs lack the specificity of "extracts text, fills forms, converts pages".	3 / 5
Completeness	Explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Panzura data"), matching the anchor for both present with the when somewhat narrow. Not a 5 because the trigger phrase is narrow and does not cover records, workflows, or file-system use cases concretely.	4 / 5
Trigger Term Quality	Includes relevant keywords ("Panzura", "data", "records", "workflows", "interact with Panzura data") but misses common variations users would say (files, folders, shares, file system), fitting the anchor for some relevant keywords missing synonyms. Not a 4 because file-system terms the body reveals are absent from the description.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named product ("Panzura integration", "interact with Panzura data"), giving it a clear niche with distinct triggers and minimal conflict risk, matching the top anchor. It is not a 4 because the product name itself makes overlap with other skills unlikely.	5 / 5
	Total	15 / 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/panzura/SKILL.md
Commit: f484c82

Reviewed: 5 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.