Agent skill

Email Best Practices

by viclafouch in viclafouch/meme-studio

A skill your agent uses when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM…

No licenceAuto-check passedBackend & APIs

Install Email Best Practices

skills CLI
$ npx skills add viclafouch/meme-studio --skill email-best-practices -a claude-code

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

GitHub CLI
$ gh skill install viclafouch/meme-studio email-best-practices --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/viclafouch/meme-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/email-best-practices .claude/skills/email-best-practices && 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-best-practices
GitHub stars
110
Used in
7 other repos
Token cost
~787 tokens
SKILL.md length
159 words
Files
18
Skills in repo
12
Repo updated
First seen
Licence
None found

At a glance

A skill your agent uses when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM…

  • Building email features
  • SKILL.md covers Architecture Overview, Quick Reference and Start Here
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Emails going to spam

What it does

Email Best Practices is an agent skill from viclafouch/meme-studio. Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, or deciding transactional vs marketing.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. The skill folder holds 20 other files (for example `README.md`, `resources/compliance.md` and `resources/deliverability.md`).

It sits in Backend & APIs, covering Webhooks, Privacy and GDPR and Transactional email. The repository describes itself as: 📌 A complete and fast website building in Next.js for creating and sharing "internet memes".

When your agent uses it

  • Building email features
  • Emails going to spam
  • High bounce rates
  • Setting up SPF/DKIM/DMARC authentication

Example prompts

  • “/email-best-practices”

What it can do on your machine

Read from SKILL.md and the folder at commit d8fa0be. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Email Best Practices loads about 787 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 159 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~787

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); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 159 words (~787 tokens).

“Guidance for building deliverable, compliant, user-friendly emails.”

— opening of SKILL.md by viclafouch
name
email-best-practices

Read the full SKILL.md on GitHub

Files

SKILL.md and 17 other files in .agents/skills/email-best-practices of viclafouch/meme-studio.

  • SKILL.md
  • README.md
  • resources/compliance.md
  • resources/deliverability.md
  • resources/email-capture.md
  • resources/email-types.md
  • resources/list-management.md
  • resources/marketing-emails.md
  • resources/sending-reliability.md
  • resources/transactional-email-catalog.md
  • resources/transactional-emails.md
  • resources/webhooks-events.md
  • tests/README.md
  • tests/scenarios/01-spam-deliverability.md
  • tests/scenarios/02-multi-region-compliance.md
  • tests/scenarios/03-retry-idempotency.md
  • tests/scenarios/04-webhook-bounce-handling.md
  • tests/scenarios/05-new-saas-email-plan.md

Open the folder on GitHubat commit d8fa0be

Used in 7 other repositories

We found 9 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 7 other GitHub owners. This page covers the copy in viclafouch/meme-studio, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Email Best Practices 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 Best Practices compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Email Best Practices this skillviclafouch/meme-studio1107 repos~787Automated safety check: PassNone
API Route Patternsbybren-llc/safe-agentic-workflow423—~1.6kAutomated safety check: PassMIT
Loops APIopeninary/openinary412—~1.1kAutomated safety check: PassAGPL-3.0
E2a Doctortokencanopy/e2a193—~994Automated safety check: PassApache-2.0
E2a Integratetokencanopy/e2a193—~840Automated safety check: PassApache-2.0
Inngest Durable FunctionsAsymmetric-al/core381—~4kAutomated safety check: PassAGPL-3.0

Similar skills

  • API Route Patterns

    bybren-llc/safe-agentic-workflow

    API route implementation patterns with RLS, validation, and error handling. Use when creating API routes, implementing CRUD endpoints, adding server-side…

    423 GitHub stars~1.6k tokensUpdated 2 mo ago
    Backend & APIsAuto-check passed
  • Loops API

    openinary/openinary

    A skill your agent uses whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation.

    412 GitHub stars~1.1k tokensUpdated 5 days ago
    Backend & APIsAuto-check passed
  • 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 4 days ago
    Backend & APIsAuto-check passed
  • E2a Integrate

    tokencanopy/e2a

    A skill your agent uses when adding e2a email capabilities to an application or codebase: outbound sending, inbound signed webhooks, REST polling, or SDK integration.

    193 GitHub stars~840 tokensUpdated 4 days ago
    Backend & APIsAuto-check passed
  • Inngest Durable Functions

    Asymmetric-al/core

    A skill your agent uses when building functions that must survive process crashes, retry automatically on failure, run on a schedule, react to events, or maintain state across infrastructure…

    381 GitHub stars~4k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • API Integration Specialist

    aiskillstore/marketplace

    Expert in integrating third-party APIs with proper authentication, error handling, rate limiting, and retry logic.

    433 GitHub starsUsed in 2 repos~2.2k tokens
    Backend & APIsAuto-check passed

