360 Secure SkillHub
360 安全技能中心

AgentMail (QQ)

该 Skill 借助 oo CLI 调用 agent_qq 连接器，提供列出别名、列出或搜索邮件、读取邮件、发送邮件和把邮件移入回收站的动作，凭证由 OOMOL 服务端注入。写操作与删除操作需先向用户确认载荷与影响；安装、登录与连接仅在命令报错时按一次性指引处理。

oomol
oomol
热度 14.49
最近更新 2026-07-30 00:22:38
分类：协作依赖：代码执行 / 第三方 API应用场景：邮件起草 / 工作流

安装技能

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

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

AgentMail (QQ)

Operate AgentMail (QQ) through your OOMOL-connected account. This skill calls the agent_qq 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 AgentMail (QQ). 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 "agent_qq" --action "<action_name>"

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

oo connector run "agent_qq" --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_message — Move an AgentMail message to trash and automatically complete the provider confirmation flow. [destructive]
  • list_aliases — List the current AgentMail (QQ) user's aliases and account limits.
  • list_messages — List or search messages in an AgentMail alias mailbox.
  • read_message — Read one AgentMail message including its body and attachment metadata.
  • send_message — Send an AgentMail message and automatically complete the provider confirmation flow when required. [write]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change AgentMail (QQ) 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 — AgentMail (QQ) is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=agent_qq

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources