Agent skill

Email Blast

Send one-off email blasts to Gumroad creators directly via production console, no PR or deploy needed.

MITAuto-check passedDatabases

Install Email Blast

skills CLI

$ npx skills add antiwork/gumroad --skill email-blast -a claude-code

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

GitHub CLI

$ gh skill install antiwork/gumroad email-blast --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/antiwork/gumroad.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/email-blast .claude/skills/email-blast && 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/

Paste into Claude Code

Install the "email-blast" agent skill from https://github.com/antiwork/gumroad/tree/main/.agents/skills/email-blast into .claude/skills/email-blast/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-blast", 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

$skill-installer install https://github.com/antiwork/gumroad/tree/main/.agents/skills/email-blast

Type 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.

skills CLI

$ npx skills add antiwork/gumroad --skill email-blast -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install antiwork/gumroad email-blast --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/antiwork/gumroad.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/email-blast .agents/skills/email-blast && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "email-blast" agent skill from https://github.com/antiwork/gumroad/tree/main/.agents/skills/email-blast into .agents/skills/email-blast/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-blast", 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.

skills CLI

$ npx skills add antiwork/gumroad --skill email-blast -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install antiwork/gumroad email-blast --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/antiwork/gumroad.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/email-blast .cursor/skills/email-blast && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "email-blast" agent skill from https://github.com/antiwork/gumroad/tree/main/.agents/skills/email-blast into .cursor/skills/email-blast/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-blast", 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

$ gemini skills install https://github.com/antiwork/gumroad.git --path .agents/skills/email-blast

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add antiwork/gumroad --skill email-blast -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install antiwork/gumroad email-blast --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/antiwork/gumroad.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/email-blast .gemini/skills/email-blast && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "email-blast" agent skill from https://github.com/antiwork/gumroad/tree/main/.agents/skills/email-blast into .gemini/skills/email-blast/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-blast", 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.

GitHub CLI

$ gh skill install antiwork/gumroad email-blast

Installs 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).

skills CLI

$ npx skills add antiwork/gumroad --skill email-blast -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/antiwork/gumroad.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/email-blast .github/skills/email-blast && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "email-blast" agent skill from https://github.com/antiwork/gumroad/tree/main/.agents/skills/email-blast into .github/skills/email-blast/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-blast", 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.

skills CLI

$ npx skills add antiwork/gumroad --skill email-blast -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install antiwork/gumroad email-blast --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/antiwork/gumroad.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/email-blast .opencode/skills/email-blast && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "email-blast" agent skill from https://github.com/antiwork/gumroad/tree/main/.agents/skills/email-blast into .opencode/skills/email-blast/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "email-blast", 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.

Facts

Skill name: email-blast
GitHub stars: 9.8k
Token cost: ~1.4k tokens
SKILL.md length: 388 words
Files: 1
Skills in repo: 6
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Send one-off email blasts to Gumroad creators directly via production console, no PR or deploy needed.

Works in 6 steps: Clarify the request → Draft the email → Count recipients via Metabase → …
Asked to email creators
SKILL.md covers Prerequisites, Workflow, Safety Rules and Key References
Calls ruby, curl and python3; reaches gumroad.metabaseapp.com; needs METABASE_KEY

What it does

Email Blast is an agent skill from antiwork/gumroad. Send one-off email blasts to Gumroad creators directly via production console, no PR or deploy needed. Handles drafting, recipient query, count validation via Metabase, dry-run preview, and execution. Use when asked to "email creators", "send an announcement", "blast sellers", "notify users", or any request to send emails to Gumroad creators at scale.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases. It works with Redis and MySQL. The licence is MIT.

When your agent uses it

Asked to email creators
Send an announcement
Any request to send emails to Gumroad creators at scale

Example prompts

“email creators”
“send an announcement”
“blast sellers”
“/email-blast”

Requirements

Python 3
A credential in METABASE_KEY

Workflow steps

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

Clarify the request
Draft the email
Count recipients via Metabase
Dry run (preview)
Execute the blast
Resume / Reset

What it can do on your machine

Read from SKILL.md and the folder at commit bffaa9b. 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
Shell commands in SKILL.md call:
- ruby
- curl
- python3
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:
- gumroad.metabaseapp.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- METABASE_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Email Blast loads about 1.4k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 388 words of instructions outside code blocks.

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

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

The full file from antiwork/gumroad at commit bffaa9b, republished under its MIT licence (© antiwork). 388 words, ~1,365 tokens.

