Update to HolyCRM

{
  "description": "How to use HolyCRM, a church management app, to answer questions about a church's people, visitors, small groups and events, and to add or update visitors with the user's confirmation.",
  "included_files": [],
  "name": "getting-started",
  "skill_md_contents": "---\nname: getting-started\ndescription: How to use HolyCRM, a church management app, to answer questions about a church's people, visitors, small groups and events, and to add or update visitors with the user's confirmation.\n---\n\n# Using HolyCRM\n\nHolyCRM is a church management app. These tools act as the signed-in person, with their own\npermissions in their church: they only see what that person's role can see in the app, and\nrecords of children are never returned.\n\n## Which church\n\n- Call `list_churches` when you don't know the church yet. A person can belong to several.\n- A church may show `ai_allowed: false` with a note: its administrator has not turned on AI\n  assistants (or has blocked this person). Tell the user the note; do not retry.\n- When the person belongs to more than one allowed church, pass `church_id` to every tool, or\n  ask which church they mean.\n\n## Answering questions\n\n- Visitors (first-time guests): `search_visitors`. \"Not contacted yet\" is `contacted: false`.\n  Dates are `YYYY-MM-DD`; compute ranges such as \"last month\" from today's date.\n- People (adult members): `search_people`.\n- Who is missing from small groups: `group_absences`. Groups that met without taking attendance\n  are listed separately; say so instead of guessing.\n- Events: `list_events`. Times are UTC; convert them to the user's time zone when you show them.\n\n## Making changes\n\nChanges always take two steps:\n\n1. Call the prepare tool (`create_visitor`, `log_visitor_followup` or `set_visitor_stage`).\n   It changes nothing and returns a `summary`, the exact `changes` and a `confirmation_token`.\n   For a new visitor it also lists possible duplicates: mention them.\n2. Show the user the summary and changes, and ask them to confirm. Only after they clearly say\n   yes, call `confirm_change` with the token. Never confirm on your own initiative.\n\nTokens expire after 10 minutes and work once; if one fails, prepare the change again.\nTurning a visitor into a member, and deleting anything, are done in the HolyCRM app, not here.\n"
}