Agent skill

Email Connector

by ericrisco in ericrisco/rsc-harness

A skill your agent uses when wiring server code to send transactional or bulk email via Resend, SendGrid, or Postmark: a provider-agnostic sendEmail() seam, idempotent retries, 100-cap batches with…

MITAuto-check passedBackend & APIs

Install Email Connector

skills CLI
$ npx skills add ericrisco/rsc-harness --skill email-connector -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ericrisco/rsc-harness email-connector --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/email-connector .claude/skills/email-connector && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
email-connector
GitHub stars
174
Token cost
~3.1k tokens
SKILL.md length
874 words
Files
5 (incl. scripts, references)
Skills in repo
233
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when wiring server code to send transactional or bulk email via Resend, SendGrid, or Postmark: a provider-agnostic sendEmail() seam, idempotent retries, 100-cap batches with…

  • Works in 7 steps: pick a provider → the sendEmail() seam → templates → …
  • Wiring server code to send transactional
  • SKILL.md covers Step 1 — pick a provider, Step 2 — the sendEmail() seam, Step 3 — templates and Step 4 — idempotency & retries, plus 4 more sections
  • Runs Shell scripts from its folder; reaches api.postmarkapp.com; needs RESEND_API_KEY and SENDGRID_API_KEY

What it does

Email Connector is an agent skill from ericrisco/rsc-harness. Use when wiring server code to send transactional or bulk email via Resend, SendGrid, or Postmark: a provider-agnostic sendEmail() seam, idempotent retries, 100-cap batches with partial failures, transactional-vs-broadcast streams, bounce webhooks feeding a suppression list. NOT SPF/DKIM/DMARC inbox reputation (that is email-deliverability).

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `evals/README.md`, `evals/cases.yaml` and `references/providers.md`).

It sits in Backend & APIs, covering Webhooks, Transactional email and Email management. It works with SendGrid and React. The repository describes itself as: Your agent invents things because it has no memory, and can't touch your database because it has no arms. rsc is the meta-harness that gives it both, plus the trade to know the… The licence is MIT.

When your agent uses it

  • Wiring server code to send transactional
  • Bulk email via Resend
  • Postmark: a provider-agnostic sendEmail() seam
  • Idempotent retries

Example prompts

  • “/email-connector”

Requirements

  • A Bash shell
  • A credential in RESEND_API_KEY
  • A credential in SENDGRID_API_KEY

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. pick a provider
  2. the sendEmail() seam
  3. templates
  4. idempotency & retries
  5. batch / bulk
  6. transactional vs broadcast split
  7. delivery/bounce/complaint webhook → suppression

What it can do on your machine

Read from SKILL.md and the folder at commit e3d5b33. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.postmarkapp.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • RESEND_API_KEY
    • SENDGRID_API_KEY
    • POSTMARK_SERVER_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Email Connector loads about 3.1k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 874 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from ericrisco/rsc-harness at commit e3d5b33, republished under its MIT licence (© ericrisco). 874 words, ~3,130 tokens.

Download SKILL.mdSave it as .claude/skills/email-connector/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
email-connector
description
Use when wiring server code to send transactional or bulk email via Resend, SendGrid, or Postmark: a provider-agnostic sendEmail() seam, idempotent retries, 100-cap batches with partial failures, transactional-vs-broadcast streams, bounce webhooks feeding a suppression list. NOT SPF/DKIM/DMARC inbox reputation (that is `email-deliverability`).
tags
email, transactional-email, resend, sendgrid, postmark, webhooks, idempotency
recommends
email-deliverability, newsletter, webhooks, secure-coding, api-connector-builder, automation-flows
origin
risco

email-connector — put transactional & bulk email on the wire

You wire the send. A welcome mail, a password reset, a receipt, a 4,000-row digest — your job is the server code that hands it to a provider, makes it safe to retry, and keeps the suppression list honest. You do not own the inbox (SPF/DKIM/DMARC/reputation is ../email-deliverability/SKILL.md) and you do not own the words (subject lines and growth are ../newsletter/SKILL.md, launch copy is ../marketing/SKILL.md). Generic typed clients for any REST API are ../api-connector-builder/SKILL.md; deciding when a multi-step sequence fires is ../automation-flows/SKILL.md.

