技能 connector-googlemail

📦

connector-googlemail

Name: connector-googlemail
Author: caffeinelabs

v0.2.3 内容修订 r1 高风险 ⚙️ 外部命令🌐 网络访问📁 文件系统访问

Build Gmail Connections for Caffeine Apps

Gmail integrations require careful OAuth, token storage, and callback handling. This skill provides a complete Motoko and frontend recipe for connecting accounts and sending email.

支持: Claude Codex Code(CC)

⚠️ 38 差

安装前请停下并请求确认。

请审查安装计划，并在更改文件前获得用户明确同意。

使用我的智能体安装

将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。

智能体请求

Review the Skillstore skill "connector-googlemail" from https://skillstore.io/skills/caffeinelabs-connector-googlemail.md and its manifest at https://skillstore.io/api/skills/caffeinelabs-connector-googlemail/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

你的智能体仍应展示其计划，并按安全策略请求必要确认。

Agent 可读资源

当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。

Markdown 详情 GET /skills/caffeinelabs-connector-googlemail.md 已签名 manifest GET /api/skills/caffeinelabs-connector-googlemail/manifest 已签名 lockfile GET /api/skills/caffeinelabs-connector-googlemail/lockfile

测试它

正在使用“connector-googlemail”。 Build a send-only Gmail connector for signed-in users.

预期结果:

Dependencies use the documented Gmail, OAuth, and authorization package versions.
Each user completes a PKCE flow and receives caller-keyed backend token storage.
The send operation uses the Gmail send scope and one refresh attempt after HTTP 401.
The frontend includes reachable settings and callback routes.

正在使用“connector-googlemail”。 Combine Gmail sending with Google Calendar access.

预期结果:

One admin credential set serves both Google services.
One callback exchanges the authorization code for a shared per-user connection.
The consent request contains the union of required Gmail and Calendar scopes.
Each API creates its own non-replicated client configuration from the shared token.

安全审计

高风险

v1 • 2026/7/23 打开版本化报告

All 255 static findings are false positives caused by Markdown backticks, documented Google and Mops URLs, fixed relative links/imports, ellipses, and Gmail or OIDC terminology. Semantic review found unvalidated RFC 5322 headers and a disconnect flow that deletes local state without revoking Google's refresh token.

已扫描文件

764

分析行数

复核项

已忽略误报

已确认安全问题 (2)

高

SKILL.md:390-392

RFC 5322 Header Injection

The sample concatenates `to` and `subject` directly into RFC 5322 headers. Newlines can inject headers, add recipients, or alter message structure.

Lines 390-392 show direct concatenation with no CR or LF validation before the message is sent.

中

SKILL.md:303-307

Disconnect Does Not Revoke Google Token

The disconnect endpoint removes the map entry without revoking the Google refresh token. A previously exposed token remains usable after users disconnect.

Lines 303-307 only remove local state and contain no Google token revocation call.

风险因素

⚙️ 外部命令 (50)

🌐 网络访问 (20)

📁 文件系统访问 (8)

SKILL.md:46 SKILL.md:234 SKILL.md:337 SKILL.md:562 SKILL.md:599 SKILL.md:734 SKILL.md:742 SKILL.md:763

审计者: codex

分享与引用此报告

分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。

打开版本化报告

复制报告链接

https://skillstore.io/skills/caffeinelabs-connector-googlemail/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/caffeinelabs-connector-googlemail/security.svg)](https://skillstore.io/skills/caffeinelabs-connector-googlemail?utm_source=security_passport_badge)

HTML 徽章

<a href="https://skillstore.io/skills/caffeinelabs-connector-googlemail?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/caffeinelabs-connector-googlemail/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

嵌入卡片

<iframe src="https://skillstore.io/embed/skills/caffeinelabs-connector-googlemail.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

学术引用 (APA · BibTeX · CFF)

APA 引用

caffeinelabs. (2026). connector-googlemail security audit report (audit version 1) [Author version 0.2.3]. Skillstore. https://skillstore.io/skills/caffeinelabs-connector-googlemail/audits/1

BibTeX 引用

@techreport{caffeinelabs-caffeinelabs-connector-googlemail-2026,
  author = {caffeinelabs},
  title = {connector-googlemail security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/caffeinelabs-connector-googlemail/audits/1},
  note = {Author version 0.2.3}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "connector-googlemail security audit report (audit version 1)"
version: "0.2.3"
type: report
authors:
  - name: "caffeinelabs"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/caffeinelabs-connector-googlemail/audits/1"
identifiers:
  - type: other
    value: "skillstore:caffeinelabs-connector-googlemail:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 评分

评分依据证据置信度: 中

架构

100

可维护性

内容

社区

规范符合性

你能构建什么

Add Gmail Sending

Implement authenticated email sending from each user's Gmail account with minimal scopes and automatic token refresh.

Build OAuth Screens

Create reachable credential settings and callback routes that preserve OAuth state and wait for actor readiness.

Combine Google Services

Share one OAuth connection, credential set, and union scope across Gmail and Google Calendar features.

试试这些提示

Create Send-Only Gmail

Build a send-only Gmail connector for my Caffeine app. Use the documented Mops versions, per-user PKCE, and the smallest required scopes.

Add OAuth Frontend

Add admin Gmail settings and a real /connect/gmail callback route. Show the exact redirect URI and wait for authenticated actor readiness.

Extend Mailbox Access

Extend the connector to list Gmail messages. Request gmail.readonly only for reading, preserve non-replicated calls, and retry once after a 401.

Unify Gmail and Calendar

Create one shared Google OAuth flow for Gmail and Calendar. Use union scopes, one connection map, and separate non-replicated client configurations.

最佳实践

Request only the Gmail scopes required by implemented operations.
Keep client secrets and bearer tokens in the canister behind caller and admin checks.
Use one exact callback URI, generate state on the backend, and validate it before token exchange.

避免

Do not hand-roll Google HTTP requests when the documented OAuth and Gmail packages provide the operation.
Do not return client secrets, access tokens, refresh tokens, or complete connection records to the frontend.
Do not create separate OAuth flows for Gmail and Calendar when both use the same Google account.

常见问题

Which applications does this skill support?

It supports Caffeine AI applications written in Motoko for the Internet Computer.

Whose address sends the email?

Messages are sent from the signed-in user's connected Gmail account, not a shared application mailbox.

Which scopes are required for sending?

Use openid, email, and gmail.send. Add gmail.readonly only when the application reads mailbox data.

Can the frontend access OAuth tokens?

No. The recipe keeps tokens in caller-keyed canister state and returns only status, email address, and authorization URLs.

Does disconnect revoke Google access?

No. The sample removes local connection state only. Production applications should revoke the Google refresh token before deletion.

How should Gmail and Calendar share OAuth?

Use one credential set, one callback route, union scopes, and one per-user connection shared by both service clients.

开发者详情

作者

caffeinelabs

许可证

MIT

作者版本

v0.2.3

Skillstore 修订

仓库

https://github.com/caffeinelabs/skills/tree/10fb452613c797633b8cb33639fc9a754a138039/skills/connector-googlemail

引用

f32f934280aa94e399d875d7cf7b2ed16d1b82a3

维护新鲜度

2026/7/23

使用量

0 次下载 · 0 次浏览

文件结构

📄 SKILL.md