Name: wesupply
Rating: 53.6 (1 reviews)
Author: membranedev

wesupply

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

Quality

60%

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

Quality

Content

71%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 Membrane CLI commands and a well-sequenced connection workflow including state validation, but it is somewhat verbose in its intro and is monolithic with no progressive disclosure into reference files.

Suggestions

Trim the marketing-style WeSupply intro and redundant 'fastest way to get a connection' sentences to improve token efficiency.

Fix the inconsistent step numbering (1b without 1a, 'Step 2' without a numbered parent) so the workflow sequence is unambiguous.

Move the detailed connection state machine and the full `membrane request` flag table into a references file and link to it from the body.

Dimension	Reasoning	Score
Conciseness	Quotes "WeSupply is a returns management platform that helps e-commerce businesses streamline and automate their returns process... improve customer satisfaction and reduce the costs associated with returns" and "This is the fastest way to get a connection" — mostly efficient CLI guidance, but the marketing-style intro, a few padded sentences, and a duplicated `action list` command could be trimmed. It does not reach 4 because several sentences add explanation rather than instruction.	3 / 5
Actionability	Quotes copy-paste ready commands such as `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://wesupplylabs.com/" --json`, `membrane action run <actionId> --connectionId=CONNECTION_ID --input '{...}' --json`, plus a flag table for `membrane request` — fully executable guidance covering the common cases. No gaps justify a lower score.	5 / 5
Workflow Clarity	Quotes a clear sequence (install → login → `connection ensure` → poll `connection get --wait` → `action list` → `action run`/`request`) with explicit state checks (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) acting as validation checkpoints and a re-poll feedback loop. It stops at 4 because step labels are inconsistent ('#### 1b' with no 1a, references to 'Step 2' without a numbered parent structure).	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent), and the body is a single monolithic document inlining the full connection state machine, proxy flag table, and best practices under clear headers. Structure is decent but content that could be split into reference files is inlined with no external references, fitting 'Some structure but could be better organized' rather than 4.	3 / 5
	Total	15 / 20 Passed

Description

48%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 includes an explicit 'Use when' trigger and names the WeSupply platform, giving reasonable distinctiveness and completeness, but the stated capabilities are generic ('manage data, records, automate workflows') rather than concrete returns-management actions.

Suggestions

Replace generic verbs with concrete WeSupply capabilities, e.g. 'Initiate and track returns, manage shipments and inquiries, and issue refunds or exchanges.'

Add natural trigger terms users actually say, such as 'returns', 'refunds', 'shipments', or 'order returns' alongside 'WeSupply'.

Tighten the 'what' so it clearly enumerates what the skill does rather than 'Manage data, records, and automate workflows'.

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" — it names the WeSupply domain but the actions are minimal and generic (manage, automate) rather than concrete capabilities, matching the anchor 'Names the domain but actions are minimal or generic.' It does not reach 3 because no concrete, specific actions (e.g. initiate returns, track shipments, issue refunds) are named.	2 / 5
Completeness	Quotes "WeSupply integration. Manage data, records, and automate workflows" as a vague 'what' and "Use when the user wants to interact with WeSupply data" as an explicit 'when'. Both are present so it clears the missing-trigger cap, but the 'what' is generic rather than concrete, fitting the lower end of 'Has both what and when' rather than a clear 4.	3 / 5
Trigger Term Quality	Quotes "interact with WeSupply data" and "Manage data, records, and automate workflows" — the WeSupply brand plus 'data/records/workflows' give some relevant keywords but miss the natural returns-specific phrases users would say (returns, shipments, refunds, exchanges). It is above 2 because 'WeSupply' is a real natural term, but below 4 given the missing domain synonyms.	3 / 5
Distinctiveness Conflict Risk	Quotes "WeSupply integration" and "interact with WeSupply data" — naming a specific platform gives a clear niche with low conflict risk, but the generic action language (manage data, records, workflows) keeps minor overlap risk with broad data skills, so it sits at 'Mostly distinct; minor overlap risk' rather than 5.	4 / 5
	Total	12 / 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/wesupply/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.