Token导航 LogoToken导航TokenDH.com
开发敏感数据github未标认证来源可访问许可证需确认审计提醒

agentmailagentmail 邮件管理

Agent Skill

agentmail 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

475

周安装

20

GitHub Stars

4

下载量

166
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:agentmail(agentmail 邮件管理)
来源仓库:https://github.com/alphaonedev/openclaw-graph
仓库路径:skills/agentmail
安装命令:
npx skills add https://github.com/alphaonedev/openclaw-graph --skill agentmail
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/alphaonedev/openclaw-graph --skill agentmail

简介

agentmail 实现 AI 自主管理邮件,包括分类、回复起草与调度发送。

  • 适合处理高并发收件箱、客户支持自动化或个人生产力提升任务。
  • 具备基于内容或关键词的智能分类、模板化回复及定时发送功能。
  • 安装命令为 npx skills add https://github.com/alphaonedev/openclaw-graph --skill agentmail。
  • 使用前请确认邮箱访问权限,并评估对现有工作流的潜在影响。

SKILL.md

agentmail

Purpose

This skill enables an AI agent to autonomously manage emails, including classification, response drafting, and scheduling, using AI-driven automation for efficient email handling.

When to Use

Use this skill for high-volume email inboxes, automated customer support, personal productivity workflows, or integrating email tasks into broader AI agent operations to reduce manual intervention.

Key Capabilities

  • Classify emails based on content, sender, or keywords using machine learning models.
  • Draft response emails with customizable templates and tone adjustments.
  • Schedule email sends or follow-ups based on user-defined rules or calendar integration.
  • Manage email threads by summarizing, prioritizing, or archiving based on criteria.
  • Integrate with email providers via APIs for real-time operations.

Usage Patterns

To use agentmail, invoke it via CLI or API calls, passing necessary parameters like email IDs or content. Always set the API key via environment variable $AGENTMAIL_API_KEY. For CLI, prefix commands with authentication flags. Example pattern: Fetch an email, classify it, draft a response, then schedule if needed. Chain commands in scripts for automation.

Common Commands/API

CLI commands require Node.js environment; install via npm install agentmail-cli. API endpoints are under https://api.openclaw.com/agentmail/v1.

  • Classify an email: CLI: agentmail classify --email-id 12345 --key $AGENTMAIL_API_KEY API: POST /api/agentmail/classify with JSON body: {"email_id": "12345", "api_key": "$AGENTMAIL_API_KEY"} Code snippet: curl -X POST https://api.openclaw.com/agentmail/v1/classify \ -H "Content-Type: application/json" \ -d '{"email_id": "12345", "api_key": "'$AGENTMAIL_API_KEY'"}'
  • Draft a response: CLI: agentmail draft --email-id 12345 --tone professional --key $AGENTMAIL_API_KEY API: POST /api/agentmail/draft with body: {"email_id": "12345", "tone": "professional", "api_key": "$AGENTMAIL_API_KEY"} Code snippet: const response = await fetch('https://api.openclaw.com/agentmail/v1/draft', {method: 'POST', headers: {'Content-Type': 'application/json'}, body: JSON.stringify({email_id: '12345', tone: 'professional', api_key: process.env.AGENTMAIL_API_KEY})});
  • Schedule an email: CLI: agentmail schedule --email-content "Reply text" --send-at "2023-10-01T10:00:00Z" --key $AGENTMAIL_API_KEY API: POST /api/agentmail/schedule with body: {"email_content": "Reply text", "send_at": "2023-10-01T10:00:00Z", "api_key": "$AGENTMAIL_API_KEY"} Config format: Use JSON for scheduling rules, e.g., {"rules": [{"condition": "priority>high", "action": "schedule in 2 hours"}]}.

Integration Notes

Integrate agentmail with email services like Gmail or Outlook by providing OAuth tokens via config files (e.g., config.json: {"provider": "gmail", "token": "$GMAIL_TOKEN"}). For AI agent workflows, use webhooks to trigger on new emails (e.g., POST to /api/agentmail/webhook). Ensure compatibility by matching API versions; handle dependencies like Node.js v14+. To combine with other skills, export results as JSON and pipe to next command, e.g., agentmail classify... | jq '.category' | other-skill-process.

Error Handling

Check for HTTP status codes: 401 for auth failures (retry with $AGENTMAIL_API_KEY), 404 for missing emails (log and skip), 500 for server errors (exponential backoff). In CLI, use --verbose flag for detailed logs. Handle common issues like rate limits by adding delays (e.g., sleep 5 seconds after 429 response). Validate inputs before calls, e.g., ensure email IDs are strings via regex check: if (!emailId.match(/^\d+$/)) throw new Error('Invalid email ID');. Use try-catch in scripts for graceful recovery.

Concrete Usage Examples

  1. Classify and respond to a support ticket email: First, classify: agentmail classify --email-id 67890 --key $AGENTMAIL_API_KEY. If classified as "support", draft: agentmail draft --email-id 67890 --tone helpful --key $AGENTMAIL_API_KEY. Then schedule: agentmail schedule --email-content $(cat response.txt) --send-at now --key $AGENTMAIL_API_KEY. This automates ticket responses in a helpdesk workflow.
  2. Manage personal email scheduling: Fetch unread emails via API, classify them: curl -X POST https://api.openclaw.com/agentmail/v1/classify -d '{"email_id": "54321", "api_key": "'$AGENTMAIL_API_KEY'"}'. For high-priority, draft and schedule: agentmail draft --email-id 54321 --tone formal --key $AGENTMAIL_API_KEY; agentmail schedule --email-content "Follow up" --send-at "tomorrow" --key $AGENTMAIL_API_KEY. Use in a daily script for inbox zero.

Graph Relationships

  • Related to: email (direct), ai (cluster), agent (cluster), automation (tag).
  • Connected clusters: community (same as this skill).
  • Dependencies: May require skills like "email-parser" for input preprocessing or "scheduler" for advanced timing.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.1%
按下载量换算62

Claude

29.91%
按下载量换算50

Cursor

16.25%
按下载量换算27

Gemini CLI

9.28%
按下载量换算15

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

可疑

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills