m26-resend-email

Installation
SKILL.md

M26 Resend email automation

Assume the upstream layout scripts/emails/ exists (or will be materialized). All procedures below use cd into scripts/emails, a venv, and python <script>.py unless the user is in a full monorepo from the repository root, where python -m scripts.emails.<name> is also valid.

First: materialize scripts/emails

If the folder is missing, obtain a sparse checkout of only that path (not the whole monorepo working tree). Full step-by-step commands, Windows junctions, and Linux symlinks live in scripts/emails/MINIMAL_CLONE.md in the upstream repo.

Minimum idea:

  1. Clone with --filter=blob:none --sparse, then git sparse-checkout init --no-cone and git sparse-checkout set --no-cone '/scripts/emails/'.
  2. cd scripts/emails, create .venv, pip install -r requirements.txt, copy .env from .env.example (or from another machine — see below).
  3. Updates: git pull from the sparse clone root.

New machine / copied workspace: Copy .env and every file paths inside it (service account JSON, Gmail OAuth client JSON, gmail_token.json, etc.), then edit paths so they match the new filesystem. Copying .env alone often breaks because paths still point at the old PC. Agents should ask for missing keys or files before sending. Full checklist: references/required-credentials.md.

Do not run python scripts/emails/foo.py from the monorepo root (path through scripts/emails/). Either cd scripts/emails and run python foo.py, or from full repo use python -m scripts.emails.foo.

Secrets stay in .env or the environment — never commit API keys, webhook secrets, or Gmail token files.

Related skills

More from jarmen423/skills

Installs
8
GitHub Stars
2
First Seen
Mar 21, 2026