Name: zenkit
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zenkit

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

Quality

66%

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/zenkit/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.

A well-structured, highly actionable integration skill with concrete CLI commands and a validated connection workflow; its main weakness is mild over-explanation of Zenkit/Membrane context that could be trimmed.

Suggestions

Trim the introductory 'Zenkit is a project management...' paragraph and the 'so you can focus on the integration logic' commentary to assume Claude's familiarity.

Fix the 'skip to Step 2' reference by labeling the matching section (e.g. '## Step 2: Search and run actions') so the sequence is unambiguous.

Consider moving the proxy request flag table and connection-state reference into a separate reference file to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content, but the opening 'Zenkit is a project management...' paragraph and phrasing like 'so you can focus on the integration logic rather than auth plumbing' explain context Claude largely already knows.	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests plus a flag table, with only minor gaps (placeholder substitution paths like CONNECTION_ID).	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with polling checkpoints and state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), though it references an unlabeled 'Step 2' that slightly muddies the sequence.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no inlined bulk reference material; as a single-file skill it is appropriately structured, though some content (proxy flags, state handling) could optionally live in reference files.	4 / 5
	Total	15 / 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.

A competent third-person description that covers what and when with a clear app-specific niche, but its action verbs and trigger terms are generic and could name concrete Zenkit entities and common user phrases.

Suggestions

Replace generic verbs with concrete Zenkit operations, e.g. 'Create and update collections, list items, comments, and reports; automate workflows'.

Expand the trigger clause with natural terms users say, e.g. 'Use when the user wants to manage Zenkit tasks, projects, collections, lists, or kanban boards'.

Name specific Zenkit objects (collections, items, views) to sharpen distinctiveness and specificity.

Dimension	Reasoning	Score
Specificity	Names the Zenkit domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete operations like create/update/delete on specific entities.	3 / 5
Completeness	Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Zenkit data'), though the when clause is somewhat generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes a natural trigger ('Use when the user wants to interact with Zenkit data') and the 'Zenkit' keyword, but misses common task synonyms users would say (tasks, projects, lists, collections, kanban).	3 / 5
Distinctiveness Conflict Risk	The app-specific 'Zenkit integration' naming and Zenkit-keyed trigger give it a clear niche with minimal risk of firing for unrelated skills.	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/zenkit/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.