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

starshipit

Starshipit integration. Manage Orders, Products, Customers, Users, Integrations. Use when the user wants to interact with Starshipit 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/starshipit/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.

The content is actionable and well-organized with strong executable CLI guidance, but it lacks validation/verification safeguards around its destructive and batch operations, which caps workflow clarity. Splitting the action catalog into a reference file would further improve disclosure.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive or batch actions (e.g., verify the order id with get-order before delete-order, and confirm counts before manifest-orders) to lift workflow clarity above the cap.

Fill the empty Description column in the popular-actions table or move the catalog to a references/actions.md file with a one-line pointer from SKILL.md.

Clarify the relationship between the table "Key" (e.g. print-label) and the "<actionId>" expected by `membrane action run`, so users know how to resolve an id from `action list`.

Dimension	Reasoning	Score
Conciseness	The body is lean and CLI-focused with no generic concept padding; minor trimmable fluff (e.g., "so you can focus on the integration logic rather than auth plumbing") and an empty Description column in the popular-actions table keep it just below a 5.	4 / 5
Actionability	Copy-paste-ready commands cover install, headless login, connection ensure/poll, action list/run with JSON params, and proxy requests with a full flag table; minor gaps are the blank action descriptions and the unclarified actionId-vs-Key distinction.	4 / 5
Workflow Clarity	The connection sub-flow is well sequenced with state checkpoints and a re-poll feedback loop, but the skill exposes destructive/batch actions (Delete Order, Delete Product, Manifest Orders) with no validation or verification step before execution, triggering the destructive/batch cap at 3.	3 / 5
Progressive Disclosure	A single self-contained SKILL.md with clear section headers and one-level-only structure; the 20-row action catalog is inline and could be a separate reference, but it is useful as quick reference, fitting anchor 4.	4 / 5
	Total	15 / 20 Passed

Description

73%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 clearly identifies a distinctive niche and provides an explicit Use-when clause, but its action vocabulary is generic ("Manage") and it omits several core shipping concepts. It is solid but could be sharper and more comprehensive.

Suggestions

Replace the generic verb "Manage" with concrete actions a user would request (e.g., create/update/delete orders, print labels, track shipments, get rates) to lift specificity.

Add the missing core shipping entities (Shipments, Labels, Tracking, Carriers, Rates) to broaden trigger-term coverage.

Expand the "Use when" clause with concrete trigger phrases (e.g., "when the user wants to print shipping labels, track a shipment, or get delivery rates").

Dimension	Reasoning	Score
Specificity	"Manage Orders, Products, Customers, Users, Integrations" enumerates five concrete domains but relies on a single generic verb ("Manage") rather than several distinct actions, matching anchor 3.	3 / 5
Completeness	Both "what" (Starshipit integration, manage listed entities) and "when" ("Use when the user wants to interact with Starshipit data") are present, but the trigger is a single generic phrase rather than multiple concrete ones.	4 / 5
Trigger Term Quality	The distinctive brand term "Starshipit" plus entity names and "interact with Starshipit data" give good keyword coverage, though core shipping terms (shipments, labels, tracking, rates) are absent.	4 / 5
Distinctiveness Conflict Risk	"Starshipit" is a highly specific named SaaS niche with distinct triggers and minimal overlap risk with other skills.	5 / 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/starshipit/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.