Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Email Agent Cleanexpo Unite Hub

ASecurity

Processes incoming emails for Unite-Hub. Extracts sender data, identifies communication intents, links to CRM contacts, analyzes sentiment, and updates contact records with AI insights.

657 stars
0 votes
0 copies
0 views
Added 9/30/2026
ai-agents

Security Analysis

A100/100

Scanned 9/30/2026

$npx -y skills add majiayu000/claude-skill-registry --skill email-agent-cleanexpo-unite-hub --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Email Agent Cleanexpo Unite Hub?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Email Agent Cleanexpo Unite Hub
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-email-agent-cleanexpo-unite-hub/badge)](https://www.skillsdirectory.com/skills/majiayu000-email-agent-cleanexpo-unite-hub)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: email-agent
description: Processes incoming emails for Unite-Hub. Extracts sender data, identifies communication intents, links to CRM contacts, analyzes sentiment, and updates contact records with AI insights.
---

# Email Agent Skill

## Overview
The Email Agent is responsible for:
1. **Processing unprocessed emails** from a workspace
2. **Extracting sender information** and linking to existing contacts
3. **Analyzing email content** for intents and sentiment
4. **Updating CRM contacts** with interaction data
5. **Creating audit logs** for all actions

## How to Use This Agent

### Trigger
User says: "Process emails for Duncan's workspace" or "Analyze unprocessed emails"

### What the Agent Does

#### 1. Fetch Unprocessed Emails
```
Call: convex query emails.getUnprocessed({
  orgId: "k57akqzf14r07d9q3pbf9kebvn7v7929",
  workspaceId: "kh72b1cng9h88691sx4x7krt2h7v7dehh",
  limit: 50
})
```

Returns array of emails not yet processed (`isProcessed: false`)

#### 2. For Each Email

**Step A: Extract Sender Email**
```
From: "john@techstartup.com"
Extract: sender_email = "john@techstartup.com"
```

**Step B: Link to Contact**
```
Call: convex query contacts.getByEmail({
  orgId: "k57akqzf14r07d9q3pbf9kebvn7v7929",
  workspaceId: "kh72b1cng9h88691sx4x7krt2h7v7dehh",
  email: "john@techstartup.com"
})
```

If exists → `contactId = found_contact._id`
If NOT exists → Create new contact with:
  - email: sender_email
  - name: extracted from email or "Unknown"
  - source: "email"
  - status: "lead"

**Step C: Analyze Email Content**

Extract these intent keywords:
- "interested" / "partnership" / "collaboration" → intent: **inquiry**
- "proposal" / "quote" / "pricing" → intent: **proposal**
- "issue" / "problem" / "help" → intent: **complaint**
- "?" / "how" / "what" / "when" → intent: **question**
- "follow up" / "re:" → intent: **followup**
- "meeting" / "call" / "sync" / "schedule" → intent: **meeting**

Multiple intents can apply to one email.

**Step D: Analyze Sentiment**

Read email tone:
- Positive indicators: "excited", "love", "great", "thank you", "appreciate"
- Negative indicators: "problem", "issue", "concerned", "unhappy", "urgent"
- Neutral: Standard business tone

Classify as: **positive**, **neutral**, or **negative**

**Step E: Generate Summary**

Create 1-2 sentence summary of email intent:
```
Example: "John from TechStartup is inquiring about Q4 marketing services and partnership opportunities."
```

**Step F: Mark as Processed**

Call: convex mutation emails.markProcessed({
  orgId: "k57akqzf14r07d9q3pbf9kebvn7v7929",
  emailId: "email_id_from_step_1",
  contactId: "contact_id_from_step_b",
  intents: ["inquiry", "partnership"],
  sentiment: "positive",
  summary: "John inquiring about Q4 partnership"
})

**Step G: Update Contact**

If this is a NEW interaction, update:
```
Call: convex mutation contacts.updateAiScore({
  orgId: "k57akqzf14r07d9q3pbf9kebvn7v7929",
  contactId: "contact_id",
  score: 75  // Increase score based on engagement
})

Call: convex mutation contacts.addNote({
  orgId: "k57akqzf14r07d9q3pbf9kebvn7v7929",
  contactId: "contact_id",
  note: "Email from John: Inquiring about Q4 partnership. Sentiment: positive. Intents: inquiry, partnership"
})
```

**Step H: Log Audit Event**

Call: convex mutation system.logAudit({
  orgId: "k57akqzf14r07d9q3pbf9kebvn7v7929",
  action: "email_processed",
  resource: "email",
  resourceId: "email_id",
  agent: "email-agent",
  details: JSON.stringify({
    from: "john@techstartup.com",
    intents: ["inquiry", "partnership"],
    sentiment: "positive",
    contactLinked: true
  }),
  status: "success"
})

### Error Handling

If something fails:
```
Call: convex mutation system.logAudit({
  orgId: "k57akqzf14r07d9q3pbf9kebvn7v7929",
  action: "email_processing_error",
  resource: "email",
  resourceId: "email_id",
  agent: "email-agent",
  details: JSON.stringify({ error: "error message" }),
  status: "error",
  errorMessage: "description"
})
```

Then continue to next email (don't stop).

## Summary Output

After processing all emails, provide:
```
✅ Email Processing Complete

Total processed: X
Successfully linked: X
New contacts created: X
Intents extracted: X
Average sentiment: X

Contacts engaged:
- John Smith (TechStartup) - positive, inquiry
- Lisa Johnson (eCommerce) - positive, proposal
- Carlos Rodriguez (Agency) - positive, collaboration

Next steps:
1. Review high-priority contacts (positive sentiment + inquiry)
2. Generate followup emails for warm leads
3. Schedule meetings with decision-makers
```

## Key Points

- **Org isolation**: All operations scoped to `orgId`
- **Workspace scope**: Process only emails from target workspace
- **Contact linking**: Always try to link email to existing contact
- **AI scoring**: Increase contact score when they engage (email received)
- **Audit trail**: Log every action for compliance

---

## Example: Processing One Email

**Input Email:**
```
From: john@techstartup.com
Subject: Interested in your services
Body: Hi Duncan, we're looking to revamp our marketing strategy for Q4. Would love to chat about partnership opportunities.
```

**Agent Process:**

1. ✅ Extract sender: `john@techstartup.com`
2. ✅ Query contact: Found "John Smith" in contacts
3. ✅ Extract intents: `["inquiry", "partnership"]`
4. ✅ Analyze sentiment: `"positive"` (enthusiastic tone)
5. ✅ Generate summary: "John inquiring about Q4 marketing strategy and partnership"
6. ✅ Mark email processed with contact link
7. ✅ Increase contact AI score from 68 → 78
8. ✅ Add note with timestamp and details
9. ✅ Log audit event with full context

**Result:**
- Contact updated with fresh interaction data
- Audit trail shows agent processed email
- Contact now appears in "high-value prospects" due to increased score

Attribution

majiayu000majiayu000
View sourceSee grades on GitHubMore from majiayu000 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →