docs(gmail): clarify Gmail web URL sync IDs

[Lubrsy706]

Summary

Refs #790.

This adds a docs-only clarification that recent Gmail web URL IDs such as FMfcgz... are browser sync IDs, not Gmail API message/thread IDs. It points users and agents toward listing/searching messages first when they need an API ID.

Updated:

• README.md helper examples
• skills/gws-gmail/SKILL.md
• skills/gws-gmail-read/SKILL.md
• changeset for the docs patch

Testing

• git diff --check

I did not run cargo test because this is a docs-only change and this machine does not currently have the Rust toolchain installed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 98cee79

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 introduces documentation updates to prevent user confusion regarding Gmail identifiers. It clarifies the distinction between browser-specific sync IDs found in web URLs and the actual message or thread IDs required by the Gmail API, providing actionable examples for users to obtain the correct identifiers.

Highlights

• Documentation Clarification: Added explicit warnings across documentation files clarifying that Gmail web URL sync IDs (e.g., 'FMfcgz...') are not valid Gmail API message or thread IDs.
• Guidance for API Usage: Provided clear instructions and examples on how to search or list messages to retrieve the correct API IDs when users only have a browser URL.

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 updates the documentation across the README and skill-specific markdown files to clarify that Gmail web URL sync IDs (e.g., FMfcgz...) are not compatible with the Gmail API. It provides guidance and examples on how to retrieve the correct API message or thread IDs using search queries. I have no feedback to provide.

[googleworkspace-bot]

/gemini review

[gemini-code-assist]

Code Review

This pull request updates the documentation across the README and skill files to clarify that Gmail web URL sync IDs are not compatible with the Gmail API. It provides guidance and examples on how to retrieve the correct API message or thread IDs using search and list commands. I have no feedback to provide as there were no review comments.