Name: shiphero
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

shiphero

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

Quality

66%

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/shiphero/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 a well-structured, actionable guide with executable commands and a real readiness feedback loop. Remaining gaps are minor: an empty 'Popular actions' section, inconsistent step numbering, and light editorializing.

Suggestions

Populate the 'Popular actions' section with concrete example action names/inputs or remove the redundant header that only repeats the search command.

Fix the step numbering: label 'Step 1' (connect) and 'Step 2' (search/run actions) explicitly and renumber the '1b' subsection so 'skip to Step 2' has a clear target.

Trim editorial asides ('fastest way to get a connection', 'burn less tokens') to tighten token efficiency without losing the command guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with executable snippets, but contains minor editorializing ("This is the fastest way to get a connection", "burn less tokens") and a short concept intro that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides concrete, copy-pasteable membrane commands throughout (login, connection ensure, action list/run, request) with flag tables, but placeholders like CONNECTION_ID/QUERY and a redundant near-empty 'Popular actions' section leave minor gaps versus fully-covered anchor 5.	4 / 5
Workflow Clarity	The install→authenticate→connect→search→run sequence is clear and includes a poll-until-ready feedback loop with state handling (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the dangling 'skip to Step 2' and '1b' labels are inconsistently numbered, a minor clarity gap.	4 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections in a single self-contained file with no external references needed, matching the 'good structure; most content appropriately placed' anchor; it stays at 4 because the file exceeds the 50-line simple-skill threshold that would allow a 5 without file references.	4 / 5
	Total	16 / 20 Passed

Description

57%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 niche target and includes an explicit Use-when trigger, but its capability language is generic. Tightening the action list with concrete ShipHero functions would lift specificity and trigger coverage.

Suggestions

Replace generic verbs with concrete ShipHero capabilities, e.g. 'Manage orders, inventory, products, returns, and purchase orders; fulfill and ship orders.'

Add functional trigger terms users naturally say — 'orders', 'inventory', 'shipping', 'warehouse', '3PL' — alongside the brand name.

Sharpen the 'when' clause to name specific scenarios, e.g. 'Use when the user wants to query or update ShipHero orders, inventory, or shipments.'

Dimension	Reasoning	Score
Specificity	The description names the ShipHero domain but relies on generic verbs ("Manage data, records, and automate workflows") rather than concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor; it does not reach 3 because no genuinely concrete action is enumerated.	2 / 5
Completeness	It supplies both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with ShipHero data"), but neither is as concrete as the anchor-5 example, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	"ShipHero" and "interact with ShipHero data" provide a relevant natural keyword, but functional synonyms a user would say (orders, inventory, shipping, warehouse) are absent, leaving common variations missing as at anchor 3.	3 / 5
Distinctiveness Conflict Risk	"ShipHero" is a distinct proper-noun niche with minimal conflict risk, but the generic action phrasing leaves minor overlap ambiguity versus other integration skills, placing it just below the clearly-distinct anchor 5.	4 / 5
	Total	13 / 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/shiphero/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.