Download SKILL.mdSave it as .claude/skills/email-blast/SKILL.md (or your agent's skills folder).

name: email-blast
description: Send one-off email blasts to Gumroad creators directly via production console, no PR or deploy needed. Handles drafting, recipient query, count validation via Metabase, dry-run preview, and execution. Use when asked to "email creators", "send an announcement", "blast sellers", "notify users", or any request to send emails to Gumroad creators at scale.

Email Blast

Send one-off emails to Gumroad creators by executing Ruby inline against the production console. No PR, no deploy, no service class needed.

Prerequisites

Production console access configured via the gumroad-prod-console skill (see its SKILL.md for setup)
Metabase API key (in 1Password: "Metabase (Gumroad)" → "API Key")

All production Ruby execution in this skill goes through .claude/skills/gumroad-prod-console/scripts/prod_query.sh. That script targets the read replica for MySQL, which is sufficient here — User.alive.not_suspended...find_each is a read, and deliver_later + $redis.set hit Redis, not MySQL. Do not add any MySQL-write operations to blast scripts.

Workflow

1. Clarify the request

From the human's request, extract:

Who — recipient criteria (e.g. "all active creators", "creators who earned > $1000")
What — the message to send (subject + body)
Reply-to — default support@gumroad.com

2. Draft the email

Write a subject and HTML body:

Simple HTML only:  tags, <a> links
Sign off: — The Gumroad Team
No <ul>/<li> (renders poorly). Use • Item for bullets.
Keep it short and direct
Always use from: "Gumroad <gumroad@creators.gumroad.com>" and sender_domain: :creators
The OneOffMailer template renders the subject as an <h2> heading at the top automatically

Present the draft for human approval before proceeding.

3. Count recipients via Metabase

Build a SQL query and validate the count:

bash

METABASE_KEY=$(op item get "Metabase (Gumroad)" --vault Gumclaw --fields "API Key" --reveal)
curl -s -X POST "https://gumroad.metabaseapp.com/api/dataset" \
  -H "Content-Type: application/json" \
  -H "X-Metabase-Session: $METABASE_KEY" \
  -d '{
    "database": 2,
    "type": "native",
    "native": { "query": "SELECT COUNT(*) FROM users WHERE deleted_at IS NULL AND is_suspended = 0 AND ..." }
  }' | python3 -c "import json,sys; print(json.load(sys.stdin)['data']['rows'][0][0])"

Always filter: deleted_at IS NULL AND is_suspended = 0 (alive, not suspended).

Show the count to the human before executing.

4. Dry run (preview)

Generate a script that sends to just 1-2 test recipients first. Run via prod_query.sh:

bash

cat << 'RUBY' | .claude/skills/gumroad-prod-console/scripts/prod_query.sh
test_user = User.find_by(email: "sahil@gumroad.com")
OneOffMailer.email(
  email: test_user.form_email,
  from: "Gumroad <gumroad@creators.gumroad.com>",
  subject: "SUBJECT HERE",
  body: <<~HTML,
    <p>Body here.</p>
    <p>— The Gumroad Team</p>
  HTML
  reply_to: "support@gumroad.com",
  sender_domain: :creators
).deliver_later(queue: "low")
puts "Test email enqueued to #{test_user.form_email}"
RUBY

Wait for human confirmation that the test email looks good before proceeding.

Show full SKILL.md (143 more words)Show less

5. Execute the blast

Generate the full script with Redis checkpointing for resumability:

bash

cat << 'RUBY' | .claude/skills/gumroad-prod-console/scripts/prod_query.sh
redis_key = "email_blast_DESCRIPTIVE_KEY_last_user_id"
last_processed_id = $redis.get(redis_key).to_i
count = 0

User.alive.not_suspended.where("id > ?", last_processed_id).where(CRITERIA).find_each(batch_size: 500) do |user|
  next if user.form_email.blank?

  OneOffMailer.email(
    email: user.form_email,
    from: "Gumroad <gumroad@creators.gumroad.com>",
    subject: "SUBJECT",
    body: <<~HTML,
      <p>Body here.</p>
      <p>— The Gumroad Team</p>
    HTML
    reply_to: "support@gumroad.com",
    sender_domain: :creators
  ).deliver_later(queue: "low")

  $redis.set(redis_key, user.id)
  count += 1
  Rails.logger.info "Enqueued email for user #{user.id} (#{count} total)" if count % 100 == 0
end

puts "Done. Enqueued #{count} emails."
RUBY

6. Resume / Reset

Resume (if interrupted): Just re-run the same script. Redis checkpoint skips already-processed users.

Reset (to re-send): Delete the Redis key first:

bash

echo '$redis.del("email_blast_DESCRIPTIVE_KEY_last_user_id")' | .claude/skills/gumroad-prod-console/scripts/prod_query.sh

Safety Rules

Always get human approval on subject, body, and recipient count before executing
Always send a dry-run to a test recipient first (sahil@gumroad.com or the requester)
Always use Redis checkpointing — blasts can be interrupted and resumed
Always use deliver_later(queue: "low") — never deliver_now (would block the runner)
Always filter alive.not_suspended and form_email.present?
Never send from hi@customers.gumroad.com — that's for transactional emails only
Log progress so you can verify emails are being enqueued

Key References

OneOffMailer: app/mailers/one_off_mailer.rb
Example service: app/services/onetime/notify_sellers_about_legacy_fee_migration.rb
form_email: The user's preferred contact email (may differ from login email)
Sender domains: :creators → creators.gumroad.com, default → customers.gumroad.com

Files

Just SKILL.md in .agents/skills/email-blast of antiwork/gumroad.

