Skill: Gmail Auto-Reply for Client\r

\r

Purpose\r

\r This skill enables the agent to automatically answer Gmail messages on behalf of a client. The agent drafts and (when the user approves or when configured) sends replies using the client’s tone, sign-off, and optional templates.\r \r

When to Use\r

\r

• The user asks to “reply to my emails,” “answer my Gmail,” or “draft responses to incoming mail.”\r
• The user provides a Gmail context (e.g. “inbox for [email protected]”) and wants automated or semi-automated replies.\r
• The user wants the agent to act as the client when responding to specific threads or senders.\r \r

Prerequisites (User/Client Must Provide)\r

\r

• Gmail access: OAuth2 or app password for the client’s Gmail (never store raw passwords in the skill; use environment variables or secure config).\r
• Client profile (optional but recommended): short brief (tone, sign-off, topics they handle, topics to defer).\r \r

Instructions\r

\r

1. Gather context\r
   • Ask for or read the client’s brief: tone (formal/casual), sign-off (e.g. “Best,” “Thanks,”), and any “do not answer” or “always escalate” rules.\r
   • If the user provides an email thread or summary, use that as the incoming message to answer.\r \r
2. Draft the reply\r
   • Write a concise, professional reply that:\r
     • Addresses the sender and the main question or request.\r
     • Matches the client’s tone and sign-off.\r
     • Does not promise anything outside the client’s scope (e.g. legal/financial) unless the user explicitly approves.\r
   • Prefer short paragraphs and clear next steps (e.g. “I’ll get back to you by Friday”).\r \r
3. Use templates when provided\r
   • If the client has added templates (see templates/reply_templates.json or user-defined templates), pick the closest match by intent (e.g. “acknowledgment,” “meeting request,” “out of office”) and personalize placeholders like {{sender_name}}, {{topic}}, {{deadline}}.\r \r
4. Safety and approval\r
   • By default, output the draft for the user/client to approve before sending.\r
   • Only auto-send if the user has clearly configured “auto-send” and you have applied the client’s rules and filters (e.g. only for certain labels or senders).\r \r
5. Integrations\r
   • If the user has configured Gmail API (OAuth2) or IMAP/SMTP, use the credentials from environment or secure config—never from this skill’s files.\r
   • When “sending,” either return the draft text for the user to paste/send, or call the configured send function if the user has set one up.\r \r

Files in This Package\r

\r

• SKILL.md – This file (skill instructions).\r
• manifest.json – Package metadata.\r
• templates/reply_templates.json – Optional starter templates (acknowledgment, meeting, short reply).\r
• scripts/README.md – Short note on how the client can add their own scripts or rules.\r \r

Example Interaction\r

\r User: “Reply to this email as my client. Sender: Jane. She’s asking for a meeting next week. Client prefers a short, friendly reply and uses ‘Best’ as sign-off.”\r \r Agent: Uses this skill to draft a short, friendly reply addressing Jane, suggesting a time or asking for availability, and signing “Best,” then returns the draft for the user to approve or send.\r