Name: order-desk
Rating: 64.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

order-desk

Order Desk integration. Manage Orders. Use when the user wants to interact with Order Desk data.

Quality

77%

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

Quality

Content

88%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 and well-sequenced with strong validation checkpoints and a feedback loop, and it is largely token-efficient. The main improvement is structural: offloading the detailed clientAction spec and flag table into a reference file would sharpen the overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense, executable commands with minimal prose, but the opening paragraph explains what Order Desk is and a few lines are editorial ("so you can focus on the integration logic rather than auth plumbing"), which could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/wait, action list/run, and proxy requests, plus a flag table, fully covering the common cases.	5 / 5
Workflow Clarity	A clear sequenced flow (install -> authenticate -> connect -> discover -> run -> proxy) is backed by explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-auth feedback loop (poll again after the user acts).	5 / 5
Progressive Disclosure	No bundle files exist, and the single-file body is organized with clear section headers; however it is moderately long and the detailed clientAction sub-fields and proxy flag table could be split into a reference file for cleaner overview navigation.	4 / 5
	Total	18 / 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 correctly answers both what and when and is highly distinctive thanks to the named product, but it is thin on concrete capabilities and trigger-term variety. Expanding the action list and trigger synonyms would lift the weaker dimensions.

Suggestions

Enumerate concrete actions beyond 'Manage Orders' (e.g., manage products, customers, inventory, and workflows) to improve specificity.

Add natural trigger terms users would say, such as 'orders', 'order fulfillment', or 'e-commerce orders', not just the product name.

Tighten the 'when' clause to concrete trigger phrases (e.g., 'Use when the user needs to manage orders, check inventory, or automate fulfillment in Order Desk').

Dimension	Reasoning	Score
Specificity	The description names the domain ("Order Desk integration") and one concrete action ("Manage Orders"), but does not enumerate the broader capabilities surfaced in the body (products, customers, inventory, workflows), so coverage is not comprehensive.	3 / 5
Completeness	It states both what ("Order Desk integration. Manage Orders.") and when ("Use when the user wants to interact with Order Desk data"), but the 'what' is narrow and the 'when' trigger is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	The only natural keyword is the product name "Order Desk" ("interact with Order Desk data"); common user phrasings like "orders", "fulfillment", or "e-commerce orders" are missing, leaving relevant synonyms uncovered.	3 / 5
Distinctiveness Conflict Risk	Naming the specific third-party product "Order Desk" gives a clear niche with distinct triggers and minimal overlap with other skills.	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/order-desk/SKILL.md
Commit: f484c82

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