scbe-email-checker

Check ProtonMail and Gmail for important emails — patent updates, revenue notifications, outreach replies, security alerts. Use when asked to "check email", "check my inbox", "any new emails", "patent email", "check proton", "check gmail", or at session start for a quick email briefing.

6 stars

Best use case

scbe-email-checker is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Check ProtonMail and Gmail for important emails — patent updates, revenue notifications, outreach replies, security alerts. Use when asked to "check email", "check my inbox", "any new emails", "patent email", "check proton", "check gmail", or at session start for a quick email briefing.

Teams using scbe-email-checker should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/scbe-email-checker/SKILL.md --create-dirs "https://raw.githubusercontent.com/issdandavis/SCBE-AETHERMOORE/main/.claude/skills/scbe-email-checker/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/scbe-email-checker/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How scbe-email-checker Compares

Feature / Agentscbe-email-checkerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Check ProtonMail and Gmail for important emails — patent updates, revenue notifications, outreach replies, security alerts. Use when asked to "check email", "check my inbox", "any new emails", "patent email", "check proton", "check gmail", or at session start for a quick email briefing.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# SCBE Email Checker

Check ProtonMail (via Bridge IMAP) and Gmail (via IMAP) for important emails without leaving the terminal.

## When to Use

- User says "check email", "check inbox", "any emails", "check proton", "check gmail"
- Daily patent check (USPTO follow-ups)
- Revenue monitoring (Stripe, Shopify, Gumroad receipts)
- Outreach replies (NIST, CISA, collaborators)
- Security alerts (GitHub, npm, Dependabot)
- Session start briefing

## Accounts

| Account | Protocol | Host | Port | Username |
|---------|----------|------|------|----------|
| ProtonMail | IMAP (Bridge) | 127.0.0.1 | 1143 | issdandavis@proton.me |
| Gmail | IMAP SSL | imap.gmail.com | 993 | issdandavis7795@gmail.com |

Aliases on same ProtonMail account: `aethermoregames@pm.me`, `issdandavis@protonmail.com`

## Credentials

Load from `config/connector_oauth/.env.connector.oauth`:
- `PROTONMAIL_BRIDGE_PASSWORD` — Bridge-generated password (NOT Proton login)
- `PROTONMAIL_USER` — defaults to `issdandavis@proton.me`
- `GMAIL_APP_PASSWORD` — Google App Password (NOT Google login)
- `GMAIL_USER` — defaults to `issdandavis7795@gmail.com`

