Name: shipstation
Rating: 62.4 (1 reviews)
Author: membranedev

shipstation

ShipStation integration. Manage Orders, Products, Customers, Warehouses, Users, Stores and more. Use when the user wants to interact with ShipStation data.

Quality

73%

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

Quality

Content

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

Highly actionable CLI guidance with a well-structured connection workflow, weakened by an unnecessary intro paragraph and a lack of validation steps around destructive actions. No bundle files are referenced, so disclosure is single-file and reasonably organized.

Suggestions

Trim or remove the introductory paragraph describing what ShipStation is and who uses it — Claude already knows this and it competes for context.

Add a validation/verification checkpoint before and after destructive actions (e.g., confirm the order ID with the user before delete-order, and check the response output/status after void-label) to lift workflow clarity past the destructive-operation cap.

Consider moving the full popular-actions table and the proxy flag reference into a separate REFERENCE.md so the body stays a lean overview, which would also improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient CLI commands and tables, but the opening paragraph explains what ShipStation is and who uses it ('web-based shipping software that helps e-commerce businesses...') — background Claude does not need and could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) plus a popular-actions table covering common cases with concrete keys.	5 / 5
Workflow Clarity	The connection flow has good checkpoints (READY/BUILDING polling, CLIENT_ACTION_REQUIRED, error states), but destructive/batch actions like delete-order and void-label are run with no validation or verification of the result, capping this dimension at 3.	3 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no nested references; the bulky actions table and proxy flag list are inlined but the structure is easy to navigate.	4 / 5
	Total	15 / 20 Passed

Description

78%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 description that names the product and several entities plus an explicit 'Use when' clause. It is distinct and reasonably specific, but the generic 'Manage' verb and broad 'interact with ShipStation data' trigger keep it just below top marks.

Suggestions

Replace the generic 'Manage' with a few concrete verbs (e.g., 'list, create, update, and delete Orders, Products, Customers') to lift specificity.

Sharpen the trigger clause with concrete phrases users say, e.g. 'Use when the user wants to list or fulfill ShipStation orders, track shipments, or manage products and customers.'

Drop 'and more' or replace it with the remaining entities so coverage reads as comprehensive rather than open-ended.

Dimension	Reasoning	Score
Specificity	Lists several concrete entities to manage ('Orders, Products, Customers, Warehouses, Users, Stores') but the repeated verb 'Manage' is generic and 'and more' signals coverage gaps, stopping short of comprehensive.	4 / 5
Completeness	Has both a clear 'what' (ShipStation integration managing listed entities) and an explicit 'when' clause ('Use when the user wants to interact with ShipStation data'), but the trigger is generic rather than concrete specific phrases.	4 / 5
Trigger Term Quality	Includes the natural product name 'ShipStation' plus common entity keywords users would say (Orders, Products, Customers), but offers no synonyms or variants and 'interact with ShipStation data' is broad.	4 / 5
Distinctiveness Conflict Risk	Names the specific product 'ShipStation' with entity-specific triggers, creating a clear niche with minimal risk of firing for the wrong skill.	5 / 5
	Total	17 / 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/shipstation/SKILL.md
Commit: f484c82

Reviewed: ~19 hours 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.