ordercli

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

8.30x

Quality

71%

Does it follow best practices?

Impact

83%

8.30x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/ordercli/SKILL.md

The canonical home for this skill is ordercli in openclaw/openclaw

Quality

Content

90%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 an excellent lean CLI reference: fully executable commands, well-grouped by task, with an explicit safety checkpoint for the only risky (cart-changing) operation. The two improvements are framing the Cloudflare/session-import sections as error-recovery paths and promoting section titles to real markdown headers.

Suggestions

Convert section titles to markdown headers (e.g. '## Quick start (Foodora)', '## Orders') so sections render and navigate correctly.

Frame the Cloudflare/browser-login/session-import sections as an explicit fallback flow, e.g. 'If login fails due to bot protection: 1) retry with --browser, 2) import session from Chrome', to add a validation feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with zero explanation of concepts Claude already knows; every line is a usable command or an actionable note ('Use --config /tmp/ordercli.json for testing', 'Confirm before any reorder'), matching the 'every token earns its place' anchor.	5 / 5
Actionability	Commands are copy-paste ready with concrete flags and placeholders (--password-stdin, --browser-profile, --address-id <id>), and the examples cover the common cases: login, listing orders, watching status, history, reorder, and session import.	5 / 5
Workflow Clarity	Quick start provides a clear ordered sequence (countries -> config -> login -> orders -> history), and the one cart-changing operation has an explicit checkpoint (preview vs. --confirm plus 'Confirm before any reorder or cart-changing action'), so the destructive-operation cap does not apply; it falls short of 5 because login/session failure recovery is presented as alternatives rather than an explicit validate-and-retry loop.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/ exist) and content appropriately stays in one flat file; however, section titles ('Quick start (Foodora)', 'Orders', 'Reorder...') lack markdown '##' headers, so they render as plain text instead of navigable sections — a minor organization gap that keeps it below 5.	4 / 5
	Total	18 / 20 Passed

Description

53%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 concise and pins a clear niche (Foodora-only order checking), but it is incomplete: it lacks any 'when to use' trigger clause and its keyword coverage misses natural synonyms like 'delivery tracking' or 'reorder'. The '(Deliveroo WIP)' parenthetical is a useful scope signal but contributes little as a trigger.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about Foodora orders, wants to track an active delivery, or check past order history.'

Expand trigger keywords to include natural synonyms users would say: 'delivery tracking', 'track my order', 'reorder', 'Foodora order history'.

Mention the reorder/cart capability in the description since it is a concrete supported action, improving both specificity and trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Foodora-only CLI') and two concrete actions ('checking past orders', 'active order status'), matching the anchor for 1-2 concrete actions without comprehensive coverage; a score of 4 would require several listed actions (e.g., reorder, cart, session import are absent).	3 / 5
Completeness	The 'what' is clear (check past orders and active order status on Foodora) but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes some natural terms ('past orders', 'order status', 'Foodora', 'Deliveroo') but misses common variations users would say such as 'delivery tracking', 'track my order', or 'reorder'; not score 4 because keyword coverage is thin rather than 'good with a few missing'.	3 / 5
Distinctiveness Conflict Risk	'Foodora-only' establishes a clear vendor-specific niche with minimal conflict risk, but trigger phrases aren't staked out and a generic food-delivery/order skill could still overlap, placing it between anchors 4 and 5 rather than at a fully distinct 5.	4 / 5
	Total	13 / 20 Passed

Validation

81%

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 — 13 / 16 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	13 / 16 Passed

Repository: trpc-group/trpc-agent-go
Path: openclaw/skills/ordercli/SKILL.md
Commit: 9bb1c42

Reviewed: 5 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.