Stack as of June 2026: resend 6.12.4, @sendgrid/mail 8.1.6, Postmark via its HTTP API, React Email 5.0 (React 19.2 / Next.js 16, Tailwind 4), Node 20+ / TS.

scripts/verify.sh is read-only and greps a target for the four invariants this skill exists to hold: env-sourced key, idempotency, a single sendEmail() seam, and a webhook signature checked on the raw body.

Step 1 — pick a provider

ProviderBest default fitNative idempotencyTemplate modelBatch capPick when
ResendGreenfield, React/Next shopsYes — { idempotencyKey }, 24h, ≤256 charsReact Email JSX via react:100/callYou want JSX templates and the least ceremony
SendGrid (Twilio)High volume, marketing+txn mixNo — dedupe yourselfd- dynamic templates + dynamicTemplateDataper-send personalizationsYou need 10k req/s scale or already on Twilio
PostmarkPure transactional, deliverability-firstNo — self-dedupe via your key + webhooksPostmark server templatesper-streamReceipts/resets must never queue behind marketing

Idempotency support changes your strategy, not just your config — see Step 4. Full per-provider matrix (auth header, SDK + version, single/batch signatures, idempotency model, stream/subdomain model, dynamic-template syntax, webhook event names, rate limits, when to pick each) plus a suppression-webhook handler skeleton per provider is in references/providers.md.

Step 2 — the sendEmail() seam

One provider-agnostic function. The rest of the app calls sendEmail(...) and never imports a provider SDK. Why: swapping SendGrid→Postmark is then one file, not a grep across every call site. That one file reads the key from process.env — never a re_… / SG.… / server-token literal, because a committed key is a send-as-you credential and burns your reputation with it.

ts
// lib/email/index.ts — the only place a provider SDK is imported
export type SendArgs = {
  to: string | string[];
  subject: string;
  react?: React.ReactElement; // template component
  html?: string;
  text?: string;
  idempotencyKey: string;     // required for transactional sends
  stream?: 'transactional' | 'broadcast';
};
export async function sendEmail(args: SendArgs): Promise<{ id: string }> { /* provider impl */ }
ts
// lib/email/resend.ts
import { Resend } from 'resend';
const resend = new Resend(process.env.RESEND_API_KEY);

export async function sendEmail(a: SendArgs) {
  const { data, error } = await resend.emails.send(
    { from: 'YourApp <noreply@notify.yourdomain.com>', to: a.to, subject: a.subject, react: a.react, html: a.html, text: a.text },
    { idempotencyKey: a.idempotencyKey }, // 2nd arg, retained 24h, ≤256 chars
  );
  if (error) throw new Error(error.message);
  return { id: data!.id };
}
ts
// lib/email/sendgrid.ts
import sgMail from '@sendgrid/mail';
sgMail.setApiKey(process.env.SENDGRID_API_KEY!);

export async function sendEmail(a: SendArgs) {
  const [res] = await sgMail.send({
    from: 'noreply@notify.yourdomain.com',
    to: a.to, subject: a.subject, html: a.html, text: a.text,
    // SendGrid has no idempotency key — guard with your own dedupe (Step 4)
  });
  return { id: res.headers['x-message-id'] };
}
ts
// lib/email/postmark.ts — raw HTTP, X-Postmark-Server-Token header
export async function sendEmail(a: SendArgs) {
  // Postmark has no idempotency key: self-dedupe BEFORE calling (Step 4)
  const r = await fetch('https://api.postmarkapp.com/email', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Accept: 'application/json',
      'X-Postmark-Server-Token': process.env.POSTMARK_SERVER_TOKEN!,
    },
    body: JSON.stringify({
      From: 'noreply@notify.yourdomain.com',
      To: Array.isArray(a.to) ? a.to.join(',') : a.to,
      Subject: a.subject, HtmlBody: a.html, TextBody: a.text,
      MessageStream: a.stream === 'broadcast' ? 'broadcast' : 'outbound',
    }),
  });
  if (!r.ok) throw new Error(`Postmark ${r.status}`);
  return { id: (await r.json()).MessageID };
}

Bad → Good:

