Agent Skills
› fanfan-de/anybox
› google-calendar-group-scheduler
google-calendar-group-scheduler
GitHub用于协调多人会议时间，通过对比参会者日历数据，结合约束条件与排名启发式规则，筛选并推荐最佳会议时段及备选房间。
Trigger Scenarios
用户希望安排多人会议
需要比较多个候选时间段
寻找最佳妥协时间
添加会议室检查
Install
npx skills add fanfan-de/anybox --skill google-calendar-group-scheduler -g -y
SKILL.md
Frontmatter
{
"name": "google-calendar-group-scheduler",
"description": "Find and rank good meeting times for multiple people using connected Google Calendar data. Use when the user wants to schedule a group meeting, compare candidate slots across several attendees, find the best compromise time, or add a room check after narrowing the attendee-compatible options."
}
Google Calendar Group Scheduler
Use this skill when the scheduling problem is the task.
Relevant Actions
- Use
get_availabilityfor attendee and room/resource busy windows once you know the concrete calendar IDs. - Use
search_eventswhen you need event context, candidate-room history, or a clearer read on what is creating conflicts. - Use
read_eventorsearch_events_all_fieldswhen the attendee emails, manager contact, room email, or full source-event details need to be recovered from existing calendar events.
Workflow
- Ground the scheduling problem first: date window, duration, timezone, required attendees, optional attendees, and any hard constraints such as "this week", "afternoons only", or "avoid lunch".
- Normalize the request into explicit candidate windows before ranking anything.
- If attendee or room identities are referenced indirectly, such as "my manager", "same attendees", or "the room we usually use", search a bounded relevant window and read the likely source event before asking the user for contact details.
- Rank slots, do not enumerate everything. Optimize for a short list of strong options.
- Prefer slots that minimize conflict cost, are reasonably fair across timezones, and avoid fragmenting the day for the most constrained attendees.
- If no perfect slot exists, return the best compromise and state exactly who is impacted.
- If the meeting also needs a room, first narrow to attendee-compatible slots, then check likely rooms or resources against those shortlisted times.
Ranking Heuristics
- Favor required-attendee fit over optional-attendee fit.
- Favor slots that avoid very early or very late local times for distributed attendees.
- Favor slots that preserve lunch and avoid consuming the only large free block in someone's day unless the meeting is clearly important.
- Favor a small number of high-confidence options over a long weak list.
- When two slots are similar, prefer the one that causes less calendar fragmentation.
Output Conventions
- Return 2-4 candidate slots by default.
- For each slot, say why it works and who, if anyone, would be inconvenienced.
- If there is no clean option, say what tradeoff the best slot is making.
Version History
- 08dc189 Current 2026-07-05 19:00
