chore: sync skills with Discovery API

[googleworkspace-bot]

Automated PR — the Google Discovery API specs have changed and the
generated skill files are out of date.

Created by the Generate Skills workflow (generate-skills.yml).

[changeset-bot]

🦋 Changeset detected

Latest commit: d35c61e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@googleworkspace/cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[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 updates the generated skill documentation to align with the latest Google Discovery API specifications. The changes include adding new API methods to the documentation, clarifying existing parameter behaviors, and providing better guidance for service-specific operations to ensure the CLI documentation remains accurate and helpful for users.

Highlights

• API Specification Sync: Updated generated skill documentation to reflect the latest changes from the Google Discovery API.
• New Functionality: Added support for new methods across several services, including 'transferOwnership' in Calendar, 'findGroupChats' and 'availability' in Chat, and various approval management methods in Drive.
• Documentation Improvements: Refined parameter descriptions and usage notes for Sheets, Gmail, and Classroom to improve clarity and accuracy.

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 the 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 counterproductive. 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.

Footnotes

1. Review the Generative AI Prohibited Use Policy, 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 syncs generated skills with the latest Google Discovery API specifications, updating the documentation (SKILL.md files) for Calendar, Chat, Classroom, Drive, Gmail, and Sheets Append. The review feedback highlights a formatting issue in the newly added Calendar transferOwnership documentation, where the authorization scopes list is broken and needs proper indentation.

[gemini-code-assist]

The formatting for this list of authorization scopes is broken, making it hard to read. The scopes should be properly indented as a sub-list, and the subsequent text should be separated for clarity.

Suggested change

	- https://www.googleapis.com/auth/calendar
	- https://www.googleapis.com/auth/calendar.calendars In the request, set useAdminAccess to true. The secondary calendar must be active to be transferred. Transferring disabled or deleted calendars isn't supported.
	- `https://www.googleapis.com/auth/calendar`
	- `https://www.googleapis.com/auth/calendar.calendars`
	In the request, set `useAdminAccess` to `true`. The secondary calendar must be active to be transferred. Transferring disabled or deleted calendars isn't supported.