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, distinctive niche (Foodora CLI for order management) but is incomplete — it lacks explicit trigger guidance ('Use when...') and could be more specific about the concrete actions supported. The mention of 'Deliveroo WIP' adds useful scope information but the overall description is too terse to reliably guide skill selection.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Use when the user asks about Foodora orders, delivery status, order history, or food delivery tracking'.
List more specific concrete actions such as 'list past orders, check active delivery status, view order details' to improve specificity.
Include natural user terms like 'food delivery', 'track order', 'order history', 'delivery tracking' to improve trigger term coverage.
| 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 for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only partially described, warranting a 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 clear boundaries. | 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 fully actionable commands organized into clear topical sections. Its main weakness is the lack of explicit validation/error-recovery steps in the reorder workflow, where a destructive action (adding to cart) could benefit from a more structured checkpoint flow. Overall it's an effective skill that respects Claude's intelligence and token budget.
Suggestions
Integrate the 'confirm before any reorder or cart-changing action' guidance directly into the Reorder section as an explicit numbered workflow (1. Preview → 2. Verify output → 3. Confirm with --confirm) rather than a footnote.
| 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 given as specific, copy-paste-ready CLI commands with real flags and arguments. The skill covers login, querying, reordering, session management, and workarounds for bot protection—all with executable examples. | 3 / 3 |
Workflow Clarity | The quick start section implies a sequence (configure country → login → use), but there are no explicit validation checkpoints. The reorder section has a preview-then-confirm flow, which is good, but the 'Confirm before any reorder or cart-changing action' note is only a brief mention at the end rather than an integrated validation step in the workflow. | 2 / 3 |
Progressive Disclosure | For a simple CLI reference skill under 50 lines with no need for external 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. | 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
- attilaczudor/Test
- Commit
b4fc4af
- 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.