SlopScore
00 crowd

claude-email-assistant

An autonomous email triage and reply system built with Claude Code and Google Workspace CLI (gws).
Open repo on GitHub Open the demogithub.com/marian-kamenistak/claude-email-assistant
Shell · ★ 2 · 0 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other🤖 claude-code
listed 2 hours ago by marian-kamenistak · last checked 2 hours ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-09-14: An autonomous email triage and reply system built with Claude Code and Google Workspace CLI (gws).; its own README says "An autonomous email triage and reply system built with Claude Code and Google Workspace CLI (gws)". 2 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as marian-kamenistak. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
An autonomous email triage and reply system built with Claude Code and Google Workspace CLI (gws).
website
https://www.marian.coach/
topics
aiai-toolsclaude-skillsemail-replyskills
created
2026-03-14 · pushed 2 weeks ago · 13 commits · 1 contributor
languages
Shell 80%HTML 20%
paperwork
licensereadme 42% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 2 hours ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
built_with
claude-code
language (detected)
htmlshell
topic (detected)
aiai-toolsclaude-skillsemail-replyskills
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: An autonomous email triage and reply system built with Claude Code and Google Workspace CLI (gws).; its own README says "An autonomous email triage and reply system built with Claude Code and Google Workspace CLI (gws)". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

Claude Code Email Assistant

An autonomous email triage and reply system built with Claude Code and Google Workspace CLI (gws).

Email triage screenshot

Every workday at 8:30, Claude Code reads your inbox, drafts replies in your voice, saves them as Gmail drafts, and blocks time in your calendar. You wake up, open Gmail, review the drafts, and hit Send.

The system learns from every edit you make. If you change a draft before sending, next morning it compares what it wrote vs what you actually sent — and adjusts.

How it works

8:30  launchd triggers Claude Code
        │
        ▼
┌─────────────────┐
│ 1. Triage inbox │  Classify emails: reply / info / ops
│ 2. Learn        │  Compare yesterday's drafts vs what was sent
│ 3. Draft        │  Write replies in your voice, save as Gmail Drafts
│ 4. Label        │  Tag emails: AI ready / info / ops / high / $
│ 5. Summarize    │  Estimate time per email
│ 6. Calendar     │  Block time based on actual workload
└─────────────────┘
        │
        ▼
┌─────────────────┐
│ You open Gmail   │  Drafts are there, in the right threads
│ ✓ Send as-is    │  Most drafts just need one click
│ ✎ Edit + Send   │  Fix anything directly in Gmail
│ ✗ Delete        │  Skip what doesn't need a reply
└─────────────────┘
        │
        ▼
┌─────────────────┐
│ Next morning     │  System diffs drafts vs sent messages
│ Learns from edits│  Every correction improves future drafts
└─────────────────┘

What you get

  • Gmail Drafts — replies appear in the right threads, ready to send
  • Gmail Labels — emails auto-categorized: AI ready, info, ops, high, $
  • Calendar block — dynamic time block based on actual email volume
  • Self-improving — learns your voice from corrections, not just from examples
  • Time estimates — know exactly how long your email block will take

Prerequisites

  • macOS (uses launchd for scheduling)
  • Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
  • gws CLI — Google Workspace CLI with Gmail and Calendar access
  • iTerm2 (optional, for the interactive terminal with distinct styling)
  • A Google Workspace account with Gmail API and Calendar API enabled

Installation

See INSTALL.md for the full setup guide.

Quick start

# 1. Clone this repo
git clone https://github.com/marian-kamenistak/claude-email-assistant.git
cd claude-email-assistant

# 2. Run the setup script
./setup.sh

# 3. Test it
./scripts/morning-triage.sh

Project structure

claude-email-assistant/
├── .claude-plugin/
│   └── plugin.json                    # Plugin manifest for marketplace
├── CLAUDE.md                          # Claude Code project instructions
├── INSTALL.md                         # Full installation guide
├── LICENSE                            # MIT license
├── setup.sh                           # Interactive setup script
├── screenshot-triage.png              # Triage output screenshot
├── scripts/
│   └── morning-triage.sh             # The scheduler script (launched by launchd)
├── launchd/
│   └── com.claude.morning-triage.plist  # macOS scheduler config
├── skills/
│   └── reply-email/
│       ├── SKILL.md                   # Reply drafting skill definition
│       ├── email-voice-guide.md       # Your email voice examples (you fill this in)
│       ├── learned-replies.md         # Auto-populated from corrections
│       └── drafts-log.md             # Draft tracking for the learning loop
└── shared/
    └── communication-style.md         # Your writing style rules

The learning loop

This is the key differentiator. Most AI email tools are fire-and-forget. This one learns.

  1. Morning: Claude drafts replies based on your voice guide + past corrections
  2. You: Review in Gmail. Send as-is, edit and send, or delete
  3. Next morning: Claude compares what it drafted vs what you actually sent
  4. Result: Every word you change, every sentence you shorten, every draft you delete teaches it something

After ~30 corrections, the drafts start sounding like you actually wrote them.

Gmail labels

The system uses labels to track email state:

Label Meaning
AI ready Draft created, waiting for you to review and send
info No reply needed (newsletters, notifications, FYIs)
ops Needs operational work (download invoice, sign doc, update system)
high Urgent / time-sensitive
$ Invoice or billing context

Calendar integration

Each morning, the system creates a calendar event with:

  • Dynamic duration: minimum 15 min, expands based on actual email volume
  • Summary in description: full breakdown of what needs attention
  • Time estimates: per-email estimates so you know exactly what you're walking into

Customization

Your voice

Edit skills/reply-email/email-voice-guide.md with 10-20 real emails you've sent. The more examples, the better the voice match. Include:

  • Quick confirmations (1-liners)
  • Scheduling emails (dates + calendar link)
  • Client replies (proposals, follow-ups)
  • Casual emails (networking, community)

Your style rules

Edit shared/communication-style.md with your writing rules:

  • Words you never use
  • How you sign off
  • Your tone by context (casual vs professional)
  • Anti-patterns to avoid

Schedule

Edit the launchd plist to change when the triage runs. Default is weekdays at 8:30.

Security note

The morning triage script uses --dangerously-skip-permissions because it runs unattended via launchd. This flag allows Claude Code to execute tools without interactive approval prompts. Review the prompt in scripts/morning-triage.sh to understand exactly what it does autonomously.

Limitations

  • macOS only (launchd). Linux users can adapt to cron/systemd.
  • Requires gws CLI with Google Workspace API access.
  • The learning loop needs ~1 week of corrections to start producing good drafts.
  • Claude Code CLI subscription required.
  • Calendar integration requires a Google Calendar you own (not just read access).

License

MIT

Read the rest on GitHub

Scan report · 2026-09-14
  • Prohibited terms or links
  • Repository eligibility
  • slopscore.md paperwork
  • Content policy
  • Risk review

0 comments

log in to comment.

report this listinglog in to report