Skip to content

Commit 57dcb5d

Browse files
Update Calendly skill to always fetch invitees for event details
The event `name` field only shows the event type name (e.g. "Meeting"), not who booked it or what it's about. Added explicit instructions to always fetch the invitees sub-resource for meaningful event details. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent b947e2b commit 57dcb5d

1 file changed

Lines changed: 11 additions & 1 deletion

File tree

skills/calendly/SKILL.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,12 +98,22 @@ Response fields per event type in `collection[]`:
9898
- `duration` — duration in minutes
9999
- `active` — whether this event type is active
100100

101+
## IMPORTANT: Always fetch invitees
102+
103+
The `name` field on scheduled events is just the event type name (e.g. "Meeting") and is the SAME for every event. It does NOT tell you what the meeting is about or who it's with. You MUST always fetch invitees (Step 3) for each event to get meaningful details:
104+
105+
- The invitee `name` field tells you who the meeting is with (e.g. "RunAnywhere Celebration", "Ajay Negi")
106+
- The `questions_and_answers` field contains notes about the meeting purpose
107+
- Without invitee data, you cannot accurately describe any event to the user
108+
101109
## Common workflows
102110

103-
**Fetch today's meetings:**
111+
**Fetch today's meetings (ALWAYS use this full flow):**
104112

105113
1. `GET /users/me` → extract `resource.uri`
106114
2. `GET /scheduled_events?user=<uri>&min_start_time=<today_start>&max_start_time=<today_end>&status=active`
115+
3. For EACH event in the response, `GET /scheduled_events/<uuid>/invitees` to get who it's with and what it's about
116+
4. Present the invitee name and notes to the user, NOT the generic event type name
107117

108118
**Get details about who booked a meeting:**
109119

0 commit comments

Comments
 (0)