deliverability
Skill5.9k starsChanged 4 days agoApache-2.0View on GitHub
Use when the question is whether email will reach the inbox, covering sending domain setup, authentication, list hygiene, complaint and bounce rates, or a drop in delivery.
3 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- vercel-labs/marketing-team-eve-templateword for word, first seen Nov 12, 2026
- andrewluxem/email-deliverability-suitetheir own version, first seen Sep 28, 2026
- 808enzo/chappietheir own version, first seen Sep 17, 2026
Who's talking about vercel/eve
- @qdrddr.bsky.social“@vercel.com Eve #Agentic #framework uses #filesystem as interface for tools, just drop a #TypeScript code …”Bluesky · Oct 16, 2026 · 8 likes
- @projectnothing.bsky.social“When frameworks like eve break out, it’s a sign: AI agents are no longer side projects—they’re becoming a …”Bluesky · Jun 17, 2026 · 3 likes
- @github-trending-js.bsky.social“📦 vercel / eve ⭐ 5,184 (+40) 🗒 TypeScript The Open Framework for Building Agents”Bluesky · Sep 17, 2026 · 2 likes
- DataDog/dd-trace-js“feat(llmobs): add external experiment recorder”GitHub · Jul 31, 2026 · 2 reactions
- byronwade/rebuzzle.byronwade.com“Bump the production-dependencies group across 1 directory with 13 updates”GitHub · Nov 9, 2026 · 1 reactions
The biggest 5 of 57 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 57
Talked about on GitHub and Bluesky (57 times).
On GitHub · 50
- Jul 31, 2026feat(llmobs): add external experiment recorder — DataDog/dd-trace-js2 reactions · 5 comments
- Nov 9, 2026Bump the production-dependencies group across 1 directory with 13 updates — byronwade/rebuzzle.byronwade.com1 reaction · 5 comments
- Nov 3, 2026chore(deps-dev): bump the npm-development group across 1 directory with 8 updates — ComposioHQ/composio1 reaction · 6 comments
- Oct 30, 2026Bump the production-dependencies group across 1 directory with 11 updates — byronwade/rebuzzle.byronwade.com1 reaction · 6 comments
- Oct 30, 2026chore(deps-dev): bump the npm-development group with 7 updates — ComposioHQ/composio1 reaction · 6 comments
45 more on GitHub
- Oct 16, 2026chore(deps-dev): bump the npm-development group across 1 directory with 8 updates — ComposioHQ/composio1 reaction · 6 comments
- Oct 16, 2026chore(deps-dev): bump the npm-development group with 4 updates — ComposioHQ/composio1 reaction · 6 comments
- Oct 13, 2026chore(deps-dev): bump the npm-development group with 3 updates — ComposioHQ/composio1 reaction · 5 comments
- Oct 9, 2026chore(deps-dev): bump the npm-development group across 1 directory with 7 updates — ComposioHQ/composio1 reaction · 6 comments
- Sep 25, 2026chore(deps-dev): bump the npm-development group with 8 updates — ComposioHQ/composio1 reaction · 4 comments
- Sep 14, 2026chore(deps): bump the production-dependencies group across 1 directory with 13 updates — byronwade/rebuzzle.byronwade.com1 reaction · 5 comments
- Sep 11, 2026chore(deps-dev): bump the npm-development group with 5 updates — ComposioHQ/composio1 reaction · 4 comments
- Sep 7, 2026chore(deps): bump the production-dependencies group across 1 directory with 12 updates — byronwade/rebuzzle.byronwade.com1 reaction · 4 comments
- Sep 1, 2026@nuxt/kit missing @nuxt/schema dependency breaks TypeScript with pnpm 12 GVS — nuxt/nuxt1 reaction
- Aug 31, 2026chore(deps): bump the production-dependencies group with 11 updates — byronwade/rebuzzle.byronwade.com1 reaction · 4 comments
- Aug 26, 2026Add conversational Discord agent template — vercel/eve-examples1 reaction · 2 comments
- Aug 13, 2026基于 vercel/eve 实现 agents demo 切片 — SawanaLabs/agent-demos1 reaction · 3 comments
- Jul 28, 2026fix(nitro): vercel function rules - preserve relative symlinks — nitrojs/nitro1 reaction · 4 comments
- Jul 3, 2026Add Eve adapter (eve_gateway + eve_local) — paperclipai/paperclip1 reaction · 6 comments
- Jun 30, 2026Install eve skill from vercel/eve — TommyBez/evex1 reaction · 2 comments
- Jun 19, 2026[codex] Read downloads from the sandbox stream — remiconnesson/eve-single-user-agent-starter1 reaction · 1 comment
- Nov 11, 2026feat: fully replace duplicated Bot/Frontend agent infrastructure with eve + ambient Slack — alexj11324/Mikka0 reactions · 24 comments
- Nov 9, 2026Broken links report — Li-Evan/awesome-jev0 reactions
- Nov 3, 2026[ARCHITECTURE ASSESSMENT] Eve.dev adoption — no control-plane replacement; bounded comparative pilot — mastermindx-market-intelligence/Mastermind0 reactions
- Nov 2, 2026Broken links report — Li-Evan/awesome-jev0 reactions
- Oct 27, 2026Telegram HITL: при нажатии кнопки подтверждения теряется нажавший (auth: null) — в вендоренном eve 0.51.1 нет фикса vercel/eve#4241 — smixs/iva-agent0 reactions · 2 comments
- Oct 26, 2026Broken links report — Li-Evan/awesome-jev0 reactions
- Oct 19, 2026Broken links report — Li-Evan/awesome-jev0 reactions
- Oct 18, 2026T2: Preserve authenticated attachments when continuing copied history — FranciscoMoretti/chat-js0 reactions
- Oct 18, 2026T1/T2: Adopt upstream structured history imports with completed tools and attachments — FranciscoMoretti/chat-js0 reactions
- Oct 12, 2026Broken links report — Li-Evan/awesome-jev0 reactions
- Oct 11, 2026`vercel dev` stalls silently (no port, no error) when the Next.js dev-manifest config loader exits non-zero — vercel/vercel0 reactions
- Oct 6, 2026Research: custom SPARQL-generation model + separate review layer (prior art: eve + Qwen + Jev data analyst) — wazootech/wazoo-memorybench0 reactions
- Oct 3, 2026[Add] eve (vercel/eve) — PyTorchKR/landscape0 reactions
- Sep 23, 2026research(eve): isoler les contextes et garder le root CStack compact en multi-agent — charlescstpierr/cstack0 reactions
- Sep 19, 2026未対応のカードの効果の翻訳を、会話の中で Pull Request として足せるようにする — mokosystem/pokemon-tcg-buddy0 reactions
- Sep 1, 2026sep 2026 — kimtth/azure-openai-llm-notes0 reactions
- Aug 12, 2026Ship an eve and AI SDK memory integration guide — Studio-Moser/Advisaur-MCP0 reactions
- Aug 12, 2026Evaluate eve as a seventh distribution channel — tartinerlabs/skills0 reactions · 2 comments
- Aug 10, 2026epic(ai): the agent harness -- vision, prior art, and the plan to stand behind "or the agent harness itself" — routecraftjs/routecraft0 reactions · 4 comments
- Jul 14, 2026Epic: publish TypeScript SDK and durable Eve approval channel — asiraky/mayi0 reactions · 2 comments
- Jul 13, 2026@ai-sdk/openai: support ordered additional_tools after a normal tool result — vercel/ai0 reactions · 4 comments
- Jul 4, 2026test(eve): run eve evals as fak parity and regression witnesses — anthony-chaudhary/fak0 reactions · 7 comments
- Jul 4, 2026feat(eve): lease-gate shared-sandbox subagent fan-out from child session streams — anthony-chaudhary/fak0 reactions · 1 comment
- Jul 4, 2026feat(eve): preflight MCP/OpenAPI connections for scoped auth, allowlists, and approval gates — anthony-chaudhary/fak0 reactions · 1 comment
- Jul 4, 2026feat(eve): compile agent/ directories into fak policy and mount manifests — anthony-chaudhary/fak0 reactions · 1 comment
- Jul 4, 2026epic(eve): Vercel eve integration bridge - filesystem agents, policy lint, evals, and observability — anthony-chaudhary/fak0 reactions
- Jun 23, 2026@vercel/connect/eve: support context-aware Slack installation selection — vercel/vercel0 reactions
- Jun 19, 2026Remove sandbox stream compatibility fix after Eve #117 is released — remiconnesson/eve-single-user-agent-starter0 reactions
- Jun 19, 2026Add Vercel Eve sandbox backend adapter support — sandbox0-ai/sandbox00 reactions
On Bluesky · 7
- Oct 16, 2026@vercel.com Eve #Agentic #framework uses #filesystem as interface for tools, just drop a #TypeScript code into a folder, the filename… — @qdrddr.bsky.social8 likes and reposts · 1 reply
- Jun 17, 2026When frameworks like eve break out, it’s a sign: AI agents are no longer side projects—they’re becoming a new pillar of mainstream software… — @projectnothing.bsky.social3 likes and reposts
- Sep 17, 2026📦 vercel / eve ⭐ 5,184 (+40) 🗒 TypeScript The Open Framework for Building Agents — @github-trending-js.bsky.social2 likes and reposts
- Sep 20, 2026github.com/vercel/eve GitHub - vercel/eve: The Open Framework for Building Agents — @technews4869.bsky.social1 likes and repost
- Aug 11, 2026Cloudflare OS blog: blog.cloudflare.com/cloudflare-os/, github.com/cloudflare/cloudflare-os Vercel eve: vercel.com/blog/introducing-eve ·… — @akash-bhatia.bsky.social1 likes and repost
2 more on Bluesky
- Jul 2, 2026Vercel's eve is a filesystem-first framework for durable AI agents: an agent is a directory of instructions, tools, skills, channels, and… — @agentpalisade.bsky.social1 likes and repost
- Jun 17, 2026The Framework for Building Agents https://github.com/vercel/eve — @laxima-tech.bsky.social1 likes and repost
Other versions3 projects use a version of this.
Word for word · 1
- vercel-labs/marketing-team-eve-template★ 456100% same
Edited · 0
None found.
Wrote their own version · 2
- 808enzo/chappie★ 3same name
- andrewluxem/email-deliverability-suite★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository115 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apps/docs/AGENTS.mdAGENTS.md
- apps/templates/eve-agent-python-template/AGENTS.mdAGENTS.md
- apps/templates/eve-agent-python-template/apps/web/AGENTS.mdAGENTS.md
- apps/templates/eve-chat-template/AGENTS.mdAGENTS.md
- apps/templates/eve-coding-agent-template/AGENTS.mdAGENTS.md
- apps/templates/eve-content-agent-template/AGENTS.mdAGENTS.md
- apps/templates/eve-contentful-agent-template/AGENTS.mdAGENTS.md
- apps/templates/eve-data-analyst-template/AGENTS.mdAGENTS.md
- apps/templates/eve-discord-agent-template/AGENTS.mdAGENTS.md
- apps/templates/eve-llm-council-template/AGENTS.mdAGENTS.md
- apps/templates/eve-mem0-template/AGENTS.mdAGENTS.md
- apps/templates/eve-memory-agent-template/AGENTS.mdAGENTS.md
- apps/templates/eve-slack-agent-template/AGENTS.mdAGENTS.md
- apps/templates/eve-software-factory-template/AGENTS.mdAGENTS.md
- apps/templates/eve-sre-agent-template/AGENTS.mdAGENTS.md
- apps/templates/eve-tanstack-start-template/AGENTS.mdAGENTS.md
- apps/templates/eve-vercel-drives-starter/AGENTS.mdAGENTS.md
- apps/templates/eve-voice-template/AGENTS.mdAGENTS.md
- apps/templates/kody-eve-template/AGENTS.mdAGENTS.md
- apps/templates/marketing-team-eve-template/AGENTS.mdAGENTS.md
- apps/templates/openinstinct/AGENTS.mdAGENTS.md
- apps/templates/personal-agent-template/AGENTS.mdAGENTS.md
- apps/templates/sanity-copilot-eve-template/AGENTS.mdAGENTS.md
- apps/templates/slack-company-brain-template/AGENTS.mdAGENTS.md
- packages/eve-agent-desktop/AGENTS.mdAGENTS.md
- packages/eve-code/AGENTS.mdAGENTS.md
- packages/eve-computer-use/AGENTS.mdAGENTS.md
- packages/eve-custom-skills/AGENTS.mdAGENTS.md
- packages/eve-git/AGENTS.mdAGENTS.md
- packages/eve/src/internal/nitro/AGENTS.mdAGENTS.md
- apps/templates/eve-agent-python-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-chat-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-coding-agent-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-content-agent-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-contentful-agent-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-data-analyst-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-discord-agent-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-llm-council-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-mem0-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-memory-agent-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-slack-agent-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-software-factory-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-sre-agent-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-tanstack-start-template/CLAUDE.mdCLAUDE.md
- apps/templates/eve-vercel-drives-starter/CLAUDE.mdCLAUDE.md
- apps/templates/eve-voice-template/CLAUDE.mdCLAUDE.md
- apps/templates/kody-eve-template/CLAUDE.mdCLAUDE.md
- apps/templates/marketing-team-eve-template/CLAUDE.mdCLAUDE.md
- apps/templates/openinstinct/CLAUDE.mdCLAUDE.md
- apps/templates/personal-agent-template/CLAUDE.mdCLAUDE.md
- apps/templates/sanity-copilot-eve-template/CLAUDE.mdCLAUDE.md
- apps/templates/slack-company-brain-template/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- gh-pr-descriptionSkill
- pr-shepherdSkill
- technical-writingSkill
- test-auditSkill
- create-payment-credentialSkill
- dashboard-chat-best-practicesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 68
When one of these is the actual question, say what would answer it and who can check.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deliverability
Deliverability advice is mostly unfalsifiable from where you sit. Resend will tell you what it knows about the sending domain and what happened to mail already sent. Inbox placement, what any provider thinks of the domain today, and whether a filter is quietly junking the whole campaign are questions to raise rather than blanks to fill in.
That gap is the discipline in this skill. Report what you verified with a tool, name what you could not check, and never let the first turn into the second. A domain with clean records is not evidence that mail is reaching inboxes, and saying it is does more damage than saying nothing.
The same rule applies to numbers. Every threshold here traces to a page listed in references/checklist.md, and the providers do not publish the same numbers, so quote a threshold with the provider attached and never quote one you cannot point at.
Check first, in this order
- Is the sending domain verified, and does the from address use it? Read the domain rather than assuming. An unverified domain is the most common cause of mail that never leaves.
- What happened to the last comparable send? Delivered, bounced, complained. Real numbers from real sends beat any general advice you could give.
- Is this a bulk sender situation? Close to 5,000 messages or more to personal Gmail accounts in 24 hours puts the domain permanently in Gmail's bulk sender category, and the requirements below become hard gates rather than good practice.
- What changed? Deliverability problems are almost always a delta: new domain, new volume, a list imported from somewhere, a change in content or cadence. Ask what moved before theorizing.
The requirements that are actually enforced
Google and Yahoo have enforced these since February 2024. Google ramped enforcement up again in November 2025, to include temporary and permanent rejections. Microsoft applies its own set to mail sent to Outlook.com and its other consumer domains from May 5, 2025. Mail that fails these gets rate-limited, junked, or rejected.
- SPF and DKIM both configured, and the From domain aligned with one of them. Authenticating without aligning is the trap: signing with the platform's domain while sending from yours passes SPF and DKIM but fails DMARC. Google says alignment with both is likely to become a requirement, so treat one as the floor rather than the goal.
- DMARC published. Google and Yahoo both accept
p=none, so the requirement is weaker than the advice:quarantineorrejectis what protects the domain, and Resend's own guidance is to publishp=nonefirst and move up once every sending source is passing. - One-click unsubscribe on marketing mail, meaning the
List-UnsubscribeandList-Unsubscribe-Postheaders together, plus a visible unsubscribe link in the body. A landing page with a login does not satisfy it. Google and Yahoo both began enforcing it in June 2024. Then honor the request quickly: Yahoo requires two days, Google recommends 48 hours. - Spam complaint rate below 0.30% at both Google and Yahoo, which is where enforcement starts rather than a safe place to sit. Google's own recommendation is to stay below 0.10%.
These pages get revised, and the dates above were checked in July 2026. When the answer turns on a specific threshold, fetch the source from the list in references/checklist.md instead of quoting from memory.
What the law requires, which is a separate question
Everything above is what mailbox providers enforce. Marketing mail also has to satisfy the law where the recipients are, and those rules do not care about your complaint rate. A send can be perfectly deliverable and still unlawful.
Two of these are checkable from the copy, and check_send_readiness reports on both, so check them every time:
- A valid physical postal address of the sender, in the message. US law requires it in every commercial message, and it is the single most commonly missing element.
- Identification that the message is an advertisement, clear and conspicuous, unless the recipient gave prior affirmative consent. Plus clear notice of how to decline further mail.
Two more are about the mechanism rather than the copy. The opt-out has to stay capable of receiving requests for at least 30 days after the send, and a request has to be honored within 10 business days. Both are process questions for whoever runs the list.
Consent is the part you cannot inspect, and it is the part that differs most by jurisdiction. In the UK and the EU, marketing email to individuals needs prior consent, with a narrow exception for people whose details you collected while selling them something, where you market only similar products and you offered a free and simple way to refuse both at collection and in every message since. A February 2026 amendment extended a version of that exception to charities. Under the GDPR, direct marketing can rest on legitimate interests, but a person's objection to direct marketing ends the matter, with no balancing against your interest in sending.
So ask rather than assume. Where the list came from, whether consent was recorded, and which countries the recipients are in are all questions for the user, and the answer changes what is allowed. Say plainly that you are naming requirements rather than giving legal advice, and that US, UK, and EU rules are not the whole world: a list spanning other markets needs someone to confirm what applies.
What follows from the complaint rate
Almost every list decision comes back to that number, and it is small enough to be worth making concrete: at 10,000 delivered, 30 complaints is the ceiling.
- Yahoo computes its rate over mail delivered to the inbox rather than over everything it accepted, so the rate you work out from your own send totals reads lower than the one Yahoo acts on. That is a reason to leave room under 0.30% rather than to sit on it.
- A hidden or awkward unsubscribe does not keep subscribers. It converts people who would have left quietly into complaints, which is the expensive outcome.
- Mailing people who never engage is not free. It suppresses reach for the people who do want the mail.
- A list you did not build is the fastest way to the ceiling. Purchased or scraped addresses, and old lists imported from a previous tool, arrive with no consent record and often with spam traps in them.
- Sudden volume increases read as a change in behavior. Ramp instead, and expect throttling if you do not. Resend's warm-up guidance is tighter than the enforcement floor, at below 0.08% complaints and below 4% bounces while you ramp, with the instruction to slow down if either climbs.
Say what you cannot see
State these as open questions rather than findings, every time:
- Whether mail landed in the inbox or the spam folder. Delivered means accepted by the receiving server, nothing more.
- The domain's current reputation with any provider. That lives in Google Postmaster Tools, Microsoft SNDS, and Yahoo's Complaint Feedback Loop.
- Whether the DMARC record is published, and at what policy, unless the user tells you or shows you.
- Blocklist status.
- Whether there is a lawful basis for mailing this list, and which jurisdictions it spans.
- How the email renders across clients.
- Open rates as a measure of anything on Apple clients, since Mail Privacy Protection inflates them.
When one of these is the actual question, say what would answer it and who can check. Pointing the user at Postmaster Tools is a better answer than a confident guess.
References
references/checklist.md: the checks in priority order, each marked with the tool that verifies it ornonewhen nothing available here can, plus the concrete thresholds, each attributed to the page it came from. Its last section covers the legal requirements, which sit outside that priority order because a send that fails them should not go out at all.
Layers on top of
email-style covers the content side of the same problem: the copy patterns that get mail reported, and the unsubscribe and sender-identity conventions that keep complaints low.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

