name	gmail-actions
description	Send Gmail messages, reply to threads, apply labels, and triage spam with explicit action authorization
category	communication
requires	{"tools":["gmail_send","gmail_reply","gmail_label","gmail_spam_triage","connector_action_policy_status"]}
contexts	["chat","heartbeat"]
bound_tools	["gmail_send","gmail_reply","gmail_label","gmail_spam_triage","connector_action_policy_status"]

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, or archive.

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.
Do not use destructive deletion; this skill intentionally exposes label/spam/archive actions, not permanent delete.

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.

Más de este repositorio

mismo repositorio

Author or revise reusable Hexis skills from repeated successful workflows

Semantic recall, exact cross-session search, remembering, and normal continuity

Ingest URLs, documents, and text into the memory system as structured knowledge

Inspect, grant, and revoke scoped connector action policies for sends, replies, labels, spam triage, and provider state changes

Digest and ingest emails into memory, surfacing important threads and action items

Connect Gmail through explicit OAuth setup, inspect status, complete authorization, queue read-only backfill, control jobs, and revoke local access

name	gmail-actions
description	Send Gmail messages, reply to threads, apply labels, and triage spam with explicit action authorization
category	communication
requires	{"tools":["gmail_send","gmail_reply","gmail_label","gmail_spam_triage","connector_action_policy_status"]}
contexts	["chat","heartbeat"]
bound_tools	["gmail_send","gmail_reply","gmail_label","gmail_spam_triage","connector_action_policy_status"]

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

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.
Do not use destructive deletion; this skill intentionally exposes label/spam/archive actions, not permanent delete.

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.