Name: shipamax
Rating: 59.2 (1 reviews)
Author: membranedev

shipamax

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

Quality

68%

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

Quality

Content

75%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 an efficient, highly actionable CLI integration guide with a clear multi-step workflow and a real polling/validation feedback loop, organized under clear section headers. Its main gaps are minor: loose step numbering, an inconsistent `npx` vs `membrane` invocation style, and a small amount of introductory prose that could be trimmed.

Suggestions

Fix the step numbering so the "skip to Step 2" reference resolves to an actual labeled "Step 2" header (e.g. "## Step 2: Search for and run actions").

Standardize command invocation: pick either `membrane` (after install) or `npx @membranehq/cli@latest` and use it consistently across examples.

Trim the opening marketing paragraph and the "auth plumbing" aside; lead with what Claude needs to do rather than what Shipamax/Membrane is.

Dimension	Reasoning	Score
Conciseness	The body is largely tight, command-focused content, with only minor over-explanation such as the introductory marketing prose ("focus on the integration logic rather than auth plumbing"), matching anchor 4's "efficient; minor instances of over-explanation that could be trimmed" rather than the fully lean anchor 5.	4 / 5
Actionability	Concrete, copy-paste-ready CLI commands appear throughout (install, login, connection ensure, action list/run, request), but placeholders like CONNECTION_ID and inconsistent use of `npx @membranehq/cli` vs `membrane` introduce minor gaps, fitting anchor 4 rather than the fully covered anchor 5.	4 / 5
Workflow Clarity	A clear install → login → connect → poll → search → run sequence exists with a genuine feedback loop (poll until READY, re-poll after CLIENT_ACTION_REQUIRED, inspect the error field), but loose numbering ("skip to Step 2" with no Step 2 header) is a minor gap, placing it at anchor 4 rather than the checklist-level anchor 5.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline, but the body is organized with clear, well-signaled section headers (Overview, Working with Shipamax, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices); at ~140 lines with some dense inline reference material (the proxy flag table, detailed state handling) it fits anchor 4 rather than the ideally-split anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

62%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 answers both what the skill does and when to use it with an explicit trigger clause, and the named platform gives it strong distinctiveness. Its main weakness is generic, non-concrete action language and limited trigger-term coverage.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Extract data from shipping invoices and booking confirmations, manage shipments and bookings, and automate freight-forwarding workflows."

Expand trigger terms to natural variations users say, e.g. "Use when the user mentions Shipamax, freight forwarding, shipping documents, invoices, bookings, or shipments."

Tighten the "what" so it reflects the document-extraction and integration actions described in the body rather than the vague "manage data, records".

Dimension	Reasoning	Score
Specificity	Names the domain (Shipamax) and a few actions ("Manage data, records, and automate workflows"), but the actions are generic verbs rather than concrete operations, fitting anchor 3 rather than the more specific anchor 4 or the minimal/generic anchor 2.	3 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Shipamax data") are present and explicit, but the "what" is generic and the trigger could be more specific, so it lands at anchor 4 rather than the fully concrete anchor 5.	4 / 5
Trigger Term Quality	The phrase "interact with Shipamax data" supplies the natural keyword "Shipamax", but common variations a user might say (freight, shipping, booking, shipment) are absent, matching anchor 3's "some relevant keywords but missing common variations".	3 / 5
Distinctiveness Conflict Risk	The named platform "Shipamax" creates a clear niche with Shipamax-specific triggers (minimal conflict), but the generic "manage data, records, automate workflows" phrasing carries minor overlap risk with other data-management skills, placing it at anchor 4 rather than 5.	4 / 5
	Total	14 / 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/shipamax/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.