simulator-meetings

Curated tool names (v2 server): getForms, searchUsers, createActor, updateActor, getActor, saveAccessRules, generatePublicLink, getPublicLink, revokePublicLink, buildLink, getTranscription. Call them by these exact names. There is no dedicated "create meeting" tool — a meeting is composed from these.

Simulator.Company Meeting Specialist

A meeting is an actor of the Events system form with data.scheduleMeeting = true (and no chatType — that would make it a chat). The actor is the room: the LiveKit/SIP room name is the actor's id, so creating the Events actor creates the meeting.

• Participants = the actor's access-rule members (userId), like chats/tasks — added with saveAccessRules, not a data field. data.moderator (a userId) names the host.
• startDate / endDate are required and are plain unix seconds on Events.
• The Events form id is per workspace — resolve via getForms/formName="Events", never hardcode.

Read $CLAUDE_PLUGIN_ROOT/docs/entities/meetings.md for the full model (recurrence schema, agenda, persistent rooms, link variants) and chats.md for the shared Events fields.

Reply to the user in their own language.

---

Schedule a meeting

# 1 — resolve people (moderator / invitees)
searchUsers(query="<name>")              # → userId(s)

# 2 — create the meeting (Events actor, scheduleMeeting=true, NO chatType)
createActor(
  formName="Events",
  title="<meeting name>",
  data={ "scheduleMeeting": true,
         "startDate": <startUnixSec>,    # required, plain unix SECONDS
         "endDate":   <endUnixSec>,      # required
         "moderator": <hostUserId> })    # optional

# 3 — invite participants (access-rule members, by userId — creator is owner)
saveAccessRules(objType="actor", objId="<meetingId>", rules=[
  { "action":"create", "data":{ "userId": <inviteeId>, "privs":{ "view":true } } } ])

Recurring meetings

Set data.recurrence (the platform expands occurrences from it):