Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

gmail-sender

Étoiles4

Forks0

Mis à jour25 février 2026 à 18:18

Send approved emails via Gmail API. Use after a human has approved an APPROVAL_SEND_EMAIL_*.md file by moving it to vault/Approved/. Reads the payload, sends the email, logs the result, and moves the approval file to vault/Done/. Never send without an approved file present.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

metachemist

metachemist/Full-Time-Employee

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	gmail-sender
description	Send approved emails via Gmail API. Use after a human has approved an APPROVAL_SEND_EMAIL_*.md file by moving it to vault/Approved/. Reads the payload, sends the email, logs the result, and moves the approval file to vault/Done/. Never send without an approved file present.

Gmail Sender

Execute email sends after human approval using the Gmail API.

When to Use

Only call this skill when:

A file starting with APPROVAL_SEND_EMAIL_ exists in vault/Approved/
Its status frontmatter field is pending

Never send without an approved file. Never send to new contacts without checking Company_Handbook.md first.

Prerequisites

Item	Location
OAuth token	`watchers/.state/gmail_token.json`
Credentials	`watchers/.secrets/gmail_credentials.json`
Python deps	`pip install google-auth google-auth-oauthlib google-api-python-client`

If gmail_token.json is missing or expired, run the Gmail watcher once to re-authorise:

cd watchers && python gmail_watcher.py ../vault --auth-only

Workflow

1. Read the Approved File

# Find approved email actions
ls vault/Approved/APPROVAL_SEND_EMAIL_*.md

Parse the file:

---
type: approval_request
action: send_email
source_plan: Plans/PLAN_GMAIL_...md
created: ...
status: pending          # must be "pending" — if "sent" skip it
---

# Payload
- **Action:** `send_email`
- **Target:** Jane Doe <jane@example.com>
- **Subject / Title:** Re: Pricing inquiry

## Message / Content
  Dear Jane,
  ... (the email body to send)

Extract:

To: from Target: line — Jane Doe <jane@example.com>
Subject: from Subject / Title: line
Body: everything under ## Message / Content, strip the 2-space indent

2. Send the Email

python .claude/skills/gmail-sender/scripts/send_email.py \
  --to "Jane Doe <jane@example.com>" \
  --subject "Re: Pricing inquiry" \
  --body-file /tmp/email_body.txt \
  --token watchers/.state/gmail_token.json \
  --credentials watchers/.secrets/gmail_credentials.json

Or pass body inline for short messages:

python .claude/skills/gmail-sender/scripts/send_email.py \
  --to "Jane Doe <jane@example.com>" \
  --subject "Re: Pricing" \
  --body "Dear Jane, Thank you for..."

Expected output (JSON):

{"status": "sent", "message_id": "18e4bc...", "to": "jane@example.com", "timestamp": "2026-02-22T..."}

On error:

{"status": "error", "error": "Invalid credentials", "timestamp": "..."}

3. Update the Vault

After a successful send:

Update the approval file — set status: sent and add sent_at: <ISO timestamp>
Move approval file → vault/Done/<filename>
Update source plan → set status: done (find via source_plan frontmatter field)
Write audit log entry to vault/Logs/YYYY-MM-DD.jsonl:

{"timestamp": "...", "event": "email_sent", "to": "jane@example.com", "subject": "Re: Pricing", "message_id": "18e4bc...", "result": "success"}

Update Dashboard.md counts

4. Error Handling

Error	Action
`Invalid credentials`	Run auth flow, alert user, do not send
`Quota exceeded`	Wait 60 s, retry once, then alert
`Invalid recipient`	Write `status: failed` to approval file, move to `vault/Done/`
`Network error`	Retry up to 3×, exponential backoff

Never leave a failed send in vault/Approved/ — always move it to vault/Done/ with status: failed and the error message noted.

Dry-Run Mode

Test without sending a real email:

python .claude/skills/gmail-sender/scripts/send_email.py \
  --to "test@example.com" --subject "Test" --body "Hello" --dry-run

Output: {"status": "dry_run", "would_send_to": "test@example.com", ...}

Quick Reference

# Check for approved emails
ls vault/Approved/APPROVAL_SEND_EMAIL_*.md

# Send and update vault
python .claude/skills/gmail-sender/scripts/send_email.py \
  --to "<recipient>" --subject "<subject>" --body "<body>"

# Verify sent (check Gmail Sent folder)
python .claude/skills/gmail-sender/scripts/send_email.py --list-sent --limit 5

Rules (non-negotiable)

Never send without a file in vault/Approved/
Never send to a contact not in the approved file's Target field
Always log every send attempt (success or failure) to vault/Logs/
Always move the approval file to vault/Done/ after execution
Rate limit: max 20 emails per hour; pause and alert if limit reached

Plus depuis ce dépôt

même dépôt

approval-executor

metachemist/Full-Time-Employee

Process approved actions from vault/Approved/ and execute them. Reads each APPROVAL_*.md file, identifies the action type (send_email, send_linkedin_post), dispatches to the correct sender skill, logs the result, and moves files to vault/Done/. Use when the user has moved approval files to /Approved and wants them executed, or when running as part of the autonomous action loop.

2026-03-124

facebook-poster

metachemist/Full-Time-Employee

Create and publish text posts to a Facebook Page using the official Graph API. Use when asked to post on Facebook, or when processing an approved APPROVAL_SEND_FACEBOOK_POST_*.md file from vault/Approved/. Always draft first and require human approval before posting.

2026-03-114

instagram-poster

metachemist/Full-Time-Employee

