Name: easyship
Rating: 60.8 (1 reviews)
Author: membranedev

easyship

Easyship integration. Manage Shipments, Trackers, Addresses, Users. Use when the user wants to interact with Easyship data.

Quality

71%

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

Quality

Content

67%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.

A well-structured, actionable CLI integration guide with executable commands and a sensible connection workflow. Its main weakness is conciseness — an unnecessary introductory paragraph and a few padded asides — plus a dangling 'Step 2' reference that breaks the workflow's internal navigation.

Suggestions

Trim the opening marketing paragraph and 'auth plumbing' asides; assume Claude knows what a shipping platform is and start directly with the integration mechanics.

Fix the dangling 'Step 2' reference by adding a labeled '## Step 2' header or rewording the cross-references so the connection workflow is internally navigable.

Add one fully-worked end-to-end example (e.g. connect → request-rates → create-shipment) with real substituted values to lift actionability from concrete-but-templated to copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-oriented sections, but the opening marketing-style paragraph ('Easyship is a shipping platform that helps e-commerce businesses streamline...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need.	3 / 5
Actionability	Provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) with a populated actions table, though placeholders like <actionId> and CONNECTION_ID and the lack of a fully-worked end-to-end example leave minor gaps.	4 / 5
Workflow Clarity	Clear install → login → connect → poll-until-ready → search → run sequence with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, though the dangling 'Step 2' reference (no matching header) and '#### 1b' labeling create a minor sequencing gap.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Working with Easyship, Popular actions, Best practices) in a single file with no bundle references; the inline Popular actions table is sizable but reasonably placed, leaving only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

75%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.

A solid, on-brand description that states both capability and trigger, anchored to the specific Easyship domain. It is concise but the trigger clause is generic and the action list is incomplete relative to the skill's actual coverage.

Suggestions

Expand the 'when' clause with concrete natural-language triggers, e.g. 'Use when the user wants to create shipments, track packages, validate addresses, or manage couriers in Easyship'.

Add the missing capabilities surfaced in the body (rates, couriers, pickups, documents) to the action list for more comprehensive coverage.

Consider naming file extensions or entity synonyms (e.g. 'tracking', 'labels') to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Easyship domain and lists several concrete managed resources ('Shipments, Trackers, Addresses, Users'), but omits other surfaced capabilities like rates, couriers, and pickups, leaving minor coverage gaps.	4 / 5
Completeness	Both 'what' ('Manage Shipments, Trackers, Addresses, Users') and 'when' ('Use when the user wants to interact with Easyship data') are present and explicit, though the 'when' could be more specific with concrete trigger scenarios.	4 / 5
Trigger Term Quality	Includes natural resource terms ('Shipments', 'Trackers', 'Addresses') plus the brand 'Easyship', but the trigger phrase 'interact with Easyship data' is somewhat generic and misses common synonyms like 'track packages' or 'shipping labels'.	4 / 5
Distinctiveness Conflict Risk	The 'Easyship integration' framing and brand-specific resources give it a clear niche with minimal conflict risk, but the generic 'interact with Easyship data' trigger leaves minor overlap risk with other shipping-related skills.	4 / 5
	Total	16 / 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/easyship/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.