bring-listManage Bring! shopping lists (Einkaufsliste / grocery list) โ add, remove, check off items, batch ops, default list support. Use when: user wants to set up B...
Install via ClawdBot CLI:
clawdbot install MaikiMolto/bring-listManage Bring! shopping lists via the unofficial REST API. Requires curl and jq.
When a user asks you to set up or use Bring for the first time, follow these steps:
Run scripts/bring.sh lists first. If it works, setup is already done โ skip to usage.
Bring! requires an email + password. If the user doesn't have an account yet, they can create one for free at getbring.com or in the Bring! app.
If they signed up via Google/Apple: They need to set a direct password first in the Bring! app (Settings โ Account โ Change Password) before the API works.
Ask the user how they'd like to provide their credentials:
"I need your Bring! email and password. You can either share them here in chat (I'll write them to a config file and never mention them again), or if you prefer to keep them out of the chat entirely, I can give you a terminal command to enter them privately. Which do you prefer?"
Option A โ via chat (convenient):
User shares email + password in chat. Write them directly to the config file using jq for safe JSON encoding (prevents injection via special characters) and do not echo them back:
mkdir -p ~/.config/bring
jq -n --arg e "USER_EMAIL" --arg p "USER_PASSWORD" '{email: $e, password: $p}' > ~/.config/bring/credentials.json
chmod 600 ~/.config/bring/credentials.json
After writing, confirm: "Done โ credentials saved securely. I won't repeat them."
Option B โ via terminal (more private):
Give the user this command to run in their own terminal. Credentials never appear in chat:
mkdir -p ~/.config/bring
read -rp "Bring! Email: " BEMAIL
read -rsp "Bring! Password: " BPASS && echo
jq -n --arg e "$BEMAIL" --arg p "$BPASS" '{email: $e, password: $p}' > ~/.config/bring/credentials.json
chmod 600 ~/.config/bring/credentials.json
unset BEMAIL BPASS
Tell the user: "Run that in your terminal, then come back and I'll continue the setup."
โ ๏ธ Do NOT use scripts/bring.sh setup โ it requires an interactive terminal (TTY) which agents don't have. Always create the credentials file manually as shown in Step 3.
mkdir -p ~/.config/bring
jq -n --arg e "USER_EMAIL" --arg p "USER_PASSWORD" '{email: $e, password: $p}' > ~/.config/bring/credentials.json
chmod 600 ~/.config/bring/credentials.json
scripts/bring.sh login
If login fails: double-check email/password. The user may need their Bring! password (not Google/Apple SSO โ Bring requires a direct account password).
scripts/bring.sh lists
This shows all the user's Bring! lists. The user may have multiple lists, e.g.:
If the user has NO lists: Tell them to create one in the Bring! app first. The API does not support creating or deleting lists โ this must be done in the app. Once they've created a list, continue with setup.
Ask the user which list should be the default. This lets them skip typing the list name every time.
If they have only ONE list: set it as default automatically and inform them.
If they have MULTIPLE lists: show the list names and ask which one to use as default. Explain they can still target other lists by name (e.g., "Put nails on the Baumarkt list").
Update the credentials file to include the chosen default:
# Read existing config and add default_list
jq --arg list "CHOSEN_LIST_NAME" '. + {default_list: $list}' ~/.config/bring/credentials.json > /tmp/bring_conf.json && mv /tmp/bring_conf.json ~/.config/bring/credentials.json
chmod 600 ~/.config/bring/credentials.json
Show the user their current list content to confirm everything works:
scripts/bring.sh show
Tell them: "All set! You can now say things like 'Put milk on the list' or 'What's on the shopping list?'"
The Bring! API does not support creating or deleting lists. If the user asks to create a new list or delete one, tell them:
"Lists can only be created and deleted in the Bring! app. Once you've made the change there, I can immediately work with the new list."
Bring! lists are often shared between family members or partners. Changes made by the agent sync instantly to all devices sharing that list. Inform the user:
Credentials via env vars BRING_EMAIL + BRING_PASSWORD, or config file ~/.config/bring/credentials.json:
{"email": "user@example.com", "password": "secret", "default_list": "Einkaufsliste"}
Interactive setup (TTY required): scripts/bring.sh setup
All commands accept a list name (partial match) or UUID. If default_list is configured, the list argument can be omitted.
# List all shopping lists
scripts/bring.sh lists
# Show items on a list (or default list)
scripts/bring.sh show
scripts/bring.sh show "Einkaufsliste"
# Add item (with optional specification/quantity)
scripts/bring.sh add "Milch" "fettarm, 1L"
scripts/bring.sh add "Einkaufsliste" "Milch" "fettarm, 1L"
# Add multiple items at once (use "item|spec" for specifications)
scripts/bring.sh add-multi "Brot" "Kรคse|Gouda" "Butter|irische"
# Complete/check off item (moves to recently purchased)
scripts/bring.sh complete "Milch"
# Complete multiple items at once
scripts/bring.sh complete-multi "Milch" "Brot" "Kรคse"
# Move item back from recently to purchase list
scripts/bring.sh uncomplete "Milch"
# Remove item entirely
scripts/bring.sh remove "Milch"
# Remove multiple items at once
scripts/bring.sh remove-multi "Milch" "Brot" "Kรคse"
When the user has multiple lists, they can target a specific one by name:
scripts/bring.sh add "Baumarkt" "Nails"scripts/bring.sh show "Drogerie"List names support partial case-insensitive matching, so "einkauf" matches "Einkaufsliste".
If no list is specified, the default_list from the config is used.
Append --json to lists and show for raw JSON:
scripts/bring.sh lists --json
scripts/bring.sh show --json
scripts/bring.sh show "Einkaufsliste" --json
complete moves items to "recently purchased" (like checking off in the app)remove deletes items entirely from the list~/.cache/bring/token.json and auto-refreshedcountry in credentials.json controls the item catalog language (default: DE)remove fails with "not found", suggest the user check the exact item name with showGenerated Feb 26, 2026
A family uses the Bring! skill to maintain a shared grocery list that syncs instantly across all members' devices. One member can add items via chat while another checks the list in the app, reducing miscommunication and ensuring nothing is forgotten during shopping trips. This is ideal for households with multiple shoppers or busy schedules.
Caregivers or family members assist elderly or disabled individuals by managing their shopping lists remotely through chat commands. The skill allows easy addition or removal of items without requiring the user to navigate apps, enhancing independence and convenience for those with limited mobility or tech skills.
Small businesses or teams use the Bring! skill to track office supplies by maintaining a shared list for items like stationery, snacks, or cleaning products. Employees can add needs via chat, and an admin can review and purchase items, streamlining inventory management without dedicated software.
Event planners or hosts manage shopping lists for parties, weddings, or corporate events by adding items across multiple categories (e.g., food, decorations, utensils). The skill supports batch operations and default lists, helping teams coordinate purchases efficiently and avoid last-minute rushes.
Individuals following specific diets or meal plans use the skill to organize weekly grocery shopping based on recipes. They can add ingredients with quantities, check off items as they shop, and maintain separate lists for different stores (e.g., grocery vs. specialty markets), saving time and reducing food waste.
Offer a basic version of the AI agent skill for free, with premium features like advanced list analytics, integration with recipe apps, or priority support for a monthly fee. Revenue comes from subscriptions, targeting families and small businesses willing to pay for enhanced functionality and convenience.
Partner with grocery stores or delivery services to integrate direct purchasing options within the skill. Revenue is generated through affiliate commissions or referral fees when users buy items from partnered retailers, leveraging the skill's user base for targeted marketing and seamless shopping experiences.
License the skill to larger organizations, such as healthcare providers or corporate offices, for internal use. Revenue comes from one-time licensing fees or annual contracts, with added value through customization, security features, and dedicated support for managing shared resources across teams.
๐ฌ Integration Tip
Ensure users understand the need for a direct Bring! password (not SSO) and guide them through the initial setup with clear, step-by-step instructions to avoid confusion.
Monitor product prices across Amazon, eBay, Walmart, and Best Buy to identify arbitrage opportunities and profit margins. Use when finding products to flip, monitoring competitor pricing, tracking price history, identifying arbitrage opportunities, or setting automated price alerts.
Shopify integration - currently under maintenance. Contact founders@maton.ai for assistance.
Find and compare products online (Google Shopping) and locally (stores near you). Auto-selects best products based on price, ratings, availability, and preferences. Generates shopping list with buy links and store locations. Use when asked to shop for products, find best deals, compare prices, or locate items locally. Supports budget constraints (low/medium/high or "$X"), preference filtering (brand, features, color), and dual-mode search (online + local stores).
Monitor CamelCamelCamel price drop alerts via RSS and send Telegram notifications when items go on sale. Use when setting up automatic price tracking for Amazon products with CamelCamelCamel price alerts.
Navigate Amazon for buying, selling, and affiliating using price tracking, listing optimization, deal analysis, and affiliate link management.
Manage Shopify store data including orders, products, variants, customers, inventory, fulfillments, refunds, returns, and transactions via the Admin REST API.