Name: megaventory
Rating: 60 (1 reviews)
Author: membranedev

megaventory

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

Quality

70%

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/megaventory/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 content is highly actionable with concrete, copy-paste Membrane CLI commands and a well-defined connection-state feedback loop. Its main weaknesses are minor redundancy and inconsistent step numbering that slightly weakens workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, command-driven prose with brief explanations, but includes minor redundancy (the action-list command appears in both 'Searching for actions' and 'Popular actions') and a one-line product preamble that could be trimmed, matching the efficient-but-slightly-trimmable score-4 anchor.	4 / 5
Actionability	Commands are concrete and copy-paste ready — install, login, connection ensure, action list/run, and a proxy flags table — and cover the common cases with executable syntax and documented options, matching the fully-executable score-5 anchor.	5 / 5
Workflow Clarity	The connect step has an explicit state machine with a poll/retry feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the step numbering is inconsistent ('1b' and 'Step 2' with no labeled Step 1), matching the clear-sequence-with-minor-gaps score-4 anchor rather than score-5.	4 / 5
Progressive Disclosure	No bundle files exist and the single document is well-organized into clearly headed sections with no nested references, but some content (the full connection state machine and proxy flag table) is inlined where a separate reference could help, matching the good-structure score-4 anchor.	4 / 5
	Total	17 / 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 clearly names the target product and includes an explicit 'Use when' trigger, but the capability verbs are generic and the trigger lacks natural synonyms like inventory or stock. It is functional but not maximally specific.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Megaventory actions such as tracking stock levels, creating purchase/sales orders, and running stocktakes.

Expand the trigger clause with natural user phrasing: 'Use when the user wants to manage inventory, stock levels, purchase orders, or sales orders in Megaventory.'

Add a brief mention of the supported entity types (Products, Suppliers, Purchase Orders, etc.) so the description signals scope at a glance.

Dimension	Reasoning	Score
Specificity	It names the domain (Megaventory) but the actions — 'Manage data, records, and automate workflows' — are minimal and generic, matching the score-2 anchor of naming the domain with generic actions rather than the score-3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and 'when' (use when the user wants to interact with Megaventory data) are present, but the 'when' could be more explicit about specific scenarios, matching the score-4 anchor rather than the fully concrete score-5 anchor.	4 / 5
Trigger Term Quality	'Use when the user wants to interact with Megaventory data' supplies a relevant keyword but misses common natural synonyms a user might say (inventory, stock, orders, purchase orders), matching the score-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Megaventory gives it a clear niche with minimal conflict risk, though the generic 'manage data' phrasing leaves minor overlap with adjacent integration skills, matching score-4 rather than the score-5 clear-niche anchor.	4 / 5
	Total	13 / 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/megaventory/SKILL.md
Commit: f484c82

Reviewed: 6 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.