skills/clementwalter/email-assistant/SKILL.md
User asks to read, check, or manage emails - User asks to reply to or send an email - User asks to draft an email response
npx skillsauth add aiskillstore/marketplace email-assistantInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Guidelines for reading and writing emails via Gmail MCP tools.
Keep email drafts short and to the point. Avoid:
Always reply in the same language as the original email.
Never send an email without user approval.
Workflow:
1. Use list_emails to show recent emails
2. Use read_email to get full content when user selects one
3. Summarize key points if email is long
1. Read the original email
2. Identify the language
3. Draft a succinct reply in the same language
4. Present the draft:
---
**To:** [email protected]
**Subject:** RE: Original Subject
**Attachment:** file.pdf (if any)
> Draft content here
---
5. Ask: "Should I send this?"
6. Wait for confirmation
7. Use reply_email tool only after approval
1. Gather: recipient, subject, content
2. Draft the email
3. Present for validation
4. Send only after explicit approval
Always present drafts in this format:
**To:** [email protected]
**Subject:** Subject line
**Attachment:** filename.pdf (if applicable)
---
[Email body here]
---
Ready to send?
Bonjour,
Veuillez trouver ci-joint le document demandé.
Cordialement,
[Name]
Bonjour Monsieur,
J'espère que vous allez bien et que vous passez une excellente journée.
Je me permets de vous écrire pour vous transmettre le document que vous
m'avez demandé lors de notre dernier échange. Vous trouverez ci-joint
le fichier en question. N'hésitez pas à me contacter si vous avez des
questions ou si vous avez besoin d'informations supplémentaires.
Je vous souhaite une excellente fin de journée et reste à votre
entière disposition.
Bien cordialement,
[Name]
| Tool | Use For |
| --------------- | ---------------------------------- |
| list_emails | Browse inbox |
| read_email | Get full email content |
| search_emails | Find specific emails |
| reply_email | Reply in thread (with attachments) |
| send_email | New email (with attachments) |
Use the 1Password item name for the account parameter:
"Gmail Zama Claude" - Work account"Gmail Personal Claude" - Personal accountAsk user which account if unclear.
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.