ordercli
Foodora-only CLI for checking past orders and active order status (Deliveroo WIP).
71
63%
Does it follow best practices?
Impact
83%
8.30xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/ordercli/SKILL.mdQuality
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 niche (Foodora CLI for order management) which makes it distinctive, but it lacks an explicit 'Use when...' clause and provides only a brief summary of capabilities. The trigger terms are somewhat relevant but miss natural user language variations for food delivery order tracking.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to check Foodora order history, track an active food delivery, or query past orders via CLI.'
Include more natural trigger terms users might say, such as 'food delivery', 'track order', 'order history', 'delivery status', and file/command references if applicable.
Expand the capability list with more specific actions, e.g., 'Lists past Foodora orders, checks active delivery status, retrieves order details. Deliveroo support is work-in-progress.'
| Dimension | Reasoning | Score |
|---|---|---|
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 | It describes what the skill does (checking past orders and active order status via Foodora CLI), but there is no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2—and even the 'what' is minimal, so this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Foodora', 'orders', 'order status', and 'CLI', but misses common natural variations a user might say (e.g., 'food delivery', 'track order', 'order history', 'Deliveroo'). The Deliveroo mention is marked WIP which reduces its usefulness as a trigger. | 2 / 3 |
Distinctiveness Conflict Risk | The description is very specific to Foodora CLI and food delivery order checking, which is a clear niche unlikely to conflict with other skills. The platform-specific naming (Foodora, Deliveroo) makes it highly distinctive. | 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 extreme conciseness with fully concrete commands. The main weakness is the lack of explicit validation/error-recovery guidance around the reorder workflow, which involves cart-changing operations.
Suggestions
Add a brief validation/error-recovery step to the Reorder section (e.g., 'If reorder fails, check session status with `ordercli foodora session refresh`' or verify the preview output before confirming).
| 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 in the form of specific, copy-paste-ready CLI commands with real flags and arguments. The quick start section provides a complete executable workflow from configuration through to querying orders. | 3 / 3 |
Workflow Clarity | The quick start provides a clear sequence (configure country → login → query orders), and the reorder section has a preview-then-confirm flow. However, there are no explicit validation checkpoints or error recovery steps for the reorder/cart-changing operations, which are destructive actions that the notes section warns about but doesn't integrate into the workflow. | 2 / 3 |
Progressive Disclosure | For a simple 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) that are easy to scan and navigate. No external references are needed for this scope. | 3 / 3 |
Total | 11 / 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.
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
- Hung-Reo/hungreo-openclaw
- Commit
d8d7f4b
- 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.