ordercli

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

8.30x

Quality

75%

Does it follow best practices?

Impact

83%

8.30x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

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

93%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 exceptionally lean, fully executable command reference with clear sequencing and a preview-then-confirm safety pattern for the destructive reorder action. The only minor gap is that destructive-operation validation lives in a Notes section rather than inline with the workflow.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with no conceptual padding or over-explanation; every line is an executable command or a terse note, assuming Claude's competence; fits the anchor for lean, token-efficient content.	5 / 5
Actionability	Commands are fully executable and copy-paste ready across all sections (login, orders, history, reorder, cookies, session), covering the common cases with concrete flags and placeholders; matches the anchor for fully executable guidance.	5 / 5
Workflow Clarity	The Quick start gives a clear sequenced onboarding path and the Reorder section includes a preview-then-confirm checkpoint, plus a "Confirm before any reorder or cart-changing action" note; not a 5 because the destructive-operation validation is scattered in Notes rather than inline, leaving minor gaps.	4 / 5
Progressive Disclosure	At under 50 lines with no external references needed and no bundle files present, the well-organized sections (Quick start, Orders, Reorder, Cloudflare, Session import, Deliveroo, Notes) satisfy the simple-skill exception for a top score.	5 / 5
	Total	19 / 20 Passed

Description

57%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 specific about a clear niche (Foodora order tracking), but it omits an explicit "Use when..." trigger clause, which caps its completeness. Trigger term coverage is adequate but lacks common synonyms.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when the user wants to check Foodora order history or track an active Foodora delivery."

Broaden trigger terms with natural synonyms like "track order", "delivery status", and "reorder" to improve recall.

Mention reorder/cart actions in the description so the skill triggers for cart-related requests, not just status checks.

Dimension	Reasoning	Score
Specificity	Names the domain (Foodora) and two concrete actions — "checking past orders" and "active order status" — matching the anchor for 1-2 concrete actions without comprehensive coverage; not a 4 since only two actions are listed.	3 / 5
Completeness	Clearly states what the CLI does, but lacks any explicit "Use when..." trigger clause; per the guidelines a missing trigger clause caps completeness at 3, and it is not a 4 because the when is entirely absent rather than weakly present.	3 / 5
Trigger Term Quality	Includes relevant natural terms ("past orders", "active order status", "Foodora") a user might say, but misses common synonyms like "track order", "delivery status", or "reorder"; fits the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	"Foodora-only CLI for checking past orders and active order status" carves a clear niche tied to a specific delivery platform with distinct triggers and minimal conflict risk; the Deliveroo WIP aside does not broaden it enough to drop to 4.	5 / 5
	Total	14 / 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: ba4a78e

Reviewed: 1 day 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.