ordercli

Foodora-only CLI for checking past orders and active order status (Deliveroo WIP).

8.30x

Quality

63%

Does it follow best practices?

Impact

83%

8.30x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/ordercli/SKILL.md

Quality

Discovery

40%

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 identifies a clear, distinctive niche (Foodora order checking CLI) but lacks explicit trigger guidance ('Use when...') and could benefit from more natural keywords users might say. The mention of 'Deliveroo WIP' adds noise without actionable information.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Foodora orders, delivery tracking, order history, or food delivery status.'

Include more natural trigger terms users might say, such as 'food delivery', 'track delivery', 'order history', 'delivery status', or 'past deliveries'.

Either remove the 'Deliveroo WIP' note or clarify it — internal status notes don't help Claude decide when to select this skill.

Dimension	Reasoning	Score
Specificity	Names the domain (Foodora CLI) and some actions ('checking past orders and active order status'), but doesn't list comprehensive concrete actions beyond those two. The Deliveroo mention is vague ('WIP').	2 / 3
Completeness	Describes what it does (checking past orders and active order status on Foodora) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, bringing it to 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'Foodora', 'orders', 'order status', and 'CLI', but misses common natural variations users might say such as 'food delivery', 'track order', 'order history', or 'delivery status'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche — Foodora CLI for order checking is highly distinctive and unlikely to conflict with other skills. The platform-specific naming (Foodora, Deliveroo) creates clear boundaries.	3 / 3
	Total	8 / 12 Passed

Implementation

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted CLI reference skill that is lean, actionable, and well-organized. Its primary strength is providing concrete, copy-paste-ready commands organized by use case. The main weakness is the lack of explicit validation/error-handling guidance in multi-step workflows like reordering or session setup.

Suggestions

Add an explicit validation step after login (e.g., 'Verify session: `ordercli foodora orders` — if you see orders, login succeeded') to improve workflow clarity.

For the reorder workflow, add a brief error-recovery note (e.g., what to do if reorder fails due to unavailable items or expired session).

Dimension	Reasoning	Score
Conciseness	Every line is a concrete command or minimal context. No unnecessary explanations of what a CLI is, what Foodora is, or how ordering works. Every token earns its place.	3 / 3
Actionability	All guidance is given as specific, copy-paste-ready CLI commands with real flags and arguments. The skill covers login, querying, reordering, session management, and workarounds for bot protection—all with executable examples.	3 / 3
Workflow Clarity	The quick start section implies a sequence (configure country → login → use), but there are no explicit validation checkpoints. The reorder section has a preview-then-confirm flow, which is good, but the 'Notes' section's 'Confirm before any reorder or cart-changing action' is vague rather than an explicit validation step integrated into the workflow.	2 / 3
Progressive Disclosure	For a simple, single-file CLI reference skill with no bundle files, the content is well-organized into logical sections (Quick start, Orders, Reorder, Cloudflare workarounds, Session import, Deliveroo WIP, Notes). No external references are needed and the structure supports easy scanning.	3 / 3
	Total	11 / 12 Passed

Validation

72%

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 — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	8 / 11 Passed

Repository: deepgram/dglabs-deepclaw
Commit: ec8d4f8

Reviewed: about 8 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.