Bring! Shopping Lists

Manage Bring! shopping lists - view, add, and remove grocery items from shared shopping lists. Use when the user wants to interact with their Bring! shopping list app, add groceries, check what's on the list, or remove items after shopping.

Security Scan

The skill's code, instructions, and requirements are consistent with a Bring! shopping-list CLI: it needs your Bring email/password, uses the bring-shopping npm package, and stores config under ~/.openclaw/bring — nothing appears to be doing unrelated or hidden actions.

Purpose & Capability

Name/description match the included CLI wrapper and API reference. The skill requires authentication and interacting with Bring list APIs, which explains the email/password and the bring-shopping npm dependency.

Instruction Scope

Runtime instructions are scoped to Bring operations (list, add, remove, detect language). They explicitly instruct installing the bring-shopping npm package and running a local CLI wrapper. They also instruct storing email/password in ~/.openclaw/bring/config.json (plaintext), which is functionally required but a security/privacy consideration.

Install Mechanism

There is no registry install spec; SKILL.md instructs users to run `npm install -g bring-shopping`. Using an npm package is expected for this purpose but carries typical third-party-package risk (supply-chain risk, arbitrary code during install). The packaged script references that dependency; this is coherent but worth reviewing the bring-shopping project before installing globally.

Credentials

The skill requests no environment variables and does not require unrelated credentials. It does require and persist the user's Bring email/password in a config file — proportional to functionality but it means the skill will have long-term access to the user's Bring account if the file is present.

Persistence & Privilege

The skill does write its own config under the user's home directory (~/.openclaw/bring) but does not request always:true, system-wide changes, or other skills' configs. This level of persistence is expected for a CLI that stores credentials and a default list.

Assessment

This skill appears to do what it claims, but review and accept these trade-offs before installing: (1) it requires installing the third-party npm package `bring-shopping` globally — audit that package/repo and prefer installing with a pinned version; (2) it stores your Bring email and password in plaintext at ~/.openclaw/bring/config.json, which grants persistent access to your Bring account — consider whether you want to provide those credentials and whether the Bring API supports token-based auth instead; (3) global npm installs run code during install and can modify your environment — install in a controlled environment or inspect the package first. If you don't trust the bring-shopping package or the skill author, do not install or run the CLI.

Bring Shopping List Integration

Interact with Bring! shopping lists to manage groceries and shopping items.

Prerequisites

The bring-shopping npm package must be installed:

npm install -g bring-shopping

Initial Setup

Before first use, configure Bring credentials:

./bring configure <email> <password>

Credentials are stored in ~/.openclaw/bring/config.json.

Common Operations

List All Shopping Lists

Get all available shopping lists with their UUIDs:

./bring lists

Output includes list names, UUIDs, and themes.

Find a List by Name

Search for a list by partial name match:

./bring findlist "Home"
./bring findlist "Groceries"

Returns matching lists with their UUIDs.

View List Items

Show all items in a shopping list:

./bring items <listUuid>

Or use the default list (if set):

./bring items

Returns items to purchase and recently purchased items.

Add Items

Add an item to a shopping list:

./bring add <listUuid> "<item-name>" "<optional-note>"

Examples:

./bring add abc-123 "Latte" "2 litri"
./bring add abc-123 "Pane"

Tip: Use item names that match what you already use in the Bring app to ensure icons appear.

Remove Items

Remove an item from a shopping list (moves to recent list):

./bring remove <listUuid> "<item-name>"

Set Default List

Set a default list UUID to avoid passing it each time:

./bring setdefault <listUuid>

After setting default, you can use ./bring items without specifying listUuid.

Manage List Languages

Set the language for a list (for reference):

./bring setlang <listUuid> it-IT
./bring setlang <listUuid> es-ES
./bring setlang <listUuid> en-US

Get the configured language:

./bring getlang <listUuid>

Supported locales: en-US, it-IT, es-ES, de-DE, fr-FR

Workflow Examples

Adding to a Named List

When user says "Add milk to the Home list":

1. Find the list:

   ./bring findlist "Home"
   

2. Check what language/names are used in that list:

   ./bring items <listUuid>
   

3. Add using the appropriate name (match existing items):

   ./bring add <listUuid> "Latte"  # If list uses Italian
   # or
   ./bring add <listUuid> "Milk"   # If list uses English
   

Checking What's Needed

When user asks "What's on my shopping list?":

./bring items <listUuid>

Or if default is set:

./bring items

Parse and present items in a readable format.

Marking Items as Purchased

When user says "Remove milk from the list":

./bring remove <listUuid> "Latte"

Multilingual Families

For families using multiple languages:

1. Check existing items in each list to see what language is used
2. Use consistent naming - match the names already in the list
3. Set list language with setlang for reference
4. Learn from context - if a list has "Latte", "Pane", "Uova", it's Italian

The Bring app automatically shows icons when item names match its catalog. To ensure icons appear, use names that match what the Bring app recognizes for that language.

Technical Details

• The bring wrapper script sets NODE_PATH for the npm package
• Configuration stored in ~/.openclaw/bring/config.json
• Session authenticated via email/password
• Lists can be shared among family members
• Changes sync in real-time across all devices

Notes

• Item names are case-sensitive
• The "remove" command moves items to "recent" list (not permanent deletion)
• Multiple family members can share lists
• Each list can use different language conventions
• Match item names to what's already in your lists for best icon support