360 Secure SkillHub
360 安全技能中心

QQ Mail

借助 OOMOL 的 oo CLI 与 qq_mail 连接器管理 QQ 邮箱:查看文件夹与邮件计数、搜索和读取邮件、下载附件,以及发送、回复、转发、标记已读/未读、移动和删除邮件。写和删除类操作执行前需与用户确认;凭据由 OOMOL 服务端注入。需预先安装并登录 oo CLI 且已连接 QQ 邮箱。

oomol
oomol
热度 46.86
最近更新 2026-09-20 11:30:27
分类:协作依赖:代码执行 / 第三方 API / 读写文件应用场景:邮件起草 / 工作流

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add oo-qq-mail
Metadata
name
oo-qq-mail
description
QQ Mail (mail.qq.com). Use this skill for ANY QQ Mail request — reading, creating, updating, and deleting data. Whenever a task involves QQ Mail, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"QQ Mail","author":"OOMOL","version":"1.0.3","services":["qq_mail"],"icon":"https://static.oomol.com/logo/third-party/qq_mail.png"}

QQ Mail

Operate QQ Mail through your OOMOL-connected account. This skill calls the qq_mail connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected QQ Mail. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "qq_mail" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "qq_mail" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • delete_email — Delete one QQ Mail message from a folder. [destructive]
  • download_attachment — Download one QQ Mail attachment by IMAP body part identifier.
  • forward_email — Forward one QQ Mail email using SMTP with quoted original content. [write]
  • get_email — Fetch and parse one QQ Mail message without marking it as read.
  • get_folder_status — Get lightweight message counters for one QQ Mail folder.
  • list_folders — List folders visible to the connected QQ Mail account.
  • mark_email_read — Mark one QQ Mail message as read. [write]
  • mark_email_unread — Mark one QQ Mail message as unread. [write]
  • move_email — Move one QQ Mail message to another folder. [destructive]
  • reply_email — Reply to one QQ Mail email using SMTP reply headers and quoted content. [write]
  • search_emails — Search one QQ Mail folder and return lightweight email summaries.
  • send_email — Send an email through QQ Mail SMTP. [write]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change QQ Mail state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
    
    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
    
  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login
    
  • scope_missing / credential_expired / app_not_ready / app_not_found — QQ Mail is not connected, or the connection expired or lacks a scope. Connect once (auth type: custom credential) at:

    https://console.oomol.com/app-connections?provider=qq_mail
    
  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources