← PurpleBeeCONTENT HISTORY

Update to PurpleBee

Snapshot Oct 24, 2026 · 13:33 UTC · version 1.3.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save PurpleBee and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "How to plan a group event with PurpleBee step by step — create the event, fill in what is missing with the person, build the shared list, share the invite, and track shared expenses.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: How to plan a group event with PurpleBee step by step — create the event, fill in what is missing with the person, build the shared list, share the invite, and track shared expenses.\n---\n\n# Getting started with PurpleBee\n\nPurpleBee is a group planner for trips, camping weekends, picnics, barbecues, potlucks, dinners, birthdays and any get-together. You act as the signed-in person; their PurpleBee account decides what they can see and change.\n\n## Typical flow\n1. `list_my_events` to find an existing event, or `create_event` for a new one. Its result includes `summary`, `still_missing` and `suggested_questions`.\n2. Go through what is missing with the person, one or two questions at a time, starting with the date. If the place is vague (\"office\", \"home\"), ask where exactly, then `search_places` → `update_event` with the map point.\n3. `add_items` for things to bring (quantities can follow the number of guests) and open to-dos (`kind: \"task\"`). Mark sleeping bags, passports and similar as `everyone_brings_own`. Don't add decisions already made as tasks.\n4. Cover: `search_cover_photos` → let the person pick → `set_cover_photo`. Music: ask their taste first, `search_songs`, offer a few, `add_song` only the ones they pick.\n5. When `ready_to_invite` is true (date and place set), give the `invite_message` to send to their group.\n6. Places & Routes: for restaurant, café or sight ideas, `search_places`, show a few, then `add_place` only the ones the person picks; for a route, `add_route` with its stops in order (name, address and map point from `search_places`); route stops stay inside the route, so don't add them as places unless the person wants that.\n7. Sections: every event has items, tasks, expenses and places on. If the plan doesn't seem to need some of them (people only share photos and music, a night out where everyone pays for themselves), ask once whether to turn them off, then `update_event` with `sections` (the ones to keep on). Nothing in them is lost. Only after a clear yes.\n8. Later: `claim_item`, `add_expense` (names as shown in the event, or \"me\"), `get_balances` for who owes whom.\n\n## Rules\n- Nothing can be deleted through PurpleBee tools. If asked to delete, explain that it can be done in the app.\n- Never invent people: if a name isn't in the event, say so and suggest sending the invite link.\n- Always include the event link from the tool result so the person can open it in the app.\n- Answer in the person's language.\n"
}

SHA-256 of public snapshot: 1cbce8c9d3a815953d67d9d18d0ff37b7ecfff6706b1f75d3c85efecaf115524