Name: shipcloud
Rating: 64 (1 reviews)
Author: membranedev

shipcloud

Shipcloud integration. Manage Shipments, Trackings, Carriers, Services, Labels, Pickups and more. Use when the user wants to interact with Shipcloud data.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/shipcloud/SKILL.md

Quality

Content

73%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 strong, executable guide with an excellent connection-state workflow and feedback loops. Its main weakness is token efficiency: an introductory concept dump and motivational phrasing add tokens Claude does not need.

Suggestions

Trim the opening paragraph ("Shipcloud is a shipping platform...") and motivational phrases like "so you can focus on the integration logic rather than auth plumbing"; Claude already knows what a shipping platform is.

Remove low-value filler such as "Use action names and parameters as needed."

Optionally move the proxy request flag table and detailed clientAction field descriptions into a references/ file to shorten the main body while keeping it one level deep.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content, but padded with an unnecessary intro paragraph explaining what Shipcloud is and rhetorical flourishes like "so you can focus on the integration logic rather than auth plumbing."	3 / 5
Actionability	Provides concrete, copy-paste-ready membrane CLI commands with flags, JSON examples, and a flag table, with only minor gaps around interpreting output schemas.	4 / 5
Workflow Clarity	Clear multi-step sequence from install through connection-state handling, with an explicit state machine and feedback loops (poll again after user completes the action) for error recovery.	5 / 5
Progressive Disclosure	Well-organized into clear single-level sections with no nested references and easy navigation, though the ~150-line self-contained file inlines some CLI reference material that could optionally live in a reference file.	4 / 5
	Total	16 / 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.

The description is specific, well-structured, and uses correct third-person voice with an explicit Use-when clause. It is held back from the top band by the generic verb "Manage," the "and more" hedge, and a broad trigger phrase rather than concrete trigger terms.

Suggestions

Replace the single verb "Manage" with a few specific concrete verbs (e.g., "Create and track Shipments, generate Labels, schedule Pickups, query Carriers and Services").

Tighten the trigger clause to concrete phrases a user would say, e.g. "Use when the user wants to create shipments, print shipping labels, track packages, or schedule carrier pickups via Shipcloud."

Drop the "and more" hedge or replace it with the remaining named capabilities so coverage reads as comprehensive.

Dimension	Reasoning	Score
Specificity	Names multiple concrete Shipcloud resources ("Shipments, Trackings, Carriers, Services, Labels, Pickups"), but the single generic verb "Manage" and the hedging phrase "and more" leave minor coverage gaps short of comprehensive.	4 / 5
Completeness	Explicitly answers both what ("Manage Shipments, Trackings...") and when ("Use when the user wants to interact with Shipcloud data"), but the trigger is somewhat generic rather than a concrete trigger phrase.	4 / 5
Trigger Term Quality	Good keyword coverage with natural resource names plus "interact with Shipcloud data," but lacks synonyms and broader variations that would make it comprehensive.	4 / 5
Distinctiveness Conflict Risk	Names a specific product (Shipcloud) and its dedicated resources with repeated brand mentions, creating a clear niche with minimal overlap risk.	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/shipcloud/SKILL.md
Commit: f484c82

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