Name: zenler
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zenler

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

Quality

61%

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

Quality

Content

62%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 delivers executable CLI guidance and a serviceable connection workflow, but it inlines reference-style material in one file and omits validation/verification steps for the destructive proxy and action-run operations, capping workflow clarity. It is actionable but not maximally lean or well-staged.

Suggestions

Add explicit validation/verification steps after `membrane action run` and proxy requests (e.g. check the `output`/response status before proceeding) to lift workflow clarity above 3.

Move the proxy flag table and clientAction schema details into a separate reference file referenced one level deep, keeping SKILL.md a concise overview.

Reorder so 'Running actions' precedes 'Popular actions', and remove the duplicated action-list instruction to reduce padding.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with command blocks and short explanations that assume competence, though introductory framing ('Zenler is a platform for creators...') and the repeated action-list instruction add minor padding that could be trimmed.	4 / 5
Actionability	It provides concrete, executable `membrane` CLI commands with flags and JSON examples covering connection, action search/run, and proxy requests, with only minor gaps such as placeholder substitution for CONNECTION_ID and actionId.	4 / 5
Workflow Clarity	A rough connection-to-action sequence exists with state handling, but destructive/batch operations (action run, proxy requests) lack validation checkpoints, and the section ordering jumps (Popular actions appears before Running actions) creating implicit gaps.	3 / 5
Progressive Disclosure	Content is organized into clear sections but everything is inlined into a single SKILL.md with no separate reference files, so API-like detail (proxy flag tables, clientAction schemas) that could live one level deep is kept inline.	3 / 5
	Total	14 / 20 Passed

Description

60%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 names a distinct domain and includes an explicit 'Use when' trigger, satisfying basic completeness, but its action verbs are generic and the trigger terms miss the natural domain vocabulary (courses, memberships, funnels). It is clear but not comprehensive.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Zenler operations such as creating courses, managing enrollments, or sending email broadcasts.

Expand trigger terms to include natural user phrasings like 'Zenler courses', 'memberships', 'funnels', or 'Zenler students' so the skill matches real requests.

Tighten the 'Use when' clause to reference specific intents (e.g. 'Use when the user wants to manage Zenler courses, lessons, users, or orders').

Dimension	Reasoning	Score
Specificity	It names the Zenler domain and lists a few concrete actions ('Manage data, records, and automate workflows') but the actions are generic ('manage', 'automate') rather than comprehensive specific operations like creating courses or processing orders.	3 / 5
Completeness	It provides a clear 'what' (Zenler integration to manage data/records/workflows) and an explicit 'when' trigger ('Use when the user wants to interact with Zenler data'), though the 'when' could name more specific intents.	4 / 5
Trigger Term Quality	It surfaces the natural term 'Zenler' and 'Zenler data', but misses common phrasings users would say (courses, memberships, funnels, subscriptions) and lacks synonyms or file extensions, so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	The Zenler niche is fairly distinct with the named trigger term 'Zenler', giving minimal conflict risk with other skills, though 'manage data, records, workflows' is broad enough for minor overlap.	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/zenler/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.