CtrlK
BlogDocsLog inGet started
Tessl Logo

zencom

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

62

Quality

74%

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/zencom/SKILL.md
SKILL.md
Quality
Evals
Security

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 highly actionable with copy-paste CLI commands and a well-sequenced connection workflow with state validation; its main weaknesses are minor redundant sections and a few over-explanatory sentences.

Suggestions

Merge the redundant "Popular actions" section into "Searching for actions" to remove the repeated discovery command.

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

DimensionReasoningScore

Conciseness

The body is mostly lean command-and-flag content, with only minor over-explanation such as "so you can focus on the integration logic rather than auth plumbing", fitting the efficient-with-minor-trim anchor.

4 / 5

Actionability

It provides copy-paste-ready commands for every operation (login, connection ensure, action run, request) plus a full flag table, matching the fully-executable anchor covering common cases.

5 / 5

Workflow Clarity

The connection setup is a clear sequenced flow with state-check feedback loops (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR and poll-again), but the "Popular actions" section is redundant with "Searching for actions", leaving minor gaps.

4 / 5

Progressive Disclosure

Content is well-organized into clear sections with no need for external bundle files (none present), but everything is inline with minor organization redundancy, matching the good-structure anchor.

4 / 5

Total

17

/

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 answers both what and when and is clearly distinct via the ZEN.COM brand, but its capability list and trigger terms are generic rather than specific concrete actions or natural synonyms.

Suggestions

Replace generic verbs ("Manage data", "automate workflows") with concrete ZEN.COM capabilities such as multi-currency accounts, money transfers, and payment cards.

Add natural trigger phrases users would say, e.g. "Use when the user wants to check a ZEN.COM balance, send a transfer, or manage cards."

DimensionReasoningScore

Specificity

Names the ZEN.COM domain and lists actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete capabilities, matching the anchor for domain + 1-2 generic actions.

3 / 5

Completeness

Explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with ZEN.COM data"), but the when trigger is somewhat generic rather than concrete, matching the both-present-but-could-be-more-explicit anchor.

4 / 5

Trigger Term Quality

Includes the natural keyword "ZEN.COM data" and "interact with ZEN.COM data", but lacks synonyms or variations a user might say, fitting the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

The ZEN.COM brand names a clear niche with distinct triggers and minimal overlap risk with other skills, matching the clear-niche anchor.

5 / 5

Total

15

/

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.