CtrlK
BlogDocsLog inGet started
Tessl Logo

ordercli

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

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/ordercli/SKILL.md

The canonical home for this skill is ordercli in openclaw/openclaw

SKILL.md
Quality
Evals
Security

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 exemplary lean command reference: fully executable commands, well-organized sections, and an explicit confirm-before-cart-change checkpoint. The only gap is the absence of a quick validation step after login and any error-recovery guidance for failed commands.

DimensionReasoningScore

Conciseness

The body is pure command listings under short headers with zero concept explanations or padding ("Use `ordercli` to check past orders and track active order status (Foodora only right now)."), so every token earns its place.

5 / 5

Actionability

Every entry is a copy-paste-ready executable command with realistic flags (e.g., `ordercli foodora login --email you@example.com --password-stdin`, `ordercli foodora reorder <orderCode> --confirm --address-id <id>`) covering the common cases.

5 / 5

Workflow Clarity

The quick start gives a real sequence (countries → config set → login → orders → history) and the cart-changing reorder flow has an explicit Preview → --confirm checkpoint plus the "Confirm before any reorder or cart-changing action" note, so the destructive-operation cap does not apply; it falls short of 5 because there is no explicit post-login verification step or error-recovery guidance (e.g., what to do when login or `orders` fails).

4 / 5

Progressive Disclosure

This is a simple single-purpose skill under 50 lines with no external bundle files; the sections (Quick start, Orders, Reorder, Cloudflare, Session import, Deliveroo, Notes) are well organized, which the rubric's simple-skill exception says can score 5.

5 / 5

Total

19

/

20

Passed

Description

53%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, specific, and clearly scoped to Foodora order checking, with a distinct niche. Its main weakness is the complete absence of "when to use" trigger guidance and of natural trigger variations (e.g., "order history", "track my order"), leaving it at the midpoint of the scale.

Suggestions

Add a "Use when..." clause, e.g., "Use when the user asks about Foodora orders, order history, or tracking an active delivery."

Include natural trigger synonyms such as "order history", "track my order", and "reorder" so the description matches how users actually phrase these requests.

Decide whether the "(Deliveroo WIP)" aside belongs in the description; if kept, state its status in trigger terms (e.g., "Deliveroo support is WIP and not yet usable") to avoid inviting unfulfillable requests.

DimensionReasoningScore

Specificity

"checking past orders and active order status" names the domain and two concrete actions, matching the 1-2-actions anchor; it omits reorder, session import, and cookie handling shown in the body, so coverage is not comprehensive enough for 4.

3 / 5

Completeness

The "what" is clearly stated (a Foodora-only CLI for checking past orders and active order status), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

"past orders", "active order status", "Foodora", and "Deliveroo" are natural user terms, but common variations like "order history", "track my order", or "reorder" are missing, which fits the some-keywords-missing-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

"Foodora-only CLI" carves out a clear niche with service-specific triggers, so conflict risk is minor; it falls short of 5 because no explicit trigger phrases are given and the "(Deliveroo WIP)" aside leaves scope slightly ambiguous.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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
Bitterbot-AI/bitterbot-desktop
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.