Overview

Interface with the AnyList service via a CLI to view and manage grocery and shopping lists (list items, add, check/uncheck, remove, and clear items), with JSON output for programmatic use in an OpenClaw agent.

Key Advantages

1.Direct mapping to common grocery-list workflows (viewing, adding, checking off items) with clear CLI commands.

2.Supports JSON output for all key read operations, making it straightforward to parse responses in tools and agents.

3.Simple, consistent command structure (list name then action) reduces implementation complexity.

4.Supports item categorization and quantities, enabling richer list-management behaviors beyond plain text items.

5.Case-insensitive list and item names help avoid user-friction due to capitalization differences.

Use Cases

Answering questions like “What’s on my grocery list?” by listing unchecked items from a default list such as "Grocery".
Adding one or multiple items (optionally with categories and quantities) when the user requests updates to a shopping list.
Marking items as purchased (checked) or not purchased (unchecked) based on user confirmations during a shopping conversation.
Clearing completed items from a list after a shopping trip to keep the list tidy.
Building recipe-based flows where adding items again automatically reactivates (unchecks) them on the list.

Evaluation History (1)

8.0/103/20/2026darwin-x64

▼

OS: darwin-x64LLM: anthropic/claude-sonnet-4.5

**Quick judgment**: A solid, focused skill for managing grocery/shopping lists through the AnyList service. It exposes all core list operations with a clean CLI and JSON modes, making it well-suited for an assistant that maintains a user’s grocery list over time. **Strengths** - Covers the full basic lifecycle: list viewing, adding items (with categories/quantities), checking/unchecking, removing, and clearing. - JSON output options (`--json`) make it easy for an agent to parse list contents and unchecked items. - Command design is straightforward and consistent, reducing integration complexity. - Case-insensitive handling of names reduces user-facing friction. **Key risks / limitations** - Requires AnyList authentication (`anylist auth` or `ANYLIST_EMAIL` / `ANYLIST_PASSWORD` env vars); misconfiguration or expired credentials will cause failures that the agent must detect and handle gracefully. - Depends on the AnyList backend and network availability; outages or API changes could impact reliability. - The skill is narrowly scoped to AnyList; it is not a generic list manager and won’t work without an AnyList account. **Recommended scenarios** - Assistants that act as a user’s grocery/shopping companion: adding items while planning meals, checking off items while shopping, and reviewing what’s left to buy. - Contexts where the agent can safely be configured with user-specific AnyList credentials and maintain a persistent grocery list. - Systems that need structured access to list data (via JSON) to perform higher-level reasoning, such as recipe planning or inventory-like checks based on what’s on the shopping list.

Anylist

Overview

Key Advantages

Use Cases

Evaluation Scores

Download Trend

Evaluation History (1)

Comments (0)

Post a Comment