ordercli

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

8.30x

Quality

—

Does it follow best practices?

Impact

83%

8.30x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-organized command reference: lean on tokens, fully executable, with a clear quick-start sequence and an explicit confirm-checkpoint for destructive reorder actions, and appropriately sectioned for a single-file skill.

Dimension	Reasoning	Score
Conciseness	The body is a lean set of command bullets with a single orienting sentence ("Use `ordercli` to check past orders and track active order status"), with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Every section gives concrete, copy-paste-ready commands (e.g. `ordercli foodora history show <orderCode> --json`), fully executable with specific flags and arguments.	3 / 3
Workflow Clarity	The Quick start section sequences setup (countries → config → login → orders → history), and the Notes section provides an explicit checkpoint ("Confirm before any reorder or cart-changing action") for the destructive cart operations.	3 / 3
Progressive Disclosure	The skill is under 50 lines with no external bundle files and is organized into clearly labeled sections (Orders, Reorder, Cloudflare, Session import, Deliveroo, Notes), satisfying the simple-skill allowance for progressive disclosure.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 specific and distinctive, clearly naming the Foodora domain and core order actions, but it lacks an explicit "Use when" trigger clause and broader keyword coverage, leaving it mid-range on completeness and trigger quality.

Suggestions

Add an explicit trigger clause such as "Use when the user wants to check Foodora orders, track delivery status, or reorder a past meal."

Broaden trigger terms to include natural variations like "delivery status", "order history", and "reorder" to improve keyword coverage.

Mention additional concrete capabilities (history lookup, reorder, session import) to raise specificity from partial to comprehensive.

Dimension	Reasoning	Score
Specificity	Quotes "checking past orders and active order status" name the domain and two concrete actions, but the description omits other capabilities (reorder, history detail, session import) so it is not comprehensive.	2 / 3
Completeness	It clearly states what the skill does ("Foodora-only CLI for checking past orders and active order status"), but there is no explicit "when to use it" trigger clause, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	"Foodora", "orders", and "order status" are natural keywords, but coverage of common variations is limited and there is no "Use when" trigger phrasing.	2 / 3
Distinctiveness Conflict Risk	"Foodora-only CLI" carves out a narrow niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

81%

Warnings & errors only

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

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	13 / 16 Passed

Repository: trpc-group/trpc-agent-go
Commit: 737835b

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.