docs: mandate calendarId='primary' in calendar skill

[allenhutchison]

Summary

Agents frequently omit calendarId on their first calendar tool call, causing a wasted execution turn when the call fails or requires clarification. This update explicitly mandates passing calendarId: "primary" on every calendar tool call.

Changes

• New "Always Pass calendarId" section — Added after the timezone workflow with a bold mandate and explicit examples for every tool that accepts calendarId
• Updated "Understanding Next Meeting" — The listEvents guidance now includes calendarId: "primary" in its instructions
• Updated "Creating Events" key parameters — Changed from "Defaults to primary calendar if omitted" to "Always pass "primary""

Motivation

Trace analysis of calendar skill usage showed agents often forget to include calendarId on the first call, requiring a retry and wasting an execution turn. This small skill update should eliminate that pattern.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the robustness and efficiency of calendar skill interactions by enforcing the explicit inclusion of calendarId: "primary" in all calendar tool calls. This change aims to prevent common errors and reduce unnecessary execution turns that occur when agents fail to provide this parameter, thereby streamlining the user experience and improving API call reliability.

Highlights

• Mandatory calendarId: Introduced a new section "Always Pass calendarId" to explicitly mandate the use of calendarId: "primary" for all relevant calendar tool calls.
• Updated listEvents guidance: Updated the guidance for "Understanding Next Meeting" to include calendarId: "primary" when using calendar.listEvents.
• Modified createEvent parameters: Modified the "Creating Events" key parameters to change the calendarId instruction from "Defaults to primary calendar if omitted" to "Always pass "primary"".

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• skills/calendar/SKILL.md
  • Added a new section titled "Always Pass calendarId" which provides a strong mandate and examples for including calendarId: "primary" in all relevant calendar tool calls.
  • Updated the guidance in the "Understanding Next Meeting" section to explicitly include calendarId: "primary" in the calendar.listEvents call.
  • Modified the description for the calendarId parameter under "Creating Events" to explicitly state "Always pass "primary"" instead of noting a default behavior.

Activity

• No human activity has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a clear mandate for agents to always pass calendarId: 'primary' in calendar tool calls, which is a valuable change to improve reliability and prevent wasted actions. The documentation changes are clear and well-explained. I've suggested one addition to make the new rule even more comprehensive.

_{Note: Security Review has been skipped due to the limited scope of the PR.}