Get local help for shifts and tasks (Blossomai.org)

**Judgement:** A capable, well-scoped connector to the Blossom local jobs marketplace that is functionally strong and conversationally well-designed, but carries notable privacy and safety considerations due to extensive personal data collection and a permanent full-access API key. **What it’s good for** - When a user explicitly wants to use Blossom (or is comfortable signing up) to **hire local help** or **find nearby work**. - Scenarios needing structured job posts and applications: local shifts, casual work, small-business staffing. - Users comfortable sharing their **name, email, mobile number, full address, and a chosen password** with an external service. **Key risks & constraints** - **High PII exposure:** Collects and transmits name, surname, email, mobile number, street/city/postcode/country, and a passKey (password) to Blossom’s servers. This must be clearly disclosed to the user before proceeding. - **Password sensitivity:** Users choose a `passKey` used for account authentication. They should be warned **not to reuse important passwords** (e.g., email, banking) and to treat this as a unique credential for Blossom only. - **Permanent full-access API key:** The returned `apiKey` grants ongoing full account access. The skill correctly scopes it to the current session only, but it increases the impact of any potential compromise on the Blossom side. - **Offline and employment safety:** The platform facilitates real-world work with strangers. There is inherent risk of scams, unfair work conditions, or unsafe meetings. Users should be reminded to: - Verify employers/roles where possible. - Meet in public or safe locations if appropriate. - Avoid sharing extra sensitive data (ID documents, financial details) through unofficial channels. - **Legal/compliance:** For job-seekers, `rightToWork` must be `true`. The assistant must not encourage users to misrepresent their legal right to work and should remind them to comply with local labor and immigration laws. - **Geographic limitations:** Appears optimized for certain regions (e.g., GBP currency, UK-style phone and postcode examples). Utility may be limited outside supported areas. **Recommended usage scenarios** - Use when the user clearly says things like **“post a job,” “hire staff,” “find me work near [location],” “apply to that role,”** and explicitly agrees to share the necessary personal information with Blossom. - Prefer it for users who: - Understand they are creating or using a **Blossom account**. - Are comfortable with an external service storing their data and job history. - Avoid or be very cautious when: - The user is privacy-sensitive or does not want to share their full address or contact details. - The user is a minor or seems vulnerable; consider safer, more moderated options. - The request does not truly require account-based job matching (e.g., they just want generic job-hunting advice).