CtrlK
BlogDocsLog inGet started
Tessl Logo

vend

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

63%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 solid, actionable guide to the Membrane CLI workflow for Vend, with executable commands and a clear connection state machine. Its main weaknesses are a token-heavy entity list dump and no offloading of reference material to bundled files.

Suggestions

Move the ~60-item entity catalog into a references file (e.g. references/entities.md) and link to it from the overview to reduce inline tokens.

Remove the redundant 'Popular actions' section and the filler line 'Use action names and parameters as needed.' to tighten the body.

Add an explicit numbered runbook with a validation checkpoint (e.g. poll until state == READY before calling action list/run) to lift workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the ~60-item flat entity bullet list and redundant filler like 'Use action names and parameters as needed' and a duplicate action-list command under 'Popular actions' consume tokens without earning them.

3 / 5

Actionability

Provides concrete copy-paste-ready CLI commands (install, login, connection ensure, action list/run, request) plus a flags table covering common cases; minor gaps such as placeholder action IDs keep it just below fully executable 5.

4 / 5

Workflow Clarity

Sequences install → login → connect → search → run with polling/state checkpoints (READY, CLIENT_ACTION_REQUIRED) and a re-poll feedback loop; not a numbered checklist with explicit validation, so it stays at 4 rather than 5.

4 / 5

Progressive Disclosure

Content is sectioned but the large entity catalog and reference-style material are inlined into SKILL.md with no external references; at ~225 lines it exceeds the under-50-line simple-skill exception, so the inlined bulk caps it at 3.

3 / 5

Total

14

/

20

Passed

Description

73%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 functional: it names a distinct niche (Vend) and provides an explicit 'Use when' trigger, satisfying both what and when. Its weakness is generic action verbs that under-specify the skill's concrete capabilities.

Suggestions

Replace generic verbs with concrete actions, e.g. 'List and update Vend products, sales, inventory, and customers; run Vend API actions.'

Add natural trigger synonyms users might say, such as 'point-of-sale', 'POS', or 'VendHQ' data.

DimensionReasoningScore

Specificity

Quotes 'Manage data, records, and automate workflows' — it names the Vend domain and a few actions, but the actions are generic ('manage', 'automate') rather than concrete, matching the 1-2-actions-not-comprehensive anchor.

3 / 5

Completeness

Explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Vend data'); the 'what' is somewhat vague, so it does not reach the concrete-trigger-phrase level of 5.

4 / 5

Trigger Term Quality

Includes natural terms a user would say — 'Vend', 'Vend data', 'records', 'workflows' — giving good coverage; falls short of 5 because there are no synonyms or file/extension variations, expected for a single-app integration.

4 / 5

Distinctiveness Conflict Risk

'Vend integration' carves a clear niche around a specific named product, making it highly distinguishable with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.