Name: zeet
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zeet

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

Quality

62%

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/zeet/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 body is a well-structured, command-rich integration guide with executable examples, a clear connection workflow, and explicit error-state handling. Its main weaknesses are mild verbosity/redundancy and the absence of explicit post-action validation for potentially destructive Zeet operations.

Suggestions

Remove the duplicated action-discovery command between 'Searching for actions' and 'Popular actions', merging them into one section.

Trim the introductory 'Zeet is a platform...' paragraph or fold it into the overview, since it explains context Claude largely does not need.

Add an explicit validation step after running deploy/infrastructure actions (e.g. check the output state and confirm success before reporting completion) to strengthen workflow_clarity for destructive operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-focused, but the opening 'Zeet is a platform for deploying and managing applications...' and the duplicated action-discovery command across 'Searching for actions' and 'Popular actions' are unnecessary explanation/redundancy that could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor rather than the lean level-4.	3 / 5
Actionability	It provides concrete executable commands throughout (npm install, membrane login, connection ensure/get, action list/run, request) plus a full proxy flag table, matching 'mostly executable guidance; concrete commands with minor gaps'; it stops short of level 5 because examples use placeholders (CONNECTION_ID, <actionId>) rather than a fully copy-paste-ready invocation with real values.	4 / 5
Workflow Clarity	The connection setup flow has a clear sequence with explicit checkpoints and a feedback loop ('poll again... to check if the state moved to READY', retry after CLIENT_ACTION_REQUIRED), matching 'clear sequence with most checkpoints present'; it is not level 5 because action/proxy execution lacks an explicit post-run validation step, and the destructive-deployment cap is avoided since Membrane is documented as handling errors and the primary structured workflow is well-validated.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is organized into clear, well-signaled sections (Overview, Working with Zeet, Popular actions, Best practices) appropriate for a single-file skill, matching 'good structure; most content appropriately placed'; it is not level 5 because of minor redundancy between the 'Searching for actions' and 'Popular actions' sections rather than perfectly split navigation.	4 / 5
	Total	15 / 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 includes an explicit 'Use when...' trigger and leverages the distinct Zeet brand, but its capability phrasing is generic and abstract rather than naming concrete Zeet actions. It is functional but reads as a templated integration description rather than a sharply specific one.

Suggestions

Replace generic verbs with concrete Zeet actions, e.g. 'Deploy and manage applications, environments, and instances across Zeet projects'.

Add natural trigger phrases users would say, such as 'Use when the user wants to deploy apps, manage Zeet projects/environments, or automate Zeet workflows'.

Reference the core Zeet objects (Project, Environment, Deploy, Instance, Template) in the description to boost specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrases 'Manage data, records, and automate workflows' name the Zeet domain but rely on generic, abstract verbs ('manage', 'automate') rather than concrete actions, matching the 'names the domain but actions are minimal or generic' anchor rather than the level-3 anchor which requires 1-2 concrete actions.	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 Zeet data'), satisfying the level-4 anchor of having both with the 'when' somewhat generic; it is not level 5 because neither the what nor the trigger phrases are concrete, and the explicit 'Use when...' clause keeps it above the level-3 cap.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Zeet data' supplies the specific keyword 'Zeet' but offers no synonyms or natural variations, fitting the 'some relevant keywords but missing common variations' anchor; it is above level 2 because 'Zeet' is a real, specific trigger rather than a purely generic term.	3 / 5
Distinctiveness Conflict Risk	'Zeet integration' and 'interact with Zeet data' carve a clear brand-specific niche with minimal conflict risk, but the generic action phrasing ('manage data, records, automate workflows') leaves minor overlap risk with adjacent data/integration skills, matching 'mostly distinct; minor overlap risk' rather than the fully-distinct level-5 anchor.	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/zeet/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.