Name: zerotier
Rating: 56.8 (1 reviews)
Author: membranedev

zerotier

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

Quality

65%

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/zerotier/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, actionable guide with executable membrane commands and a real state-polling feedback loop for connection setup. It is held back by an unnecessary ZeroTier explainer and a few loose cross-references ('Step 2') and placeholders.

Suggestions

Remove or condense the introductory paragraph explaining what ZeroTier is; Claude already knows this and it wastes context.

Add a short 'Verify' checkpoint after `membrane action run` (e.g. inspect the `output` field for errors) since action execution can modify or delete network resources.

Resolve the dangling 'skip to Step 2' reference by labeling the sequenced steps explicitly (Step 1 connect, Step 2 search/run).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command documentation, but the opening paragraph ('ZeroTier is a software-defined networking solution...') explains what ZeroTier is — a concept Claude already knows — which is unnecessary padding, matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	It provides concrete, copy-paste-ready membrane commands and a full flags table covering the common cases, but placeholders like CONNECTION_ID and <actionId> must be discovered first, fitting 'Mostly executable guidance; concrete code or commands with minor gaps' rather than the fully self-contained anchor 5.	4 / 5
Workflow Clarity	There is a clear install→authenticate→connect→search→run sequence with an explicit state-polling feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED) for connections, but the 'skip to Step 2' reference has no matching Step 2 heading, leaving a minor validation/sequencing gap.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized into clear sections with one external docs link and no nested references, but at ~140 lines some content (the request flags table, detailed clientAction handling) could arguably live in a separate file, matching 'Good structure; most content is appropriately placed; minor organization gaps'.	4 / 5
	Total	15 / 20 Passed

Description

62%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 is anchored to a distinctive product name. Its main weakness is generic action verbs and a trigger clause that omits the natural ZeroTier vocabulary (networks, members).

Suggestions

Replace generic verbs with concrete ZeroTier actions, e.g. 'Manage ZeroTier networks and members, list nodes, and automate network workflows.'

Broaden the trigger with natural user phrasing: 'Use when the user wants to manage ZeroTier networks, members, or nodes.'

Add file/term synonyms (e.g. 'network IDs', 'member authorization') so the trigger matches how users actually refer to ZeroTier.

Dimension	Reasoning	Score
Specificity	Names the ZeroTier domain and lists several actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, fitting 'Names domain and 1-2 concrete actions, but not comprehensive' better than the more specific anchor 4.	3 / 5
Completeness	It supplies both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with ZeroTier data'), but the 'when' clause could be more specific, matching 'Has both what and when; when could be more explicit or specific' rather than the fully concrete anchor 5.	4 / 5
Trigger Term Quality	The only natural keyword is 'ZeroTier' (repeated as 'interact with ZeroTier data'), missing common variations users would say such as 'networks', 'members', or 'join network', matching 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	ZeroTier is a distinct named product with a brand-specific trigger, giving minimal conflict risk, but the generic 'Manage data, records, and automate workflows' phrasing leaves minor overlap with other integration skills, so anchor 4 fits better than 5.	4 / 5
	Total	14 / 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/zerotier/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.