Send Google Chat messages via webhook with text, rich cards, and threaded replies.
Works with
Supports text messages with Google Chat formatting ( *bold* , _italic_ , `code` , <url|text> links), rich card messages (cardsV2) with headers, sections, and widgets, and threaded conversations using threadKey
Includes five widget types: text paragraphs, decorated text (label + value with icons), button lists, images, and dividers; reference documentation for all widget types and available icons
P
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongoogle-chat-messagesExecute the skills CLI command in your project's root directory to begin installation:
Fetches google-chat-messages from jezweb/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate google-chat-messages. Access via /google-chat-messages in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
695
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
695
stars
Send messages to Google Chat spaces via incoming webhooks. Produces text messages, rich cards (cardsV2), and threaded replies.
In Google Chat:
Store the URL as an environment variable or in your secrets manager — never hardcode.
| Need | Type | Complexity |
|---|---|---|
| Simple notification | Text message | Low |
| Structured info (status, digest) | Card message (cardsV2) | Medium |
| Ongoing updates | Threaded replies | Medium |
| Action buttons (open URL) | Card with buttonList | Medium |
Use assets/webhook-sender.ts for the sender utility. Use assets/card-builder.ts for structured card construction.
Google Chat does NOT use standard Markdown.
| Format | Syntax | Example |
|---|---|---|
| Bold | *text* |
*important* |
| Italic | _text_ |
_emphasis_ |
| Strikethrough | ~text~ |
~removed~ |
| Monospace | `text` |
`code` |
| Code block | ```text``` |
Multi-line code |
| Link | <url|text> |
<https://example.com|Click here> |
| Mention user | <users/USER_ID> |
<users/123456> |
| Mention all | <users/all> |
<users/all> |
Not supported: **double asterisks**, headings (###), blockquotes, tables, images inline.
await sendText(webhookUrl, '*Build Complete*\n\nBranch: `main`\nStatus: Passed\n<https://ci.example.com/123|View Build>');
Cards use the cardsV2 format (recommended over legacy cards).
const message = {
cardsV2: [{
cardId: 'unique-id',
card: {
header: {
title: 'Card Title',
subtitle: 'Optional subtitle',
imageUrl: 'https://example.com/icon.png',
imageType: 'CIRCLE' // or 'SQUARE'
},
sections: [{
header: 'Section Title', // optional
widgets: [
// widgets go here
]
}]
}
}]
};
All widget types available in cardsV2 sections.
Formatted text block. Supports Google Chat formatting (*bold*, _italic_, <url|text>).
{
textParagraph: {
text: '*Status*: All systems operational\n_Last checked_: 5 minutes ago'
}
}
Labelled value with optional icons. Most versatile widget for key-value data.
Basic:
{
decoratedText: {
topLabel: 'Environment',
text: 'Production',
bottomLabel: 'Last deployed 2h ago'
}
}
With start icon:
{
decoratedText: {
topLabel: 'Status',
text: 'Healthy',
startIcon: { knownIcon: 'STAR' }
}
}
With custom icon URL:
{
decoratedText: {
topLabel: 'GitHub',
text: 'PR #142 merged',
startIcon: {
iconUrl: 'https://github.githubassets.com/favicons/favicon.svg',
altText: 'GitHub'
}
}
}
With button:
{
decoratedText: {
topLabel: 'Alert',
text: 'CPU at 95%',
button: {
text: 'View',
onClick: { openLink: { url: 'https://monitoring.example.com' } }
}
}
}
Clickable (whole widget):
{
decoratedText: {
text: 'View full report',
wrapText: true,
onClick: { openLink: { url: 'https://reports.example.com' } }
}
}
With wrap text:
{
decoratedText: {
topLabel: 'Description',
text: 'This is a longer description that should wrap to multiple lines instead of being truncated',
wrapText: true
}
}
One or more action buttons. Buttons open URLs or trigger actions.
Single button:
{
buttonList: {
buttons: [{
text: 'Open Dashboard',
onClick: { openLink: { url: 'https://dashboard.example.com' } }
}]
}
}
Multiple buttons:
{
buttonList: {
buttons: [
{
text: 'Approve',
onClick: { openLink: { url: 'https://app.example.com/approve/123' } },
color: { red: 0, green: 0.5, blue: 0, alpha: 1 }
},
{
text: 'Reject',
onClick: { openLink: { url: 'https://app.example.com/reject/123' } }
}
]
}
}
Button with icon:
{
buttonList: {
buttons: [{
text: 'View on GitHub',
icon: { knownIcon: 'BOOKMARK' },
onClick: { openLink: { url: 'https://github.com/org/repo/pull/42' } }
}]
}
}
Standalone image widget.
{
image: {
imageUrl: 'https://example.com/chart.png',
altText: 'Monthly usage chart'
}
}
Horizontal line separator between widgets.
{ divider: {} }
Sections can be collapsed with only the first N widgets visible:
{
header: 'Details',
collapsible: true,
uncollapsibleWidgetsCount: 2, // Show first 2, collapse rest
widgets: [
{ decoratedText: { topLabel: 'Status', text: 'Active' } },
{ decoratedText: { topLabel: 'Region', text: 'AU' } },
// These start collapsed
{ decoratedText: { topLabel: 'Instance', text: 'prod-01' } },
{ decoratedText: { topLabel: 'Memory', text: '2Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
jezweb/claude-skills
jezweb/claude-skills
kostja94/marketing-skills
jwynia/agent-skills
mindrally/skills
github/awesome-copilot
google-chat-messages fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for google-chat-messages matched our evaluation — installs cleanly and behaves as described in the markdown.
google-chat-messages has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: google-chat-messages is focused, and the summary matches what you get after install.
google-chat-messages is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: google-chat-messages is focused, and the summary matches what you get after install.
google-chat-messages reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added google-chat-messages from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: google-chat-messages is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend google-chat-messages for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 67