Agent Skills › QuixiAI/Hexis › gmail-actions

gmail-actions

GitHub

处理 Gmail 邮件发送、回复、标签管理、垃圾邮件分类及删除等通信操作，强调需用户明确授权与安全原则。

skills/installed/gmail-actions/SKILL.md QuixiAI/Hexis

Trigger Scenarios

发送电子邮件回复邮件线程对邮件应用或移除标签标记垃圾邮件或非垃圾邮件删除特定邮件

Install

npx skills add QuixiAI/Hexis --skill gmail-actions -g -y

More Options

Non-standard path

npx skills add https://github.com/QuixiAI/Hexis/tree/main/skills/installed/gmail-actions -g -y

Use without installing

npx skills use QuixiAI/Hexis@gmail-actions

指定 Agent (Claude Code)

npx skills add QuixiAI/Hexis --skill gmail-actions -a claude-code -g -y

安装 repo 全部 skill

npx skills add QuixiAI/Hexis --all -g -y

预览 repo 内 skill

npx skills add QuixiAI/Hexis --list

SKILL.md

Frontmatter

{
    "name": "gmail-actions",
    "aliases": [
        "email",
        "emails",
        "mail",
        "inbox",
        "message",
        "reply",
        "send",
        "unread",
        "archive",
        "spam"
    ],
    "category": "communication",
    "contexts": [
        "chat",
        "heartbeat"
    ],
    "requires": {
        "tools": [
            "gmail_send",
            "gmail_reply",
            "gmail_label",
            "gmail_spam_triage",
            "gmail_delete",
            "connector_action_policy_status"
        ]
    },
    "bound_tools": [
        "gmail_send",
        "gmail_reply",
        "gmail_label",
        "gmail_spam_triage",
        "gmail_delete",
        "connector_action_policy_status"
    ],
    "description": "Send Gmail messages, reply to threads, apply labels, triage spam, and delete messages with explicit action authorization"
}

Gmail Actions

Use this only after Gmail is connected and the user asks for an outward Gmail action: send, reply, label, mark spam/not-spam, archive, or delete.

Principles

A connected Gmail account is not permission to act. Check or establish connector action policy for ongoing/autonomous behavior.
One-off chat actions still need a clear user request in the current conversation.
Heartbeat actions require a matching DB-owned connector action policy; if none exists, do not improvise.
Keep messages short, literal, and aligned with the user's stated intent. Do not escalate a narrow request into broader correspondence.
Deletion is Trash-only by default and never autonomous. Call gmail_delete only when the user names a specific message in the current conversation; set permanent only after the user explicitly asks for irreversible deletion of that message. Never delete during heartbeats.

Flow

If the user asks for ongoing behavior, use connector-action-authorization first.
For a one-off send, call gmail_send with to, subject, and body.
For a reply, call gmail_reply with thread_id, recipient, subject, and body.
For labels, call gmail_label with explicit add_label_ids and/or remove_label_ids.
For spam triage, call gmail_spam_triage with mark_spam, mark_not_spam, or archive.
For deletion the user explicitly requested, call gmail_delete with the message_id; leave permanent unset (Trash) unless the user asked for irreversible deletion in so many words.