/ 디렉터리 / 플레이그라운드 / claude-email
● 커뮤니티 AgriciDaniel ⚡ 바로 사용

claude-email

제작: AgriciDaniel · AgriciDaniel/claude-email

6 sub-skills for professional email: inbox triage, composition with PAS/AIDA frameworks, quality scoring, deliverability audit (SPF/DKIM/DMARC), automation sequences, 90-day strategy.

Professional email workflow skill pack. Inbox Triage uses Gmail/Outlook MCP for AI importance scoring + reply suggestions. Composition applies copywriting frameworks (PAS, AIDA, BAB, FAB, 4Ps) with tone matching. Quality Review scores 0-100 across clarity, professionalism, CTA, tone, technical. Deliverability Audit checks SPF/DKIM/DMARC + 2024-2026 bulk-sender compliance. Automation Sequences designs welcome/nurture/re-engagement/post-purchase drips. Marketing Strategy builds 90-day roadmaps + KPIs.

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

claude-email-skill.replay ▶ 준비됨
0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "claude-email-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/AgriciDaniel/claude-email",
        "~/.claude/skills/claude-email"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "claude-email-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/AgriciDaniel/claude-email",
        "~/.claude/skills/claude-email"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "claude-email-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/AgriciDaniel/claude-email",
        "~/.claude/skills/claude-email"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "claude-email-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/AgriciDaniel/claude-email",
        "~/.claude/skills/claude-email"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "claude-email-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/AgriciDaniel/claude-email",
        "~/.claude/skills/claude-email"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json
{
  "context_servers": {
    "claude-email-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/AgriciDaniel/claude-email",
          "~/.claude/skills/claude-email"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add claude-email-skill -- git clone https://github.com/AgriciDaniel/claude-email ~/.claude/skills/claude-email

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: claude-email

Triage a busy inbox in 10 minutes

👤 Anyone drowning in email ⏱ ~10 min beginner

언제 쓸까: Morning inbox review.

사전 조건
  • Gmail or Outlook MCP installed — Set up the appropriate MCP server
  • Skill installed — git clone https://github.com/AgriciDaniel/claude-email ~/.claude/skills/claude-email
흐름
  1. Run triage
    Use claude-email inbox-triage on my unread Gmail from the last 24h. Score + label + draft replies for the top 5.✓ 복사됨
    → Importance-sorted list with draft replies
  2. Review and send
    I'll edit drafts; you archive the noise.✓ 복사됨
    → Inbox down to zero unreads without missing important threads

결과: Inbox zero before coffee.

함정
  • Over-trusting AI-scored importance — Always glance at the 'noise' pile before archiving

Write a cold email using PAS + measured CTA

👤 Founders, sales reps ⏱ ~20 min beginner

언제 쓸까: Cold outreach with a clear offer.

흐름
  1. Brief the composer
    Use claude-email compose. Framework: PAS. Recipient profile: VP of Eng at a mid-size SaaS. Offer: free migration audit.✓ 복사됨
    → Draft with Problem-Agitation-Solution structure
  2. Run quality review
    Score this draft 0-100.✓ 복사됨
    → Scorecard with concrete improvements

결과: A cold email you'd actually send.

Run a deliverability audit before launching a newsletter

👤 Anyone launching email at scale ⏱ ~45 min intermediate

언제 쓸까: Before hitting send on your first 5k-person send.

흐름
  1. Run audit
    Audit example.com — SPF, DKIM, DMARC, reverse DNS. Check Google/Yahoo/Microsoft 2024-2026 bulk sender compliance.✓ 복사됨
    → Per-check pass/fail with fix instructions
  2. Fix and re-audit
    I've updated DNS. Re-audit.✓ 복사됨
    → Green across the board

결과: Send with confidence you'll land in inbox, not spam.

함정
  • DMARC at p=reject without monitoring first — Start at p=none and monitor for 2 weeks

Design a 5-email welcome sequence for a SaaS trial

👤 Growth marketers ⏱ ~60 min intermediate

언제 쓸까: Launching a new product trial and need activation emails.

흐름
  1. Specify the product + goal
    Design a 5-email welcome series for <product>. Goal: trial -> paid activation.✓ 복사됨
    → Series with timing + content brief per email
  2. Draft email 1
    Draft email 1. Tone: warm but punchy.✓ 복사됨
    → Ready-to-paste draft

결과: Automation-ready series.

함께 쓰기: clawfu-skill

조합

다른 MCP와 조합해 10배 효율

claude-email-skill + clawfu-skill

Marketing strategy from ClawFu, email execution here

Take the ClawFu positioning; build a welcome series with claude-email.✓ 복사됨

Actually fetch/send via Gmail auth

Authenticate Gmail, then run inbox_triage.✓ 복사됨

도구

이 MCP가 노출하는 것

도구입력언제 호출비용
inbox_triage filter (time/unread) Inbox review Gmail/Outlook MCP quota
compose framework, recipient profile, offer New outbound 0
quality_review email draft Before sending anything important 0
deliverability_audit sending domain Before scale sends 0
sequence_designer product, goal, audience Automation planning 0
strategy_90d business profile Quarterly planning 0

비용 및 제한

운영 비용

API 쿼터
Depends on Gmail/Outlook MCP + optional SendGrid/Mailchimp
호출당 토큰
Moderate
금액
Free skill
Triage the top 20 unread, not the whole inbox — more signal per token

보안

권한, 시크릿, 파급범위

최소 스코프: Gmail/Outlook: read for triage; send only if you trust the flow
자격 증명 저장: OAuth via Gmail/Outlook MCP; don't store raw credentials
데이터 외부 송신: Email contents go through your LLM provider — check data policy
절대 부여 금지: Send without review for cold outreach — always human-in-the-loop first

문제 해결

자주 발생하는 오류와 해결

Gmail MCP auth expired

Re-run the authenticate flow

Deliverability audit shows DKIM pass but DMARC fail

Alignment mismatch between SPF and DKIM domains — check From vs Return-Path

대안

claude-email 다른 것과 비교

대안언제 쓰나단점/장점
clawfu-skillsYou need broader marketing frameworks, not email-specificLess email execution depth

더 보기

리소스

📖 GitHub에서 공식 README 읽기

🐙 열린 이슈 보기

🔍 400+ MCP 서버 및 Skills 전체 보기