Create and publish photo posts with captions to Instagram using the official Content Publishing API (no browser required). Use when asked to post on Instagram, or when processing an approved APPROVAL_SEND_INSTAGRAM_POST_*.md file from vault/Approved/. Always draft first and require human approval before posting. NOTE: Instagram requires a publicly accessible HTTPS image URL — local file paths are not supported by the API.

2026-03-114

linkedin-poster

metachemist/Full-Time-Employee

Create and publish LinkedIn posts for business/sales content using the official LinkedIn UGC Posts API. Use when asked to post on LinkedIn, schedule a sales post, or process an approved LinkedIn post action from vault/Approved/. Always draft first and require human approval before posting.

2026-03-114

odoo-crm

metachemist/Full-Time-Employee

Integrate with self-hosted Odoo Community via JSON-RPC API. Use for CRM operations (create leads, log activities, search contacts) and accounting draft actions (create draft invoices — never post without human approval). Use when processing LinkedIn connections, approved CRM actions, or when running the weekly accounting audit. Requires ODOO_URL, ODOO_DB, ODOO_USERNAME, ODOO_PASSWORD in .env.

2026-03-114

twitter-poster

metachemist/Full-Time-Employee

Create and publish posts (tweets) to Twitter/X using the official X API v2 (OAuth 1.0a — no browser required). Use when asked to post on X/Twitter, or when processing an approved APPROVAL_SEND_TWITTER_POST_*.md file from vault/Approved/. Always draft first and require human approval before posting.

2026-03-114

name	gmail-sender
description	Send approved emails via Gmail API. Use after a human has approved an APPROVAL_SEND_EMAIL_*.md file by moving it to vault/Approved/. Reads the payload, sends the email, logs the result, and moves the approval file to vault/Done/. Never send without an approved file present.

Gmail Sender

Execute email sends after human approval using the Gmail API.

When to Use

Only call this skill when:

A file starting with APPROVAL_SEND_EMAIL_ exists in vault/Approved/
Its status frontmatter field is pending

Never send without an approved file. Never send to new contacts without checking Company_Handbook.md first.

Prerequisites

Item	Location
OAuth token	`watchers/.state/gmail_token.json`
Credentials	`watchers/.secrets/gmail_credentials.json`
Python deps	`pip install google-auth google-auth-oauthlib google-api-python-client`

If gmail_token.json is missing or expired, run the Gmail watcher once to re-authorise:

cd watchers && python gmail_watcher.py ../vault --auth-only

Workflow

1. Read the Approved File

# Find approved email actions
ls vault/Approved/APPROVAL_SEND_EMAIL_*.md

Parse the file:

---
type: approval_request
action: send_email
source_plan: Plans/PLAN_GMAIL_...md
created: ...
status: pending          # must be "pending" — if "sent" skip it
---

# Payload
- **Action:** `send_email`
- **Target:** Jane Doe <jane@example.com>
- **Subject / Title:** Re: Pricing inquiry

## Message / Content
  Dear Jane,
  ... (the email body to send)

Extract:

To: from Target: line — Jane Doe <jane@example.com>
Subject: from Subject / Title: line
Body: everything under ## Message / Content, strip the 2-space indent

2. Send the Email

python .claude/skills/gmail-sender/scripts/send_email.py \
  --to "Jane Doe <jane@example.com>" \
  --subject "Re: Pricing inquiry" \
  --body-file /tmp/email_body.txt \
  --token watchers/.state/gmail_token.json \
  --credentials watchers/.secrets/gmail_credentials.json

Or pass body inline for short messages:

python .claude/skills/gmail-sender/scripts/send_email.py \
  --to "Jane Doe <jane@example.com>" \
  --subject "Re: Pricing" \
  --body "Dear Jane, Thank you for..."

Expected output (JSON):

{"status": "sent", "message_id": "18e4bc...", "to": "jane@example.com", "timestamp": "2026-02-22T..."}

On error:

{"status": "error", "error": "Invalid credentials", "timestamp": "..."}

3. Update the Vault

After a successful send:

Update the approval file — set status: sent and add sent_at: <ISO timestamp>
Move approval file → vault/Done/<filename>
Update source plan → set status: done (find via source_plan frontmatter field)
Write audit log entry to vault/Logs/YYYY-MM-DD.jsonl:

{"timestamp": "...", "event": "email_sent", "to": "jane@example.com", "subject": "Re: Pricing", "message_id": "18e4bc...", "result": "success"}

Update Dashboard.md counts

4. Error Handling

Error	Action
`Invalid credentials`	Run auth flow, alert user, do not send
`Quota exceeded`	Wait 60 s, retry once, then alert
`Invalid recipient`	Write `status: failed` to approval file, move to `vault/Done/`
`Network error`	Retry up to 3×, exponential backoff

Never leave a failed send in vault/Approved/ — always move it to vault/Done/ with status: failed and the error message noted.

Dry-Run Mode

Test without sending a real email:

python .claude/skills/gmail-sender/scripts/send_email.py \
  --to "test@example.com" --subject "Test" --body "Hello" --dry-run

Output: {"status": "dry_run", "would_send_to": "test@example.com", ...}

Quick Reference

# Check for approved emails
ls vault/Approved/APPROVAL_SEND_EMAIL_*.md

# Send and update vault
python .claude/skills/gmail-sender/scripts/send_email.py \
  --to "<recipient>" --subject "<subject>" --body "<body>"

# Verify sent (check Gmail Sent folder)
python .claude/skills/gmail-sender/scripts/send_email.py --list-sent --limit 5

Rules (non-negotiable)

Never send without a file in vault/Approved/
Never send to a contact not in the approved file's Target field
Always log every send attempt (success or failure) to vault/Logs/
Always move the approval file to vault/Done/ after execution
Rate limit: max 20 emails per hour; pause and alert if limit reached