ts
// Bad — provider SDK called directly in a route handler, key inline
import { Resend } from 'resend';
await new Resend('re_live_123abc').emails.send({ to, subject, html });
ts
// Good — call the seam; key is in env, swap is one file
import { sendEmail } from '@/lib/email';
await sendEmail({ to, subject, react: <Welcome name={n} />, idempotencyKey });

Step 3 — templates

Templates are typed components, not string concat. Why: JSX escapes interpolated values; hand-built HTML invites injection and broken markup.

React Email 5.0 renamed renderAsync → render. The Resend SDK lazily imports @react-email/render when you pass react:, so you usually pass the component directly and skip manual rendering.

tsx
// emails/welcome.tsx
import { Html, Button, Text } from '@react-email/components';
export function Welcome({ name, url }: { name: string; url: string }) {
  return (
    <Html>
      <Text>Welcome, {name}.</Text>
      <Button href={url}>Confirm your email</Button>
    </Html>
  );
}
ts
// SendGrid: dynamic template referenced by a d- id, data passed separately
await sgMail.send({
  to, from: 'noreply@notify.yourdomain.com',
  templateId: 'd-abc123...',                  // dynamic template id starts with d-
  dynamicTemplateData: { name, confirm_url },  // values, not pre-rendered HTML
});
ts
// Bad — string concat, unescaped user input straight into HTML
const html = '<h1>Hi ' + req.body.name + '</h1>'; // XSS + broken layout risk

Step 4 — idempotency & retries

Every transactional send carries a key, because queues retry, serverless functions re-fire, and users double-click — without a stable key one password reset becomes three. Derive it from the event, not the clock. Same event → same key → provider (or your table) collapses the duplicate.

ts
const idempotencyKey = `pwreset:${userId}:${tokenVersion}`; // stable across retries
  • Resend: native. Pass { idempotencyKey } as the 2nd arg; retained 24h, ≤256 chars. For a batch, the key represents the whole batch (e.g. team-quota/123456789), not each row.
  • Postmark / SendGrid: no idempotency feature. You must self-dedupe: write the key to a sent_emails table inside the same transaction as the send, unique-constrain it, and skip if it already exists.
ts
// Self-dedupe seam for providers without native keys
const inserted = await db.sentEmails.insertIfAbsent({ key: idempotencyKey });
if (!inserted) return; // already sent — do not re-fire
await sendEmail({ to, subject, html, idempotencyKey });
ts
// Bad — no key; queue retry sends the reset 3×
await sendEmail({ to, subject, react: <Reset url={url} /> } as any);
Show full SKILL.md (380 more words)Show less

Step 5 — batch / bulk

resend.batch.send([...]) is capped at 100 emails per call and forbids attachments/scheduling. Chunk larger runs, then inspect both arrays for partial failure — a 200 response can still contain per-row errors.

Checklist for a bulk run:

  • Filter the recipient list against the suppression list (Step 7) first.
  • Chunk into ≤100; one idempotencyKey per chunk.
  • Use batchValidation: 'permissive' so one bad address does not nuke the chunk.
  • Iterate results: collect succeeded ids and failed rows separately.
  • Re-queue only the failed rows; never replay the whole chunk.
ts
function chunk<T>(xs: T[], n = 100) { const o: T[][] = []; for (let i = 0; i < xs.length; i += n) o.push(xs.slice(i, i + n)); return o; }

for (const [i, group] of chunk(recipients).entries()) {
  const { data } = await resend.batch.send(
    group.map((r) => ({ from, to: r.email, subject, react: <Digest items={r.items} /> })),
    { idempotencyKey: `digest-2026-06/${i}`, batchValidation: 'permissive' },
  );
  data?.data?.forEach((d) => markSent(d.id));      // succeeded rows
  // inspect per-row errors and re-queue only those — do not replay the chunk
}

Step 6 — transactional vs broadcast split

Reputation isolation. Give each stream a distinct From, subdomain, and stream/IP so they cannot poison each other:

StreamFromSubdomainProvider stream
Transactionalnoreply@notify.yourdomain.comnotify.Resend default / Postmark outbound
Broadcastnews@promo.yourdomain.compromo.dedicated marketing stream / broadcast

Why: a marketing send that trips a blocklist must never take password resets down with it. The DNS/auth setup for those subdomains is ../email-deliverability/SKILL.md's job; you just send on the right one.

