grocery-shopping
Help order groceries for delivery. Concierge-style flow — store selection, occasion-based list building, budget tracking, and cart assembly.
67
58%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/grocery-shopping/SKILL.mdQuality
Discovery
67%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 does a good job of listing specific capabilities in a concise, well-structured manner, clearly defining a grocery ordering concierge workflow. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Trigger term coverage could also be expanded to include more natural user phrasings.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to order groceries, build a shopping list, plan meals for delivery, or manage a grocery budget.'
Include additional natural trigger terms users might say, such as 'grocery list', 'food delivery', 'meal planning', 'shopping list', or 'grocery shopping'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: store selection, occasion-based list building, budget tracking, and cart assembly. These are distinct, actionable steps in a grocery ordering workflow. | 3 / 3 |
Completeness | Clearly answers 'what' (order groceries with store selection, list building, budget tracking, cart assembly) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes natural terms like 'order groceries', 'delivery', 'budget', and 'cart', but misses common variations users might say such as 'grocery list', 'meal planning', 'food delivery', 'shopping list', or specific service names. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of grocery delivery, store selection, occasion-based list building, budget tracking, and cart assembly creates a very specific niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured concierge-style grocery ordering flow with clear sequencing and user confirmation checkpoints. However, it suffers from vague actionability on critical steps (opening apps, applying coupons, checking calendars) with no concrete tool invocations or code examples for these operations. The content is moderately concise but could be tightened, and the monolithic structure would benefit from supporting reference files for templates and examples.
Suggestions
Add concrete tool invocations or commands for vague steps like 'open the delivery app,' 'apply coupons automatically,' and 'check the calendar' — specify which tools/APIs to use and how.
Provide a concrete example of the final styled cart summary card (step 10) so the output format is unambiguous.
Add explicit error recovery steps for cart assembly failures (step 7) and coupon application failures, rather than the generic 'offer a manual fallback' in step 9.
Extract the occasion-based branching logic (step 3) and default list templates into a separate reference file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary elaboration — e.g., the detailed sub-bullets for each occasion type could be tighter, and phrases like 'Act like a concierge — warm, natural, and one step at a time' are repeated at the end. Some instructions (like 'Think like a concierge, not a form') are stylistic padding. | 2 / 3 |
Actionability | The skill provides a clear step-by-step flow with specific tool references (ask_user_input_v0) and concrete behavioral instructions, but lacks executable code, specific API calls, or concrete examples of what the cart summary card looks like. Guidance on how to 'open the delivery app,' 'apply coupons automatically,' or 'check the calendar' is vague — no specific commands or tool invocations are given for these critical steps. | 2 / 3 |
Workflow Clarity | The 11-step flow is clearly sequenced and includes some validation checkpoints (step 6 confirmation, step 8 out-of-stock handling, step 10 final OK). However, there are no explicit validation/feedback loops for error recovery in the cart assembly or coupon application steps, and step 9's 'offer a manual fallback' is vague without specifying what that looks like. | 2 / 3 |
Progressive Disclosure | The content is well-structured with numbered steps and bold sub-categories, but it's a monolithic single file with no references to supporting materials. The occasion-based branching logic in step 3 is fairly dense and could benefit from being split out. For a skill of this complexity, some external references (e.g., a default sick-day list template, example cart summary format) would improve organization. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- douglasvought/wiggle-skills
- Commit
b27906e
- 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.