Bring! Shopping List App (Unofficial)

**Quick judgment:** Useful but niche skill that gives an agent direct control over Bring! shopping lists through an unofficial email/password API library. Functionally capable for list and item management, but with meaningful reliability and security/TOS risks due to the unofficial nature and credential handling. **What it’s good for** - Automating everyday Bring! tasks: listing lists, reading items, and adding/removing/checking/unchecking items. - Power users who already rely on Bring! and want voice/chat automation or integration into larger assistant workflows. - Environments where storing BRING_EMAIL/BRING_PASSWORD securely in config is acceptable and managed. **Key risks & limitations** - **Unofficial API & fragility:** Relies on the `bring-shopping` npm package and Bring!’s private API; any backend change or anti-bot measure can break the skill without warning. - **Credential sensitivity:** Requires storing raw Bring! email/password. If environment variables or host configuration are mismanaged, this poses an account-compromise risk. - **Possible TOS/anti-automation issues:** As access is unofficial, it may be against Bring!’s Terms of Service or trigger rate limits or account flags in edge cases. - **Scope limited to Bring!:** Only useful for users who already have (and trust the use of) a Bring! account; doesn’t generalize beyond that ecosystem. **Recommended scenarios** - Internal or personal setups where you control the environment, can store credentials securely, and accept the risk of occasional breakage. - Users comfortable creating a dedicated/secondary Bring! account for automation, isolating risk from their primary account. - Assistants that need a lightweight way to keep a single Bring! list (default "Willig" or a specified list) in sync with natural-language user requests.