More from viclafouch/meme-studio

All 12 skills in this repo
  • React Email

    viclafouch/meme-studio

    A skill your agent uses when creating HTML email templates with React components - welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails.

    110 GitHub starsUsed in 2 repos~3.6k tokens
    Auto-check passed
  • Send Email

    viclafouch/meme-studio

    A skill your agent uses when sending transactional emails (welcome messages, order confirmations, password resets, receipts), notifications, or bulk emails via Resend API.

    110 GitHub starsUsed in 2 repos~3.8k tokens
    Auto-check passed
  • Resend

    viclafouch/meme-studio

    A skill your agent uses when working with Resend email platform - routes to specific sub-skills for sending, receiving, audiences, or broadcasts.

    110 GitHub starsUsed in 2 repos~823 tokens
    Auto-check passed
  • Better Auth Best Practices

    viclafouch/meme-studio

    Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.

    110 GitHub starsUsed in 5 repos~1.5k tokens
    Auto-check passed
  • Resend Inbound

    viclafouch/meme-studio

    A skill your agent uses when receiving emails with Resend - setting up inbound domains, processing email.received webhooks, retrieving email content/attachments, or forwarding received emails.

    110 GitHub starsUsed in 2 repos~2.1k tokens
    Auto-check: warnings
  • Update Deps

    viclafouch/meme-studio

    Audit all outdated dependencies with detailed research on changelogs, breaking changes, bug fixes, and deprecations.

    110 GitHub stars~2.6k tokensUpdated 6 mo ago
    Auto-check passed

Categories

Questions about Email Best Practices

What does Email Best Practices do?

A skill your agent uses when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM…. Email Best Practices is an agent skill from viclafouch/meme-studio. Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM, GDPR, CASL), handling webhooks, retry logic, or deciding transactional vs marketing.

When should I use Email Best Practices?

Email Best Practices fits situations like: building email features; emails going to spam; high bounce rates; setting up SPF/DKIM/DMARC authentication.

How do I install Email Best Practices in Claude Code?

Run `npx skills add viclafouch/meme-studio --skill email-best-practices -a claude-code`. Or copy the skill folder (.agents/skills/email-best-practices in viclafouch/meme-studio) into .claude/skills/email-best-practices in your project. Claude Code loads it when a task matches its description.

How do I install Email Best Practices in Codex?

Run `npx skills add viclafouch/meme-studio --skill email-best-practices -a codex`. Or copy the skill folder (.agents/skills/email-best-practices in viclafouch/meme-studio) into .agents/skills/email-best-practices in your project. Codex loads it when a task matches its description.

Can I use Email Best Practices 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 viclafouch/meme-studio --skill email-best-practices -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-best-practices, .gemini/skills/email-best-practices, .github/skills/email-best-practices and .opencode/skills/email-best-practices in your project.

What does Email Best Practices need to run?

SKILL.md names no scripts, command-line tools or credentials: Email Best Practices is instructions for the agent only.

Does Email Best Practices access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Email Best Practices 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. Review the folder before installing.

What licence does Email Best Practices use?

No licence was found for Email Best Practices or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Email Best Practices use?

About 787 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Email Best Practices?

Skills that share tags, products or a category with Email Best Practices: API Route Patterns (bybren-llc/safe-agentic-workflow, 423 stars), Loops API (openinary/openinary, 412 stars), E2a Doctor (tokencanopy/e2a, 193 stars) and E2a Integrate (tokencanopy/e2a, 193 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Email Best Practices?

viclafouch (a GitHub user) maintains it in viclafouch/meme-studio, which has 110 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on March 31, 2026.

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