Name: shipperhq
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

shipperhq

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

Quality

61%

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

Quality

Content

65%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 highly actionable with copy-paste CLI commands and a sensible connection-state workflow, but it pads tokens with a long feature list and lacks validation checkpoints for destructive operations. Splitting deeper material into reference files would improve progressive disclosure.

Suggestions

Add a validation/verification checkpoint before destructive proxy or batch operations (e.g. confirm the method and target, or dry-run where supported) to lift the workflow_clarity cap.

Move the 30-item feature inventory into a separate reference file and keep a concise overview inline to improve conciseness and progressive disclosure.

Label the referenced "Step 2" explicitly (the text says "skip to Step 2" but no Step 2 header exists) to fix the navigation gap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but the 30-item feature bullet wall and the opening "what is ShipperHQ" paragraph add unnecessary padding. Not a 4 because those sections could be trimmed without losing clarity.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with flags and a proxy options table covering common cases. Not below 5 because guidance is complete and concrete.	5 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence with state-handling feedback (BUILDING/CLIENT_ACTION_REQUIRED/error), but destructive/batch-capable operations (proxy DELETE, the listed Batches feature) lack validation checkpoints, capping this at 3 per the rubric.	3 / 5
Progressive Disclosure	Good section organization but everything is inline with no reference files, and the skill exceeds 50 lines so the simple-skill exception does not apply. Not a 4 because the feature wall and detailed reference material could be split into separate files.	3 / 5
	Total	14 / 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 has an explicit use-trigger and names a distinct platform, but its capability phrasing is generic rather than concrete, weakening specificity and trigger coverage. It is solid but leaves room for sharper, more action-oriented wording.

Suggestions

Replace generic verbs with concrete ShipperHQ actions (e.g. "query shipping rates, manage carriers and shipping rules, process orders and shipments").

Add natural trigger synonyms users say, such as "shipping rates", "carriers", or "shipping zones", to broaden keyword coverage.

Tighten the "Use when" clause to reference specific ShipperHQ tasks rather than the vague "interact with ShipperHQ data".

Dimension	Reasoning	Score
Specificity	Names the domain ("ShipperHQ integration") but the actions ("Manage data, records, and automate workflows") are minimal and generic rather than concrete. It sits below 3 because no specific concrete action like "extract" or "create" is given.	2 / 5
Completeness	Both a "what" (ShipperHQ integration, manage data/records/workflows) and an explicit "Use when the user wants to interact with ShipperHQ data" trigger are present. Not a 5 because the "what" is generic and the "when" could be more specific.	4 / 5
Trigger Term Quality	"ShipperHQ" and "data" are relevant keywords users would say, but common domain synonyms (shipping rates, carriers, shipping rules) are missing. Not a 4 because coverage is thin and lacks variations.	3 / 5
Distinctiveness Conflict Risk	The named platform "ShipperHQ" gives a clear niche with a distinct trigger, but the generic action verbs (manage data, automate workflows) create minor overlap risk with other data-management skills. Not a 5 because of that generic action phrasing.	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/shipperhq/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.