CtrlK
BlogDocsLog inGet started
Tessl Logo

ordercli

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

71

8.30x
Quality

63%

Does it follow best practices?

Impact

83%

8.30x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Content

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. Commands are concrete and copy-paste ready with clear grouping by function. The main weakness is the lack of explicit validation/error handling guidance for destructive operations like reorder, though the preview-before-confirm pattern partially addresses this.

Suggestions

Add brief error recovery guidance for reorder failures (e.g., what to do if cart-changing action fails or session expires mid-operation)

DimensionReasoningScore

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 concrete, copy-paste-ready CLI commands with specific flags and arguments. The quick start section provides a clear executable sequence from setup to usage.

3 / 3

Workflow Clarity

The quick start provides a clear sequence (countries → config → login → orders), and the reorder section shows preview-before-confirm. However, there's no explicit validation or error recovery guidance for the reorder/cart-changing operations, which are destructive actions that the Notes section flags as needing confirmation.

2 / 3

Progressive Disclosure

For a simple CLI reference skill under 50 lines with no bundle files, the content is well-organized into logical sections (Quick start, Orders, Reorder, Cloudflare, Session, Deliveroo, Notes) that are easy to scan and navigate.

3 / 3

Total

11

/

12

Passed

Description

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, narrow niche (Foodora CLI for order management) which makes it distinctive, but it lacks an explicit 'Use when...' clause and could benefit from more specific action verbs and natural trigger terms. The mention of 'Deliveroo WIP' adds noise without actionable value.

Suggestions

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

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

Remove or clarify 'Deliveroo WIP' — either drop it or reframe as 'Deliveroo support planned' to reduce confusion about the skill's current capabilities.

DimensionReasoningScore

Specificity

Names the domain (Foodora CLI) and some actions ('checking past orders and active order status'), but doesn't list multiple concrete actions in detail—it's fairly brief and only covers two capabilities.

2 / 3

Completeness

Describes what it does (checking past orders and active order status) 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 closer to 1.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'Foodora', 'orders', 'order status', and 'CLI', but misses common user-facing variations (e.g., 'food delivery', 'track order', 'order history'). 'Deliveroo WIP' is noted but not actionable as a trigger.

2 / 3

Distinctiveness Conflict Risk

Very specific niche—Foodora CLI for order checking is unlikely to conflict with other skills. The platform-specific naming (Foodora, Deliveroo) makes it clearly distinguishable.

3 / 3

Total

8

/

12

Passed

Validation

72%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation8 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.