Step 7 — delivery/bounce/complaint webhook → suppression

The provider POSTs bounce and complaint events. Verify the signature on the raw body (parse after verifying), then write the address to a suppression list and check that list before every future send. The verification is absolute because this hook mutates the suppression list: unverified, anyone can suppress — or un-suppress — your users.

ts
// app/api/email/webhook/route.ts (Next.js 16) — verify BEFORE parsing
export async function POST(req: Request) {
  const raw = await req.text();                       // raw body, not req.json()
  if (!verifyProviderSignature(raw, req.headers)) return new Response('bad sig', { status: 401 });
  const event = JSON.parse(raw);
  if (event.type === 'email.bounced' || event.type === 'email.complained') {
    await db.suppressions.upsert({ email: event.data.to, reason: event.type });
  }
  return new Response('ok');
}
ts
// Before any send: skip suppressed addresses
const recipients = candidates.filter(async (e) => !(await db.suppressions.has(e)));

Generic webhook hardening (replay windows, queueing, retries beyond email) is ../webhooks/SKILL.md. The address-validity question (is this mailbox real before I ever send) is ../lead-gen/SKILL.md / ../email-deliverability/SKILL.md.

Anti-patterns

Anti-patternWhy it bitesDo instead
API key hard-coded (re_…, SG.…, server token)Committed credential = send-as-you abuseRead from process.env; rotate via ../secure-coding/SKILL.md
No idempotency key on transactional sendsQueue/serverless retry double-sendsDeterministic event:userId:version key
One stream for everythingMarketing hit poisons reset/receipt deliverabilitySplit From + subdomain + stream (Step 6)
String-concatenated HTML with user inputXSS + broken layoutReact Email component or d- dynamic template
Ignoring per-row data.errors in a batchSilent partial loss; "looked like 200"Inspect both arrays; re-queue only failures
Trusting the webhook without signature checkAnyone can poison your suppression listVerify signature on raw body, then parse
Sending to a bounced/complained addressReputation damage, ISP penaltiesFilter against suppression list before send
Calling the provider SDK at scattered call sitesProvider swap = grep across the appOne sendEmail() seam (Step 2)

© ericrisco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references) in skills/email-connector of ericrisco/rsc-harness.

  • SKILL.md
  • evals/README.md
  • evals/cases.yaml
  • references/providers.md
  • scripts/verify.sh

Open the folder on GitHubat commit e3d5b33

Compare with similar skills

Email Connector next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Email Connector compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Email Connector this skillericrisco/rsc-harness174—~3.1kAutomated safety check: PassMIT
E2a Doctortokencanopy/e2a193—~994Automated safety check: PassApache-2.0
Agent Email Inboxviclafouch/meme-studio1102 repos~10kAutomated safety check: WarnNone
Lunora Setup Mailanolilab/lunora282—~1.9kAutomated safety check: PassCustom licence
Resend CLIAsymmetric-al/core381—~4.3kAutomated safety check: PassMIT
Emailmagnus919/agent-skills116—~2.4kAutomated safety check: PassMIT

Similar skills

  • E2a Doctor

    tokencanopy/e2a

    A skill your agent uses when an existing e2a MCP connection, inbox, custom domain, protection policy, webhook, or message delivery is failing or unclear.

    193 GitHub stars~994 tokensUpdated 3 days ago
    Backend & APIsAuto-check passed
  • Agent Email Inbox

    viclafouch/meme-studio

    A skill your agent uses when setting up an email inbox for an AI agent (Moltbot, Clawdbot, or similar) - configuring inbound email, webhooks, tunneling for local development, and implementing…

    110 GitHub starsUsed in 2 repos~10k tokens
    Backend & APIsAuto-check: warnings
  • Lunora Setup Mail

    anolilab/lunora

    Adds transactional email to a Lunora app with the mail registry item (@lunora/mail).

    282 GitHub stars~1.9k tokensUpdated today
    Backend & APIsAuto-check passed
  • Resend CLI

    Asymmetric-al/core

    Operate the Resend platform from the terminal — send emails (including React Email .tsx templates via --react-email), manage domains, contacts, broadcasts, templates, webhooks, API keys, logs…

    381 GitHub stars~4.3k tokensUpdated today
    Backend & APIsAuto-check passed
  • Email

    magnus919/agent-skills

    Send and diagnose transactional email through Twilio SendGrid from a terminal or agent: send messages, check deliverability (bounces and spam reports), and verify Signed Event Webhook signatures…

    116 GitHub stars~2.4k tokensUpdated today
    Backend & APIsAuto-check passed
  • Email Template Builder

    alirezarezvani/claude-skills

    Build complete transactional email systems: React Email templates, provider integration (Resend, Postmark, SendGrid, AWS SES), preview server, i18n support, dark mode, spam optimization, analytics…

    28k GitHub starsUsed in 1 repo~3.8k tokens
    Frontend & DesignAuto-check passed

