feat: add Chat skill for Google Chat messaging guidance

[allenhutchison]

Summary

Add a new Chat skill modeled after the Gmail skill, providing behavioral guidance for Google Chat tools.

What's included

• Chat markdown formatting — Supported syntax (*bold*, _italic_, code, links, mentions) and conversion rules for unsupported syntax (**bold** → *bold*, [text](url) → <url|text>)
• Spaces vs. DMs — Tool selection guide for group spaces vs 1:1 DMs
• Threading — How to start, reply to, list, and read threads
• Unread messages — Using unreadOnly and how it resolves the user's lastReadTime
• Space management — Creating named spaces with setUpSpace
• Resource name formats — Quick reference for spaces/, threads/, users/ patterns

Files changed

• skills/chat/SKILL.md — New skill file

[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 a new skill designed to provide comprehensive guidance for interacting with Google Chat. It covers essential aspects of messaging, conversation management, and space administration, ensuring users adhere to Google Chat's specific formatting and operational guidelines.

Highlights

• Chat Markdown Formatting: Detailed rules for supported and unsupported markdown syntax in Google Chat messages, including conversion guidelines for common patterns like bolding, links, and headings.
• Spaces vs. Direct Messages: Guidance on when to use group spaces versus 1:1 direct messages, along with associated tools for finding, listing, sending messages, and creating spaces.
• Threading Mechanics: Explanations and examples for starting new threads, replying to existing ones, listing threads within a space, and retrieving all messages in a specific thread.
• Unread Message Filtering: Instructions on using the unreadOnly parameter for chat.getMessages to filter for unread messages, detailing how it interacts with the user's lastReadTime.
• Space Management: Details on creating new named spaces using chat.setUpSpace, emphasizing the requirement for user resource names (users/{userId}) rather than email addresses.
• Resource Name Formats: A quick reference table for the structured naming conventions used for various Google Chat resources, including spaces, messages, threads, and users.

🧠 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/chat/SKILL.md
  • Added a new skill file providing comprehensive guidance for Google Chat messaging and management.

Activity

• No specific 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 new skill file for Google Chat, providing detailed guidance for an LLM on using the associated tools. The documentation is comprehensive and well-structured. I've provided a few suggestions to enhance the clarity and accuracy of these instructions, which will help prevent potential tool usage errors. My feedback focuses on clarifying a confusing example for list formatting, correcting a minor inaccuracy in the description of the chat.listThreads tool, and adding a crucial instruction for transforming user IDs when creating spaces.

[abhipatel12]

LGTM, do we need to remove the correlating chat section from the workspace context file?