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 explicit trigger guidance ('Use when...') and could benefit from more specific action verbs and natural user keywords. The mention of 'Deliveroo WIP' adds context but also introduces ambiguity about the skill's actual capabilities.
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 would say, such as 'food delivery', 'track delivery', 'order history', 'delivery status', 'what did I order'.
Expand the action list to be more specific, e.g., 'Checks past Foodora order history, tracks active delivery status, and retrieves order details via CLI.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Foodora CLI, past orders, active order status) and some actions (checking past orders, checking active order status), but doesn't list comprehensive concrete actions like canceling, reordering, or filtering. | 2 / 3 |
Completeness | Describes what it does (checking past orders and active order status via Foodora CLI) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, placing this at 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Foodora', 'orders', 'order status', and 'Deliveroo', 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 mention of specific platforms (Foodora, Deliveroo) creates a clear, narrow scope. | 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, concise CLI reference skill that provides highly actionable, copy-paste-ready commands organized into clear sections. Its main weakness is the lack of explicit validation/error-recovery steps, particularly around the reorder workflow and login/session management where things could fail (e.g., Cloudflare blocks, expired sessions).
Suggestions
Add brief error recovery guidance for common failure modes (e.g., what to do when Cloudflare blocks login, or when a session expires mid-use)
Add a validation step to the reorder workflow, such as checking the cart state after reorder or verifying the order was placed successfully
| 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 food delivery works. Lean and efficient throughout. | 3 / 3 |
Actionability | Nearly every line is a copy-paste-ready CLI command with realistic arguments. The quick start section provides a complete workflow from configuration to usage. Flag options are specific and concrete. | 3 / 3 |
Workflow Clarity | The quick start provides a clear sequence (configure → login → use), and the reorder section has a preview-then-confirm pattern. However, there are no explicit validation checkpoints or error recovery steps, and the reorder workflow (a cart-changing/destructive operation) lacks a feedback loop beyond 'confirm before any reorder.' | 2 / 3 |
Progressive Disclosure | For a simple CLI skill under 50 lines, the content is well-organized into logical sections (Quick start, Orders, Reorder, Cloudflare handling, Session import, Deliveroo WIP, Notes). No need for external file references given the scope, and navigation is easy. | 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.