CtrlK
BlogDocsLog inGet started
Tessl Logo

food-order

Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.

73

Quality

93%

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

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.

An exemplary lean, command-first skill body: fully executable guidance, a clearly sequenced workflow with an explicit preview-before-confirm safety gate, and appropriately compact single-file organization. The only improvement space is error-recovery guidance for failure cases like expired sessions.

DimensionReasoningScore

Conciseness

The ~40-line body is pure commands and imperatives ("Country: `ordercli foodora countries`", "Recent list: `ordercli foodora history --limit 10`") with no concept explanations or padding — every token earns its place, matching the lean anchor.

5 / 5

Actionability

Every step is a copy-paste-ready command covering the common cases: setup, two login methods, history, preview, confirmed reorder with the --address-id variant, tracking, and a throwaway-config debug path, matching the fully-executable anchor.

5 / 5

Workflow Clarity

The sequence (Setup → Find → Preview → Confirm → Track) is clear with an explicit checkpoint ("Prefer preview-only steps first; show what will happen; ask for confirmation"), so the destructive-operation cap does not apply; however there is no error-recovery feedback loop (e.g., handling login expiry or a failed reorder), matching the 'most checkpoints present; minor validation gaps' anchor rather than the feedback-loop anchor.

4 / 5

Progressive Disclosure

A single-purpose skill under 50 lines with well-organized sections and no need for external references (none exist in the bundle, so no dangling paths), which scores 5 under the rubric's simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

92%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.

A strong description: concrete third-person capabilities, an explicit 'Use when...' clause with natural trigger phrases, and a service/tool-specific niche that avoids conflict risk. The only gap is modest synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

"Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status" plus "browse recent Foodora order history" lists multiple concrete actions in third person with comprehensive coverage of the skill's user-facing capabilities, matching the anchor for full specificity rather than the 'minor gaps' anchor below it.

5 / 5

Completeness

The description explicitly answers both what ("Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli") and when ("Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history") with concrete trigger phrases, matching the top anchor; the anchor below requires the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Natural phrases like "reorder food", "check delivery status", and "browse recent Foodora order history" give good coverage, but common synonyms (e.g., "order again", "where is my order", "track my food") are missing, matching the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Naming the specific service ("Foodora") and tool ("ordercli") with distinct triggers gives this a clear niche with minimal conflict risk against any other skill, matching the top anchor.

5 / 5

Total

19

/

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.