ProtonMail Bridge must be running locally for IMAP to work.
Gmail requires an App Password (generate at https://myaccount.google.com/apppasswords).

## Workflow

### Step 1: Load credentials

```python
import os
env_path = "config/connector_oauth/.env.connector.oauth"
for line in open(env_path).read().splitlines():
    if line.strip() and not line.startswith("#") and "=" in line:
        k, v = line.split("=", 1)
        os.environ.setdefault(k.strip(), v.strip().strip("\"'"))
```

### Step 2: Connect to ProtonMail via Bridge

```python
import imaplib
mail = imaplib.IMAP4("127.0.0.1", 1143)
mail.login(os.environ["PROTONMAIL_USER"], os.environ["PROTONMAIL_BRIDGE_PASSWORD"])
mail.select("INBOX")
```

### Step 3: Connect to Gmail via IMAP SSL

```python
gmail = imaplib.IMAP4_SSL("imap.gmail.com", 993)
gmail.login(os.environ.get("GMAIL_USER", "issdandavis7795@gmail.com"), os.environ["GMAIL_APP_PASSWORD"])
gmail.select("INBOX")
```

### Step 4: Search for important emails

Priority search terms (run against both accounts):

```python
PRIORITY_SEARCHES = [
    # Patent
    ("USPTO", 'FROM "uspto.gov"'),
    ("Patent EBC", 'FROM "ebc@uspto.gov"'),
    ("Patent AAU", 'FROM "HelpAAU@uspto.gov"'),
    # Revenue
    ("Stripe", 'FROM "stripe.com"'),
    ("Shopify", 'FROM "shopify.com"'),
    ("Gumroad", 'FROM "gumroad.com"'),
    # Outreach
    ("NIST", 'FROM "nist.gov"'),
    ("CISA", 'FROM "cisa.gov"'),
    # Security
    ("GitHub Security", 'FROM "noreply@github.com" SUBJECT "security"'),
    ("npm Advisory", 'FROM "npm"'),
    # Recent (last 3 days)
    ("Recent Unread", '(UNSEEN SINCE {3_days_ago})'),
]
```

### Step 5: Display results

For each match, show:
- From, Subject, Date (one line per email)
- Flag anything from USPTO, Stripe, or outreach contacts as HIGH PRIORITY
- Count unread messages

### Step 6: Patent-specific check

If user asks about patent specifically, run the full patent check:
```bash
python scripts/system/daily_patent_check.py --check-email
```

## Important Notes

- NEVER display full email bodies (copyright + privacy)
- Show From/Subject/Date only — enough to know what's there
- ProtonMail Bridge must be running (check: `Get-Process bridge`)
- Gmail App Password is NOT the Google account password
- If Bridge is not running, skip ProtonMail and report that it's down
- If Gmail creds are missing, skip Gmail and report what's needed

## Output Format

```
EMAIL CHECK — 2026-03-26
========================================
PROTONMAIL (issdandavis@proton.me):
  [HIGH] USPTO — "AIA/122 form" from ebc@uspto.gov (Mar 26)
  [new]  3 unread messages

GMAIL (issdandavis7795@gmail.com):
  [new]  GitHub — "Security alert" from noreply@github.com (Mar 25)
  [new]  7 unread messages

PATENT STATUS: Waiting (5 biz days from Mar 26 → follow up Apr 2)
========================================
```

## Quick Test

```bash
python scripts/system/daily_patent_check.py --check-email
```

Related Skills

scbe-training-pair-authoring

6
from issdandavis/SCBE-AETHERMOORE

Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.

scbe-spin-conversation-engine

6
from issdandavis/SCBE-AETHERMOORE

Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.

scbe-research-training-bridge

6
from issdandavis/SCBE-AETHERMOORE

Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.

scbe-document-management

6
from issdandavis/SCBE-AETHERMOORE

Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.

scbe-colab-bridge

6
from issdandavis/SCBE-AETHERMOORE

Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.

scbe-claim-to-code-evidence

6
from issdandavis/SCBE-AETHERMOORE

Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.

scbe-autonomous-worker-productizer

6
from issdandavis/SCBE-AETHERMOORE

Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.

scbe-code-scanning-ops

6
from issdandavis/SCBE-AETHERMOORE

Operate GitHub code scanning and CodeQL remediation for SCBE repositories. Use when triaging code-scanning alerts, mapping alert classes to fix patterns, validating targeted regressions, or wiring dedicated CodeQL workflows and runbooks into the repo.

scbe-world-anvil-lore-rag-7th-tongue

6
from issdandavis/SCBE-AETHERMOORE

Build and operate a lore-focused RAG system using World Anvil exports and SCBE docs, with deterministic Claude/Codex cross-talk packets for handoff. Use when users ask to structure lore canon retrieval, sync worldbuilding data, enforce citation-grounded generation, or coordinate a 7th Tongue overseer lane across multiple AI agents.

scbe-webtoon-book-conversion

6
from issdandavis/SCBE-AETHERMOORE

Convert The Six Tongues Protocol and related manuscript sections into webtoon/manhwa storyboard packets, episode roadmaps, panel expansion plans, and image-generation-ready prompt lanes. Use when extending the series storyboard, adapting book chapters into vertical scroll episodes, or keeping art generation tied to canon instead of drifting into generic fantasy panels.

scbe-voice-render-verification

6
from issdandavis/SCBE-AETHERMOORE

Govern and verify SCBE voice rendering work that maps Langues weighting into breath, phase, and Layer 14 audio-axis packets. Use when implementing or reviewing `scripts/voice_gen_hf.py`, emitting sidecar voice packets, validating canonical tongue ordering, tuning breath planning or phase timing, or keeping voice docs and code aligned with `docs/LANGUES_WEIGHTING_SYSTEM.md` and `docs/specs/SCBE_VOICE_EMOTIONAL_TIMBRE_SYSTEM.md`.

scbe-universal-synthesis

6
from issdandavis/SCBE-AETHERMOORE

Orchestrate all installed Codex skills through an auto-updating synthesis matrix with Sacred Tongues routing, emotion/intent metadata, and decodable lexicon packets tied to established SCBE characters. Use when the user asks for cross-skill coordination, auto skill updates, multi-skill routing, or Sacred Tongues intent mapping.