Open the folder on GitHubat commit bffaa9b

Compare with similar skills

Email Blast 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 Blast compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Email Blast this skillantiwork/gumroad	9.8k	—	~1.4k	Automated safety check: Pass	MIT	today
Tgf Server Devthkhxm/tgf	128	—	~1.3k	Automated safety check: Notes	MIT	2 mo ago
Cache Debugzhyese/grid-qa	145	—	~646	Automated safety check: Pass	Custom licence	5 days ago
Resume Backend Project OptimizerLAIJiangFeng/resume-builder	248	—	~868	Automated safety check: Pass	None	1 mo ago
Cloudrun DevelopmentTencentCloudBase/CloudBase-AI-Toolkit	1.1k	1 repos	~7.2k	Automated safety check: Pass	MIT	today
Leaderboard SystemOpenLitterMap/openlittermap-web	134	—	~2k	Automated safety check: Pass	GPL-3.0	24 days ago

Similar skills

Tgf Server Dev
thkhxm/tgf
基于 tgf v2（github.com/thkhxm/tgf/v2）用确定性的 tgfctl 工作流创建、验证和维护 Go 游戏服务器项目。
128 GitHub stars~1.3k tokensUpdated 2 mo ago
DatabasesAuto-check: notes
Cache Debug
zhyese/grid-qa
排查问答缓存问题（不命中/脏缓存/黑名单误拦/置信度过滤/多轮不缓存）时使用。覆盖三级缓存(Redis/MySQL/Semantic)+黑名单+置信度规则。
145 GitHub stars~646 tokensUpdated 5 days ago
DatabasesAuto-check passed
Resume Backend Project Optimizer
LAIJiangFeng/resume-builder
将中文后端项目经历改写为高质量、可面试追问、强数据化的简历要点。适用于用户提供“项目经历/主要工作/职责描述”后，要求按统一模板输出“负责xxx功能 + 关键技术细节组合 + 解决问题 + 数据化结果”的场景；适用于 Java 后端求职、简历优化、面试前项目复盘，且需要对齐面试高频考点（Java 集合与并发、MySQL、Redis、Spring、消息队列、系统设计等）时使用。
248 GitHub stars~868 tokensUpdated 1 mo ago
DatabasesAuto-check passed
Cloudrun Development
TencentCloudBase/CloudBase-AI-Toolkit
CloudBase Run backend development rules (Function mode/Container mode).
1.1k GitHub starsUsed in 1 repo~7.2k tokens
DatabasesAuto-check passed
Leaderboard System
OpenLitterMap/openlittermap-web
LeaderboardController, Redis sorted sets for all-time XP rankings, per-user metrics rows for time-filtered rankings, rewardXpToAdmin, and leaderboard privacy.
134 GitHub stars~2k tokensUpdated 24 days ago
DatabasesAuto-check passed
Metrics Pipeline
OpenLitterMap/openlittermap-web
MetricsService, RedisMetricsCollector, ProcessPhotoMetrics, metrics table, Redis stats, leaderboards, XP processing, and photo processing state (processedat/fp/tags/xp).
134 GitHub stars~1.8k tokensUpdated 24 days ago
DatabasesAuto-check passed

Questions about Email Blast

What does Email Blast do?

Send one-off email blasts to Gumroad creators directly via production console, no PR or deploy needed. Email Blast is an agent skill from antiwork/gumroad. Send one-off email blasts to Gumroad creators directly via production console, no PR or deploy needed.

When should I use Email Blast?

Email Blast fits situations like: asked to email creators; send an announcement; any request to send emails to Gumroad creators at scale.

How do I install Email Blast in Claude Code?

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

How do I install Email Blast in Codex?

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

Can I use Email Blast 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 antiwork/gumroad --skill email-blast -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-blast, .gemini/skills/email-blast, .github/skills/email-blast and .opencode/skills/email-blast in your project.

What does Email Blast need to run?

Going by SKILL.md and its folder, Email Blast needs the command-line tools its instructions call (ruby, curl and python3) and credentials named METABASE_KEY. Our summary lists: Python 3; A credential in METABASE_KEY.

Does Email Blast access the network?

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

Is Email Blast 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 Blast use?

Email Blast 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 Blast use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Blast?

Skills that share tags, products or a category with Email Blast: Tgf Server Dev (thkhxm/tgf, 128 stars), Cache Debug (zhyese/grid-qa, 145 stars), Resume Backend Project Optimizer (LAIJiangFeng/resume-builder, 248 stars) and Cloudrun Development (TencentCloudBase/CloudBase-AI-Toolkit, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Email Blast?

antiwork (a GitHub organization) maintains it in antiwork/gumroad, which has 9,831 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.

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

Install Email Blast

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Email Blast

Prerequisites

Workflow

1. Clarify the request

2. Draft the email

3. Count recipients via Metabase

4. Dry run (preview)

5. Execute the blast

6. Resume / Reset

Safety Rules

Key References

Files

Compare with similar skills

Similar skills

More from antiwork/gumroad

Related

Questions about Email Blast