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 ./openclaw/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 order checking CLI) which makes it distinctive, but it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords. The 'Deliveroo WIP' note is internal/developmental and doesn't help with skill selection.
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', or 'past deliveries'.
Remove or reframe the internal note '(Deliveroo WIP)' — either omit it or state it as a supported scope, e.g., 'Deliveroo support planned but not yet available.'
| 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 fully actionable commands organized into clear sections. Its main weakness is the lack of explicit validation/error-handling guidance in multi-step workflows like reordering or session setup. Overall it serves its purpose effectively as a quick-reference guide.
Suggestions
Add explicit validation steps to the reorder workflow (e.g., 'Verify cart contents before confirming: `ordercli foodora cart show`') to make the destructive operation safer.
Consider adding a brief note on how to verify a successful login or session import (e.g., expected output or a test command) to close the feedback loop in the setup workflow.
| 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. Lean and efficient throughout. | 3 / 3 |
Actionability | Fully concrete, copy-paste-ready CLI commands covering login, orders, history, reorder, session management, and Cloudflare workarounds. Specific flags and arguments are shown with realistic 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 workflow has a preview-then-confirm pattern which is good, but the 'confirm before any reorder or cart-changing action' note is vague rather than being an explicit validation step in the workflow. | 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, Session import, Deliveroo, Notes) with clear headers enabling easy navigation. No need for external file references given the 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
- trpc-group/trpc-agent-go
- Commit
af8bd5f
- 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.