Name: zype
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zype

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

Quality

73%

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

Quality

Content

80%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 highly actionable with executable commands and a well-sequenced connection workflow, and it stays lean for a self-contained CLI skill. Its key weakness is the lack of explicit validation/feedback loops for the proxy's destructive HTTP methods, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint for destructive proxy requests (POST/PUT/PATCH/DELETE), e.g. dry-run or confirm-before-execute and inspect the response status before proceeding.

Trim restated guidance such as 'You should always search for actions in the context of a specific connection' since the preceding command already implies it.

Make the action-search -> action-run handoff explicit (capture the returned actionId, then pass it to `membrane action run`) so the two-step flow is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with command snippets and tables rather than padded prose, though a few lines restate obvious points (e.g. 'You should always search for actions in the context of a specific connection'), placing it just above the midpoint toward 'Efficient; minor instances that could be trimmed'.	4 / 5
Actionability	It provides copy-paste-ready CLI commands for install, login, connection, action search/run, and proxy requests, with concrete flags and JSON examples covering the common cases, matching the 'Fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state checks and a polling loop, but the proxy supports destructive HTTP methods (POST/PUT/PATCH/DELETE) with no explicit validation/verification steps, so per the destructive-operation cap workflow clarity is held at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the content is under 50 lines of substantive guidance with well-organized sections; per the simple-skills guidance, a concise self-contained skill with clear sections scores 5 here.	5 / 5
	Total	17 / 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 correctly pairs a 'what' with an explicit 'Use when' trigger and leverages a distinctive brand name for low conflict risk. Its weakness is generic action wording ('manage data, records, automate workflows') and limited natural trigger-term coverage.

Suggestions

Replace generic verbs with concrete Zype-specific actions, e.g. 'Manage videos, playlists, and users; automate video distribution workflows.'

Add natural trigger phrasings users would say, e.g. 'Use when the user wants to manage Zype videos, playlists, users, or video distribution.'

Mention file/extension or object terms users actually reference (e.g. 'Zype videos', 'video content') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain (Zype) and lists concrete actions ('Manage data, records, and automate workflows'), but the actions are generic and not comprehensive, mirroring the 'Names domain and 1-2 concrete actions, but not comprehensive' anchor.	3 / 5
Completeness	It gives a clear 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Zype data'), with the 'when' somewhat generic, matching the 'both present but when could be more explicit' anchor.	4 / 5
Trigger Term Quality	It surfaces relevant keywords ('Zype', 'data', 'records', 'workflows') but misses natural user phrasings and synonyms a user would actually say; comparable to 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The Zype brand name and video-distribution framing give it a clear niche with distinct triggers and minimal conflict risk, matching the 'Clear niche with distinct triggers' anchor.	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/zype/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.