Name: zeta
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

zeta

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

Quality

72%

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

Quality

Content

82%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 highly actionable, well-sequenced integration guide with copy-paste commands and a genuine state-polling feedback loop for connection readiness. Its only weak spots are minor padded prose and a slightly inconsistent step-numbering scheme.

Suggestions

Fix the step numbering: label the initial connection step as "Step 1" so the "skip to Step 2" references resolve, or relabel the readiness section without the orphaned "1b" prefix.

Trim editorial filler such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" to tighten token efficiency.

Add a short validation note for the proxy path (e.g. check HTTP status / error field before treating output as success) to give the raw-request workflow an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	The body delivers efficient operational guidance for an unfamiliar CLI, with copy-paste commands earning their tokens; only minor prose ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way") could be trimmed, fitting the efficient-with-minor-over-explanation anchor.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases — install, login, connection ensure, action list/run, and request proxy — plus a concrete flags table, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connect-to-run flow is clearly sequenced with a real feedback loop (poll --wait, then branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-poll), but "skip to Step 2" is referenced without a labeled Step 1, leaving a minor clarity gap below 5.	4 / 5
Progressive Disclosure	No bundle files exist, so the skill is a single self-contained guide; it is well-sectioned into cohesive stages (install, auth, connect, search, run, proxy, best practices) with content appropriately inline, fitting the good-structure anchor rather than the separate-file reference pattern of 5.	4 / 5
	Total	17 / 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 is compact and correctly pairs a what-statement with an explicit Use-when trigger, anchored by a distinctive brand name. Its main weakness is generic action language ("manage data/records") that blunts specificity and trigger-term richness.

Suggestions

Replace generic verbs with concrete Zeta capabilities (e.g. "create and approve expense cards, submit and reconcile expense reports, query spending transactions") to lift specificity.

Add natural user phrasing and synonyms to the trigger clause, e.g. "Use when the user wants to manage Zeta expenses, cards, or spending data."

Tighten the "when" with concrete triggers like "when the user mentions Zeta cards, expense reports, or employee spending" to approach a 5 on completeness.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Zeta domain and a few actions, but the verbs ("manage data", "manage records") are generic rather than concrete, matching the 1-2-concrete-actions anchor rather than the comprehensive 5.	3 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and an explicit "Use when the user wants to interact with Zeta data" clause are present; the "when" is explicit but generic, so it sits below the fully-concrete-trigger anchor of 5.	4 / 5
Trigger Term Quality	It surfaces "Zeta", "data", "records", and "workflows" with an explicit "interact with Zeta data" trigger, but lacks synonyms or natural variations a user might actually say, fitting the some-keywords-missing-synonyms anchor.	3 / 5
Distinctiveness Conflict Risk	"Zeta" is a named product giving it a clear niche and low conflict risk, but the generic action verbs ("manage data/records") leave minor overlap risk with adjacent data skills, keeping it just below 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/zeta/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.