Name: shipday
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

shipday

Shipday integration. Manage Accounts. Use when the user wants to interact with Shipday data.

Quality

64%

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

Quality

Content

67%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 a well-structured, executable CLI integration guide with good commands and a polling feedback loop for connections. Main weaknesses are introductory padding and a couple of broken cross-references in the workflow numbering.

Suggestions

Remove or trim the introductory paragraph explaining what Shipday is and who uses it; Claude does not need that background.

Fix the workflow numbering: add a labeled "Step 1a"/"Step 2" so the "skip to Step 2" and "1b" references resolve.

Either populate "Popular actions" with the actual common Shipday actions or remove the heading to avoid the empty promise.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but the opening paragraph explaining what Shipday is and which businesses use it is concept padding Claude does not need, fitting the score-3 anchor.	3 / 5
Actionability	Concrete copy-paste commands cover login, connection ensure, action list/run, and proxy with a full flag table, but the "Popular actions" section only rediscovery-points rather than listing actual popular actions, a minor gap.	4 / 5
Workflow Clarity	The connection flow has a clear state-check and polling feedback loop, but it references a "Step 2" that is never labeled and uses "1b" numbering with no 1a, leaving minor sequence gaps.	4 / 5
Progressive Disclosure	No bundle files exist and the content is a self-contained, well-sectioned CLI guide with clear headers, which is appropriately organized for this skill type.	4 / 5
	Total	15 / 20 Passed

Description

61%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 includes an explicit trigger clause and a distinct product name, but its capability statement is thin and generic. Tightening the action list with concrete Shipday operations would lift specificity and completeness.

Suggestions

Replace the generic "Manage Accounts" with concrete Shipday operations (e.g., create and track orders, dispatch drivers, manage drivers and restaurants).

Expand trigger terms to cover natural phrasings like deliveries, dispatch, or driver tracking that a user might say instead of just "Shipday data".

Dimension	Reasoning	Score
Specificity	Names the Shipday domain but the only actions offered ("Manage Accounts", "interact with Shipday data") are generic and minimal, matching the score-2 anchor rather than the concrete multi-action coverage of higher levels.	2 / 5
Completeness	It states both what ("Shipday integration. Manage Accounts.") and an explicit when ("Use when the user wants to interact with Shipday data"), but the what is vague, keeping it below the score-5 anchor.	4 / 5
Trigger Term Quality	"Shipday" and "Shipday data" are relevant natural keywords a user would say, but there is no coverage of variations or related terms, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	"Shipday" is a distinct named product with a clear niche and unambiguous triggers, giving minimal conflict risk as in the score-5 anchor.	5 / 5
	Total	14 / 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/shipday/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.