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.
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…
$ npx skills add ericrisco/rsc-harness --skill email-connector -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ericrisco/rsc-harness email-connector --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "email-connector" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/email-connector into .claude/skills/email-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-connector", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ericrisco/rsc-harness/tree/main/skills/email-connectorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ericrisco/rsc-harness --skill email-connector -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ericrisco/rsc-harness email-connector --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/email-connector .agents/skills/email-connector && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "email-connector" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/email-connector into .agents/skills/email-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-connector", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ericrisco/rsc-harness --skill email-connector -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ericrisco/rsc-harness email-connector --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/email-connector .cursor/skills/email-connector && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "email-connector" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/email-connector into .cursor/skills/email-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-connector", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ericrisco/rsc-harness.git --path skills/email-connector--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ericrisco/rsc-harness --skill email-connector -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ericrisco/rsc-harness email-connector --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/email-connector .gemini/skills/email-connector && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "email-connector" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/email-connector into .gemini/skills/email-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-connector", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ericrisco/rsc-harness email-connectorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ericrisco/rsc-harness --skill email-connector -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/email-connector .github/skills/email-connector && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "email-connector" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/email-connector into .github/skills/email-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-connector", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ericrisco/rsc-harness --skill email-connector -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ericrisco/rsc-harness email-connector --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/email-connector .opencode/skills/email-connector && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "email-connector" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/email-connector into .opencode/skills/email-connector/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-connector", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
email-connectorA 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. 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.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e3d5b33. It shows what the files ask for, not the result of running them.
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.
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.
Hosts in commands or code, which the agent is likely to contact:
api.postmarkapp.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
RESEND_API_KEYSENDGRID_API_KEYPOSTMARK_SERVER_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from ericrisco/rsc-harness at commit e3d5b33, republished under its MIT licence (© ericrisco). 874 words, ~3,130 tokens.
.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.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.
| Provider | Best default fit | Native idempotency | Template model | Batch cap | Pick when |
|---|---|---|---|---|---|
| Resend | Greenfield, React/Next shops | Yes — { idempotencyKey }, 24h, ≤256 chars | React Email JSX via react: | 100/call | You want JSX templates and the least ceremony |
| SendGrid (Twilio) | High volume, marketing+txn mix | No — dedupe yourself | d- dynamic templates + dynamicTemplateData | per-send personalizations | You need 10k req/s scale or already on Twilio |
| Postmark | Pure transactional, deliverability-first | No — self-dedupe via your key + webhooks | Postmark server templates | per-stream | Receipts/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.
sendEmail() seamOne 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.
// 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 */ }// 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 };
}// 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'] };
}// 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:
// 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 });// 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 });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.
// 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>
);
}// 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
});// Bad — string concat, unescaped user input straight into HTML
const html = '<h1>Hi ' + req.body.name + '</h1>'; // XSS + broken layout riskEvery 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.
const idempotencyKey = `pwreset:${userId}:${tokenVersion}`; // stable across retries{ 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.sent_emails table inside the same transaction as the send,
unique-constrain it, and skip if it already exists.// 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 });// Bad — no key; queue retry sends the reset 3×
await sendEmail({ to, subject, react: <Reset url={url} /> } as any);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:
idempotencyKey per chunk.batchValidation: 'permissive' so one bad address does not nuke the chunk.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
}Reputation isolation. Give each stream a distinct From, subdomain, and stream/IP so they cannot poison each other:
| Stream | From | Subdomain | Provider stream |
|---|---|---|---|
| Transactional | noreply@notify.yourdomain.com | notify. | Resend default / Postmark outbound |
| Broadcast | news@promo.yourdomain.com | promo. | 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.
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.
// 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');
}// 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-pattern | Why it bites | Do instead |
|---|---|---|
API key hard-coded (re_…, SG.…, server token) | Committed credential = send-as-you abuse | Read from process.env; rotate via ../secure-coding/SKILL.md |
| No idempotency key on transactional sends | Queue/serverless retry double-sends | Deterministic event:userId:version key |
| One stream for everything | Marketing hit poisons reset/receipt deliverability | Split From + subdomain + stream (Step 6) |
| String-concatenated HTML with user input | XSS + broken layout | React Email component or d- dynamic template |
Ignoring per-row data.errors in a batch | Silent partial loss; "looked like 200" | Inspect both arrays; re-queue only failures |
| Trusting the webhook without signature check | Anyone can poison your suppression list | Verify signature on raw body, then parse |
| Sending to a bounced/complained address | Reputation damage, ISP penalties | Filter against suppression list before send |
| Calling the provider SDK at scattered call sites | Provider swap = grep across the app | One 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
SKILL.md and 4 other files (scripts, references) in skills/email-connector of ericrisco/rsc-harness.
Open the folder on GitHubat commit e3d5b33
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Email Connector this skillericrisco/rsc-harness | 174 | — | ~3.1k | Automated safety check: Pass | MIT | |
| E2a Doctortokencanopy/e2a | 193 | — | ~994 | Automated safety check: Pass | Apache-2.0 | |
| Agent Email Inboxviclafouch/meme-studio | 110 | 2 repos | ~10k | Automated safety check: Warn | None | |
| Lunora Setup Mailanolilab/lunora | 282 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Resend CLIAsymmetric-al/core | 381 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Emailmagnus919/agent-skills | 116 | — | ~2.4k | Automated safety check: Pass | MIT |
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.
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…
anolilab/lunora
Adds transactional email to a Lunora app with the mail registry item (@lunora/mail).
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…
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…
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…
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…
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…
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…
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…
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…
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.
Categories
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.
Email Connector fits situations like: wiring server code to send transactional; bulk email via Resend; postmark: a provider-agnostic sendEmail() seam; idempotent retries.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.