Name: sendcloud
Rating: 59.2 (1 reviews)
Author: membranedev

sendcloud

Sendcloud integration. Manage Parcels, ShippingMethods, Addresses. Use when the user wants to interact with Sendcloud data.

Quality

69%

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

Quality

Content

72%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 executable commands and a clean connection-state workflow, and is well-structured for a self-contained skill. Its weaknesses are an over-explanatory lead paragraph and the absence of validation/verification steps around destructive parcel operations.

Suggestions

Trim or remove the opening paragraph explaining what Sendcloud is and its market—Claude does not need this background to act.

Add an explicit validate/verify checkpoint after destructive and batch actions (create-parcel, update-parcel, cancel-parcel), e.g. re-fetch the parcel with get-parcel to confirm the resulting state before reporting success.

Add a brief confirmation/prompt step before running cancel-parcel or other irreversible actions to reduce the risk of unintended destructive changes.

Dimension	Reasoning	Score
Conciseness	The opening paragraph over-explains what Sendcloud is and its target market—background Claude does not need to act—though the rest is mostly efficient commands, tables, and flags.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) with flags and JSON examples, plus a populated Popular actions table mapping names to keys.	5 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is clear and includes a state-machine polling feedback loop, but destructive/batch actions (cancel-parcel, update-parcel, create-parcel) lack validation steps, capping this dimension at 3.	3 / 5
Progressive Disclosure	A self-contained single-file skill with no bundle, organized into clear, navigable sections (Overview, Working with Sendcloud, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices); per the simple-skill note, well-organized sections with no external references warrant a 5.	5 / 5
	Total	16 / 20 Passed

Description

66%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 structurally complete, naming a distinct product and three managed entities with an explicit Use-when trigger. Its main weakness is generic trigger phrasing and a focus on data objects rather than concrete user-facing actions.

Suggestions

Replace the generic "interact with Sendcloud data" trigger with concrete natural phrases users would say, e.g. "Use when the user wants to create or track parcels, manage shipping methods, or list sender addresses."

Lead with concrete verbs rather than data-object nouns (e.g. "Create, track, and cancel parcels; list shipping methods and sender addresses") to lift specificity.

Add common synonyms such as shipping labels, returns, and tracking to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Sendcloud domain and three concrete managed entities ("Parcels, ShippingMethods, Addresses") with the verb "Manage", but lists data objects rather than multiple distinct concrete actions, matching the 1-2-actions-but-not-comprehensive anchor.	3 / 5
Completeness	Both a clear "what" (manage Parcels, ShippingMethods, Addresses) and an explicit "when" are present, though the "when" clause ("interact with Sendcloud data") could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant domain keywords (Parcels, ShippingMethods, Addresses, Sendcloud) but the trigger phrase "Use when the user wants to interact with Sendcloud data" is generic and misses common natural variations like shipping labels, tracking, or returns.	3 / 5
Distinctiveness Conflict Risk	The named product "Sendcloud" forms a clear niche with distinct triggers and minimal conflict risk, since only a Sendcloud integration skill would plausibly match.	5 / 5
	Total	15 / 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/sendcloud/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.