More from ericrisco/rsc-harness

All 233 skills in this repo
  • Ab Testing

    ericrisco/rsc-harness

    A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…

    174 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Accessibility

    ericrisco/rsc-harness

    A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…

    174 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Ads

    ericrisco/rsc-harness

    A skill your agent uses when running or fixing paid acquisition on Google or Meta — campaign structure (Performance Max, Demand Gen, Search, Advantage+), platform-fit creative, budget/scaling rules…

    174 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Agent Eval

    ericrisco/rsc-harness

    A skill your agent uses when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual…

    174 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed
  • AI Media

    ericrisco/rsc-harness

    A skill your agent uses when a creative goal must become a finished media file: pick and order generative-media models per modality — AI voiceover, image-to-video clips, score — then glue them with…

    174 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed
  • Analytics

    ericrisco/rsc-harness

    A skill your agent uses when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing.

    174 GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Email Connector

What does Email Connector do?

A skill your agent uses when wiring server code to send transactional or bulk email via Resend, SendGrid, or Postmark: a provider-agnostic sendEmail() seam, idempotent retries, 100-cap batches with…. Email Connector is an agent skill from ericrisco/rsc-harness. Use when wiring server code to send transactional or bulk email via Resend, SendGrid, or Postmark: a provider-agnostic sendEmail() seam, idempotent retries, 100-cap batches with partial failures, transactional-vs-broadcast streams, bounce webhooks feeding a suppression list.

When should I use Email Connector?

Email Connector fits situations like: wiring server code to send transactional; bulk email via Resend; postmark: a provider-agnostic sendEmail() seam; idempotent retries.

How do I install Email Connector in Claude Code?

Run `npx skills add ericrisco/rsc-harness --skill email-connector -a claude-code`. Or copy the skill folder (skills/email-connector in ericrisco/rsc-harness) into .claude/skills/email-connector in your project. Claude Code loads it when a task matches its description.

How do I install Email Connector in Codex?

Run `npx skills add ericrisco/rsc-harness --skill email-connector -a codex`. Or copy the skill folder (skills/email-connector in ericrisco/rsc-harness) into .agents/skills/email-connector in your project. Codex loads it when a task matches its description.

Can I use Email Connector in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ericrisco/rsc-harness --skill email-connector -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/email-connector, .gemini/skills/email-connector, .github/skills/email-connector and .opencode/skills/email-connector in your project.

What does Email Connector need to run?

Going by SKILL.md and its folder, Email Connector needs a shell for the scripts in its folder and credentials named RESEND_API_KEY, SENDGRID_API_KEY and POSTMARK_SERVER_TOKEN. Our summary lists: A Bash shell; A credential in RESEND_API_KEY; A credential in SENDGRID_API_KEY.

Does Email Connector access the network?

SKILL.md names 1 domain. In commands or code: api.postmarkapp.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Email Connector safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Email Connector use?

Email Connector is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Email Connector use?

About 3.1k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Email Connector?

Skills that share tags, products or a category with Email Connector: E2a Doctor (tokencanopy/e2a, 193 stars), Agent Email Inbox (viclafouch/meme-studio, 110 stars), Lunora Setup Mail (anolilab/lunora, 282 stars) and Resend CLI (Asymmetric-al/core, 381 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Email Connector?

ericrisco (a GitHub user) maintains it in ericrisco/rsc-harness, which has 174 GitHub stars. The repository holds 233 skills in this directory. The repository was last updated on October 7, 2026.

Source: ericrisco/rsc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.