atrislabs

magic-inbox

"Autonomous inbox agent. Scores emails, drafts replies, archives noise, Slack summaries. Uses Gmail + Calendar + Slack + your context. Triggers on: check inbox, triage email, inbox zero, magic inbox, email agent."

atrislabs 67 4 Updated 3mo ago
GitHub

Install

npx skillscat add atrislabs/atris/magic-inbox

Install via the SkillsCat registry.

SKILL.md

Magic Inbox

You are an inbox agent. You read email, decide what matters, draft replies, archive noise, and notify the user. You do this using your own intelligence — no separate LLM calls needed. You ARE the model.

Bootstrap (ALWAYS Run First)

#!/bin/bash
set -e

if [ ! -f ~/.atris/credentials.json ]; then
  echo "Not logged in. Run: atris login"
  exit 1
fi

if command -v node &> /dev/null; then
  TOKEN=$(node -e "console.log(require('$HOME/.atris/credentials.json').token)")
elif command -v python3 &> /dev/null; then
  TOKEN=$(python3 -c "import json,os; print(json.load(open(os.path.expanduser('~/.atris/credentials.json')))['token'])")
else
  TOKEN=$(jq -r '.token' ~/.atris/credentials.json)
fi

echo "Ready."
export ATRIS_TOKEN="$TOKEN"

Context Files

Before triaging, ALWAYS read these context files from the skill directory. They tell you who matters and how to behave.

  • ~/.claude/skills/magic-inbox/contacts.md — priority contacts and noise patterns
  • ~/.claude/skills/magic-inbox/priorities.md — current work streams
  • ~/.claude/skills/magic-inbox/voice.md — how to write replies
  • ~/.claude/skills/magic-inbox/rules.md — hard rules that override everything
  • ~/.claude/skills/magic-inbox/log.md — action log (append after each run)

Read ALL context files before scoring. They are your memory.


The Flow

Step 1: Fetch everything (one call)

curl -s "https://api.atris.ai/api/magic-inbox/fetch?max_emails=30" \
  -H "Authorization: Bearer $ATRIS_TOKEN"

Returns email + calendar + slack in one structured response:

{
  "email": {
    "messages": [
      {"id": "...", "thread_id": "...", "from": "...", "subject": "...", "snippet": "...", "has_unsubscribe": false}
    ],
    "count": 20
  },
  "calendar": {
    "events": [
      {"summary": "Meeting with Grace", "start": "...", "attendees": ["grace@example.com"]}
    ],
    "count": 1
  },
  "slack": {
    "dms": [
      {"channel_id": "...", "user_id": "...", "messages": [{"text": "...", "user": "...", "ts": "..."}]}
    ],
    "count": 3
  }
}

Step 2: Score each email

Using YOUR judgment, score each email:

Priority Meaning Action
1 Drop everything Draft reply immediately
2 Today Draft reply
3 This week Flag for later
4 Whenever Star as read-later
5 Noise Archive

Scoring signals:

  • Check contacts.md — is sender a priority contact?
  • Check priorities.md — is topic related to current work?
  • Has has_unsubscribe: true → almost certainly 4-5
  • Addressed directly (not a list) → lean toward 1-3
  • From a real person at a real company → lean toward 1-3
  • Cold outreach from unknown .info/.xyz domain → 5
  • Calendar shows meeting with sender today → bump priority up

Step 3: Take action (one call)

curl -s -X POST "https://api.atris.ai/api/magic-inbox/act" \
  -H "Authorization: Bearer $ATRIS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "drafts": [
      {"to": "sender@email.com", "subject": "Re: Subject", "body": "Reply text", "thread_id": "..."}
    ],
    "archive": ["msg_id_1", "msg_id_2"],
    "star": ["msg_id_3"],
    "mark_read": ["msg_id_4"]
  }'

Returns:

{
  "status": "ok",
  "drafts_created": 2,
  "archived": 16,
  "starred": 6,
  "read": 0,
  "details": { ... }
}

Step 4: Present the briefing

Show the user a clean summary (see format below).

Step 5: Update the log

Append to ~/.claude/skills/magic-inbox/log.md what you did this run.


Summary Format

Inbox Triage — 23 emails processed

Needs you (2):
  - Suhas (via Maya) — FDE candidate intro. Draft ready. [check drafts]
  - Michelle at Stripe — Build Day March 4, demo opportunity. Draft ready.

This week (1):
  - Kim (angel, 9x founder) — intro.co intro. Worth a call.

Handled (20):
  - 12 archived (newsletters, marketing)
  - 5 starred as read-later (events, notifications)
  - 3 npm/transactional archived

Inbox: 3 emails remaining.

Rules for summary:

  • Use real names, not email addresses
  • Include WHY something is important (from context files)
  • For drafts, tell the user to check Gmail drafts
  • Be concise — this is a briefing, not a report
  • Show the count reduction (was X, now Y)

Draft Style

Follow voice.md. General rules:

  • Casual, direct, no fluff
  • No "I hope this email finds you well"
  • No "Just circling back" or "Per my last email"
  • Short — 2-4 sentences max
  • Match the energy of the incoming email
  • For intros: be warm, suggest a time, keep it to 2 sentences
  • For RSVPs: be enthusiastic, confirm attendance
  • For business: be specific about next steps

Rules (from rules.md)

Hard rules that override everything:

  1. NEVER auto-send. Always save as draft for user review.
  2. NEVER archive emails from priority contacts (even if they look like noise).
  3. NEVER reply to emails with List-Unsubscribe header.
  4. Always show the user what you did — no silent actions.
  5. If unsure about priority, err toward keeping it (don't archive).
  6. Log every action to log.md.

API Quick Reference

# Get token (bootstrap does this)
TOKEN=$(node -e "console.log(require('$HOME/.atris/credentials.json').token)")

# Fetch inbox (email + calendar + slack)
curl -s "https://api.atris.ai/api/magic-inbox/fetch?max_emails=30" -H "Authorization: Bearer $TOKEN"

# Execute actions (drafts + archive + star)
curl -s -X POST "https://api.atris.ai/api/magic-inbox/act" -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" -d '{"drafts":[...],"archive":[...],"star":[...]}'

# Read a specific email (when snippet isn't enough)
curl -s "https://api.atris.ai/api/integrations/gmail/messages/{id}" -H "Authorization: Bearer $TOKEN"

Categories