Name: zbrain
Rating: 64.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zbrain

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

Quality

77%

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

Quality

Content

88%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 clearly sequenced, validated connection workflow, scoring well on actionability and workflow clarity. Minor trimming of introductory framing would improve conciseness, and progressive disclosure is adequate for a single-file skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with lean explanations, but the opening "Zbrain is a SaaS platform... Think of it as a company-wide wiki" and editorializing like "so you can focus on the integration logic rather than auth plumbing" are minor padding that could be trimmed. Not 5 because of these few over-explanatory passages.	4 / 5
Actionability	Concrete, copy-paste-ready bash commands appear throughout (install, login, connection ensure, polling, action list/run, request flags) and cover the common cases with explicit flags and placeholders. Fully executable guidance.	5 / 5
Workflow Clarity	The connection flow is explicitly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and feedback loops (poll until ready, re-poll after user action, check the error field). Clear sequence with explicit validation and error recovery.	5 / 5
Progressive Disclosure	The body is a single, well-sectioned file with clear headers (install, auth, connecting, searching, running, proxy, best practices) and no nested references, which is appropriate for a doc of this size. Not 5 because there is no offloading of the larger reference-style material (e.g., the proxy flags table or best practices) into separate files, though none is strictly required.	4 / 5
	Total	18 / 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 is product-distinctive and includes an explicit "Use when" clause covering both what and when, but its actions and trigger terms are generic with little synonym coverage. Tightening the trigger phrases and naming more concrete actions would raise specificity and trigger_term_quality.

Suggestions

Replace generic verbs with concrete Zbrain actions (e.g., "search the knowledge base, create and update documents, query records, trigger workflows") to lift specificity.

Expand the trigger clause with natural phrasings and synonyms users actually say (e.g., "Use when the user wants to search, query, or update Zbrain records, knowledge bases, or documents").

Name the key Zbrain objects (workspace, knowledge base, document, source) in the description so the when clause maps to specific, recognizable triggers.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Zbrain domain and a couple of actions, but the actions are generic and coverage is not comprehensive. It does not reach 4 because no multiple specific concrete actions are enumerated.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Zbrain data"), but the when clause is somewhat generic and echoes the what rather than naming concrete trigger phrases. Not 5 because the trigger guidance lacks specificity.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Zbrain data" provides one natural phrase, but there are no synonyms, variations, or product-specific trigger keywords beyond repeating "Zbrain data." Missing common variations keeps it below 4.	3 / 5
Distinctiveness Conflict Risk	The description is tied to a named product (Zbrain) with Zbrain-specific triggers, giving it a clear niche and minimal conflict risk with other 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/zbrain/SKILL.md
Commit: f484c82

Reviewed: ~23 hours 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.