← 返回 Skills 市场
nitansde

Safe Email

作者 Nitan SDE · GitHub ↗ · v1.0.7 · MIT-0
cross-platform ✓ 安全检测通过
364
总下载
2
收藏
3
当前安装
8
版本数
在 OpenClaw 中安装
/install safe-email
功能描述
Privacy-first workflow for processing explicitly forwarded emails via IMAP in a dedicated inbox. Use only when the user explicitly asks to process the latest...
安全使用建议
This skill appears to do what it says: it will connect to an IMAP mailbox (using himalaya and the provided IMAP username + app password) and read the newest forwarded message when you explicitly ask it to. Before installing: (1) Use a dedicated inbox (as recommended) so the app password only exposes that mailbox. (2) Provide the app password via your runtime secret store (do not embed it in the skill). (3) Be aware that the app password grants full mailbox access—rotate/delete it if you stop using the skill. (4) Confirm the agent enforces the explicit-trigger rule and that you are comfortable with the agent's access to the mailbox; ambiguity in what counts as the “relevant” message could lead to reading an unintended email. (5) If you need stronger guarantees, consider running this skill only in an environment you control or using short-lived credentials.
功能分析
Type: OpenClaw Skill Name: safe-email Version: 1.0.7 The 'safe-email' skill is a privacy-focused tool designed to extract structured information from forwarded emails using the 'himalaya' CLI. The instructions in SKILL.md explicitly enforce security best practices, such as requiring manual triggers, forbidding background polling, and mandating user consent for email deletion. No evidence of malicious intent, data exfiltration, or prompt injection was found.
能力评估
Purpose & Capability
Name/description (privacy-first IMAP extraction) matches the declared requirements: it asks for an IMAP CLI (himalaya) and IMAP credentials (username + app password), which are exactly what a mailbox-reading skill needs.
Instruction Scope
SKILL.md restricts behavior (explicit trigger required, read only newest relevant message, optional deletion only with consent) and references only the declared IMAP credentials. However, some language is intentionally discretionary (e.g., deciding which message is the "newest relevant candidate"), which places trust in the agent's judgment. The policy relies on runtime enforcement rather than technical constraints, so there's a small risk the agent could read an unintended message if the trigger or relevance test is ambiguous.
Install Mechanism
Instruction-only skill with no install spec or downloads; lowest-risk install posture. It assumes a preinstalled himalaya binary, which is reasonable for an IMAP CLI workflow.
Credentials
Requested env vars (SAFE_EMAIL_IMAP_USERNAME and SAFE_EMAIL_IMAP_APP_PASSWORD) are proportional to the task. Note that an IMAP app password grants full access to the dedicated mailbox, so it is high-sensitivity data and should be provisioned securely and rotated if compromised. The metadata did not declare a primary credential, but that is not inconsistent.
Persistence & Privilege
always is false and the skill requires explicit triggers and forbids auto-polling in prose/metadata, limiting continual background access. Autonomous invocation is allowed by default, but the skill's explicit-trigger policy reduces risk.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install safe-email
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /safe-email 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v1.0.7
Scope simplification: removed calendar/reminder requirements and actions. Skill is now extraction-only (IMAP forwarded-email parsing + suggested next steps), with explicit-trigger and optional-deletion safeguards.
v1.0.6
Registry consistency fix: declared calendar/reminder config refs in requires.env and aligned SKILL.md credential section to metadata-declared inputs only.
v1.0.5
Metadata clarity update: added explicit top-level credentials/env declarations plus mirrored openclaw.requires credentials/env fields to eliminate registry ambiguity.
v1.0.4
Metadata coherence fix: moved required credentials and secret handling details under openclaw.requires for clearer registry parsing; retained privacy/compliance constraints.
v1.0.3
Consistency fix: aligned manifest and instructions on credentials/secrets. Credentials are required; secret source is flexible (env, keychain, secure refs, oauth store). Removed env-only implication and clarified policy.
v1.0.2
Compliance hardening: added required env/config declarations for IMAP + calendar/reminder credentials; clarified dedicated-forwarded-inbox requirement; added duplicate/timezone safety checks and explicit deletion-consent policy wording.
v1.0.1
Compliance update: declared required credentials/permissions in metadata; clarified explicit-trigger-only policy; made destructive email deletion opt-in with explicit consent.
v1.0.0
Initial release: privacy-first IMAP email workflow for forwarded mail to calendar/reminder with explicit-trigger-only and post-processing deletion.
元数据
Slug safe-email
版本 1.0.7
许可证 MIT-0
累计安装 3
当前安装数 3
历史版本数 8
常见问题

Safe Email 是什么?

Privacy-first workflow for processing explicitly forwarded emails via IMAP in a dedicated inbox. Use only when the user explicitly asks to process the latest... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 364 次。

如何安装 Safe Email?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install safe-email」即可一键安装,无需额外配置。

Safe Email 是免费的吗?

是的,Safe Email 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Safe Email 支持哪些平台?

Safe Email 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。

谁开发了 Safe Email?

由 Nitan SDE(@nitansde)开发并维护,当前版本 v1.0.7。

💬 留言讨论