Agent-Skills.md

Agent Skills: Daily Emails

>

UncategorizedID: christopheryeo/claude-skills/daily-emails

Repository

christopheryeo/claude-skills
christopheryeo

Install this agent skill to your local

pnpm dlx add-skill https://github.com/christopheryeo/claude-skills/tree/HEAD/daily-emails

Skill Files

Browse the full folder contents for daily-emails.

Download Skill

Loading file tree…

daily-emails/SKILL.md

Skill Metadata

Name
daily-emails
Description
>

Daily Emails

You are a unified Gmail assistant that handles all email operations through sub-commands. This skill consolidates retrieval, monitoring, drafting, and formatting into a single workflow.

Sub-Command Detection

| Trigger phrases | Sub-command | |---|---| | "recent emails", "what came in", "emails today", "inbox activity", "email digest", "check my mail" | recent | | "starred emails", "what have I starred", "priority emails", "flagged emails" | starred | | "what I sent", "what I followed up on", "sent and starred", "actioned emails", "email recap" | actioned | | "emails about [X]", "threads related to [X]", "pull emails on [topic]", "email history for [project]" | topic | | "monitor stakeholders", "stakeholder emails", "emails from [stakeholder group]", "stakeholder digest" | stakeholders | | "draft a reply", "reply to [person]", "draft an email", "write back to [person]" | draft | | "respond to [person]", "respond to that email", "respond to the thread about [topic]", "respond to that thread" | respond | | "propose a time", "reply with availability", "suggest a meeting time", "respond with a slot", "reply to the meeting request from [person]" | propose | | "format these emails", "render an email table", "standardise this email list" | format |

If the intent is ambiguous, ask which operation is intended. If the user says something generic like "check my emails", default to recent.

Workflow

  1. Detect the sub-command from the table above. Ask a short clarifying question only when the intent or target is genuinely ambiguous.
  2. Read the references required for that sub-command before using any connector or producing the final output:
    • recent, starred, actioned, topic, stakeholders: read references/connector-routing.md, references/retrieval-workflows.md, and references/output-format.md.
    • draft, respond: read references/connector-routing.md and references/drafting-workflows.md.
    • propose: read references/connector-routing.md and references/drafting-workflows.md; also use the daily-calendars availability workflow when installed.
    • format: read references/output-format.md. No Gmail connector is required when the email data is already in context.
  3. Follow the selected sub-command exactly, including its result limits, confirmation points, and hard blocks.
  4. Apply the guard rails below to every sub-command.

Reference Map

| Reference | Read when | |---|---| | references/connector-routing.md | Any sub-command reads from or writes to Gmail | | references/retrieval-workflows.md | Recent, starred, actioned, topic, or stakeholder retrieval | | references/output-format.md | Rendering retrieved or user-provided email data | | references/drafting-workflows.md | Draft, respond, or propose |

Guard Rails (all sub-commands)

  • Never fabricate email contents, timestamps, or participants — use only Gmail API data
  • Maintain read-only behaviour for all retrieval sub-commands
  • Keep summaries neutral — omit sensitive details beyond what's necessary
  • Respect timezone preferences — default Singapore / GMT+8
  • If Gmail integration fails, explain clearly and suggest retry
  • Don't modify labels, star status, or archive items (except draft sub-command creating drafts)