Name: shipworks
Rating: 56.8 (1 reviews)
Author: membranedev

shipworks

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

Quality

64%

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

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 delivers concrete, executable Membrane CLI commands and a well-checkpointed connection workflow, but it carries a padded entity enumeration and a generic intro and does not split detail into reference files. Trimming the inline bulk and extracting the entity catalog would improve both conciseness and progressive disclosure.

Suggestions

Cut the 'ShipWorks is a desktop e-commerce shipping solution...' intro paragraph; assume Claude knows the product or compress it to one line.

Move the 30-line entity/resource enumeration into a reference file (e.g. RESOURCES.md) and link to it, leaving the overview a concise index.

Add a brief verify step after running actions (e.g., check the `output`/`error` fields) to close the action-run loop and lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The guidance is mostly efficient CLI instruction, but the 30-line enumeration of entity names (Orders, Customers, Products, ...) and the introductory 'what ShipWorks is' paragraph are padded content Claude could do without, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Concrete, executable commands appear throughout (membrane login, connection ensure, action list/run, request) with flags and a proxy-options table, matching 'mostly executable guidance; concrete code or commands with minor gaps'; placeholders like CONNECTION_ID and QUERY keep it just short of fully copy-paste ready.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-after-user-action feedback loop, fitting 'clear sequence with most checkpoints present'; it lacks a final verify step for some paths, so it does not reach score 5.	4 / 5
Progressive Disclosure	Sections are clearly headed, but the file is monolithic with no reference files and the bulk entity index is inlined rather than split out, fitting 'some structure but could be better organized; content that should be separate is inline' rather than the well-split structure at score 4.	3 / 5
	Total	14 / 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 cleanly states a distinct named-app niche and includes an explicit 'Use when' trigger, but its action list is generic and it relies on a single keyword. Tightening the 'what' with concrete ShipWorks actions would lift specificity and completeness.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete ShipWorks actions (e.g., 'query orders, customers, and shipments; print labels; update order status') to raise specificity.

Expand trigger terms beyond a single keyword by adding natural phrases users say (e.g., 'shipping labels', 'order status', 'ShipWorks .xlsx exports').

Make the 'when' clause more concrete by tying it to the specific tasks users perform, not just 'interact with ShipWorks data'.

Dimension	Reasoning	Score
Specificity	It names the domain ('ShipWorks integration') and lists a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor and falling short of the multi-action coverage at score 4.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with ShipWorks data') are present, but the 'what' is generic and the trigger could be more specific, so it does not reach the concrete-trigger-phrase level of score 5.	4 / 5
Trigger Term Quality	The only natural keyword is 'ShipWorks' (repeated as 'ShipWorks data'), with no synonyms or variations, fitting 'some relevant keywords but missing common variations or synonyms' rather than the broader coverage at score 4.	3 / 5
Distinctiveness Conflict Risk	ShipWorks is a named niche product with a distinct trigger ('ShipWorks' / 'ShipWorks data') and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	15 / 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/shipworks/SKILL.md
Commit: f484c82

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