CtrlK
BlogDocsLog inGet started
Tessl Logo

zooz

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/zooz/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable with executable CLI commands and a well-sequenced connection workflow including state-based feedback loops. Its main weaknesses are minor redundancy and an inconsistent step numbering scheme that slightly obscures the workflow.

Suggestions

Remove the duplicated `action list` command in 'Popular actions' or replace it with a cross-reference to 'Searching for actions' to cut redundancy.

Fix the step numbering (define '1a' before '1b' and add the referenced 'Step 2' header) so the connection workflow sequence is unambiguous.

Consider moving the proxy flags table and action-discovery details into a references file to slim the SKILL.md overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient with command-first guidance, but the opening paragraph explaining what ZOOZ is and the repeated `action list` command in 'Popular actions' (already shown in 'Searching for actions') add padding that could be trimmed.

3 / 5

Actionability

It provides copy-paste-ready commands throughout (install, login, connection ensure, action run, proxy) plus a concrete flags table, fully covering the common cases with executable guidance.

5 / 5

Workflow Clarity

The connection flow is clearly sequenced with polling and explicit state handling (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) as feedback checkpoints, but the step numbering is inconsistent (a '1b' with no visible 1a, an undefined 'Step 2') leaving minor gaps.

4 / 5

Progressive Disclosure

No bundle files exist, so all content lives inline, but it is organized into well-labeled sections (Install, Authentication, Connecting, Searching, Proxy, Best practices) with clear navigation; at ~140 lines some API/flag reference could be split out, which keeps it just below a 5.

4 / 5

Total

16

/

20

Passed

Description

57%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/when structure around a distinctive named product, but its capability language is generic rather than concrete. Tightening the action list to specific ZOOZ operations (payments, refunds, reports) would lift specificity and trigger quality.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete ZOOZ operations such as processing refunds, pulling reports, and managing merchants.

Add natural synonyms and file/endpoint cues users might say (e.g. 'ZOOZ payments', 'refund a transaction', 'ZOOZ reports') to broaden trigger coverage.

Make the 'when' clause more specific about which ZOOZ tasks trigger the skill rather than the broad 'interact with ZOOZ data'.

DimensionReasoningScore

Specificity

The description names the domain ('ZOOZ integration') but its actions are generic ('Manage data, records, and automate workflows') rather than concrete operations, matching the 'names the domain but actions are minimal or generic' anchor and falling well below the multi-action specificity of higher anchors.

2 / 5

Completeness

Both 'what' (ZOOZ integration, manage data/records/workflows) and 'when' ('Use when the user wants to interact with ZOOZ data') are present and explicit, but the 'what' is generic so it does not reach the concrete, comprehensive level of a 5.

4 / 5

Trigger Term Quality

It includes the distinctive product name 'ZOOZ' and a 'Use when... interact with ZOOZ data' trigger, but lacks common synonyms or variations a user might naturally say, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The proper-noun trigger 'ZOOZ' makes it mostly distinct with minimal conflict risk, though the generic 'manage data, records, and automate workflows' phrasing leaves minor overlap with general data-handling skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.