Stripe Projects
fossasia/eventyay
A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.
A skill your agent uses when the user wants to review, audit, improve, or plan email sending best practices.
Install Loops Email Sending Best Practices
$ npx skills add openinary/openinary --skill loops-email-sending-best-practices -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openinary/openinary loops-email-sending-best-practices --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/openinary/openinary.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/loops-email-sending-best-practices .claude/skills/loops-email-sending-best-practices && 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 "loops-email-sending-best-practices" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-email-sending-best-practices into .claude/skills/loops-email-sending-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-email-sending-best-practices", 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/openinary/openinary/tree/main/.agents/skills/loops-email-sending-best-practicesType 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 openinary/openinary --skill loops-email-sending-best-practices -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openinary/openinary loops-email-sending-best-practices --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/loops-email-sending-best-practices .agents/skills/loops-email-sending-best-practices && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "loops-email-sending-best-practices" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-email-sending-best-practices into .agents/skills/loops-email-sending-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-email-sending-best-practices", 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 openinary/openinary --skill loops-email-sending-best-practices -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openinary/openinary loops-email-sending-best-practices --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/loops-email-sending-best-practices .cursor/skills/loops-email-sending-best-practices && 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 "loops-email-sending-best-practices" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-email-sending-best-practices into .cursor/skills/loops-email-sending-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-email-sending-best-practices", 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/openinary/openinary.git --path .agents/skills/loops-email-sending-best-practices--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 openinary/openinary --skill loops-email-sending-best-practices -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openinary/openinary loops-email-sending-best-practices --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/loops-email-sending-best-practices .gemini/skills/loops-email-sending-best-practices && 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 "loops-email-sending-best-practices" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-email-sending-best-practices into .gemini/skills/loops-email-sending-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-email-sending-best-practices", 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 openinary/openinary loops-email-sending-best-practicesInstalls 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 openinary/openinary --skill loops-email-sending-best-practices -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/loops-email-sending-best-practices .github/skills/loops-email-sending-best-practices && 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 "loops-email-sending-best-practices" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-email-sending-best-practices into .github/skills/loops-email-sending-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-email-sending-best-practices", 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 openinary/openinary --skill loops-email-sending-best-practices -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openinary/openinary loops-email-sending-best-practices --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/loops-email-sending-best-practices .opencode/skills/loops-email-sending-best-practices && 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 "loops-email-sending-best-practices" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-email-sending-best-practices into .opencode/skills/loops-email-sending-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-email-sending-best-practices", 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
loops-email-sending-best-practices- GitHub stars
- 412
- Token cost
- ~943 tokens
- SKILL.md length
- 351 words
- Files
- 6 (incl. references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
A skill your agent uses when the user wants to review, audit, improve, or plan email sending best practices.
- Works in 5 steps: Identify the primary problem → Load only the relevant reference files. → Give generic email best-practice… → …
- The user wants to review
- SKILL.md covers When To Use, Working Style, Category Routing and Output Checklist
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Loops Email Sending Best Practices is an agent skill from openinary/openinary. Use this skill when the user wants to review, audit, improve, or plan email sending best practices. This includes deliverability, inbox placement, sender reputation, consent, list hygiene, subject lines, preview text, preference centers, onboarding emails, lifecycle emails, product updates, or deciding between marketing and transactional email. It works for any email stack, but when Loops is involved, use Loops behavior and docs as the source of truth. Trigger on phrases like "email deliverability", "inbox…
Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/audience-and-consent.md`, `references/content-and-design.md` and `references/deliverability.md`).
It sits in Backend & APIs, covering Transactional email. The repository describes itself as: The self-hostable alternative to Cloudinary. The licence is AGPL-3.0.
When your agent uses it
- The user wants to review
- Plan email sending best practices
- Phrases like email deliverability
- Inbox placement
Example prompts
- “email deliverability”
- “inbox placement”
- “sender reputation”
- “/loops-email-sending-best-practices”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Identify the primary problem
- Load only the relevant reference files.
- Give generic email best-practice guidance first.
- Add Loops-specific caveats, defaults, and product behavior where relevant.
- If the user is drifting into cold email or promotional use of transactional email, call that out directly and steer toward opt-in…
What it can do on your machine
Read from SKILL.md and the folder at commit 1f05325. 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
Loops Email Sending Best Practices loads about 943 tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 221 tokens; SKILL.md has 351 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.
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 openinary/openinary at commit 1f05325, republished under its AGPL-3.0 licence (© openinary). 351 words, ~943 tokens.
Download SKILL.mdSave it as
.claude/skills/loops-email-sending-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- loops-email-sending-best-practices
- description
- Use this skill when the user wants to review, audit, improve, or plan email sending best practices. This includes deliverability, inbox placement, sender reputation, consent, list hygiene, subject lines, preview text, preference centers, onboarding emails, lifecycle emails, product updates, or deciding between marketing and transactional email. It works for any email stack, but when Loops is involved, use Loops behavior and docs as the source of truth. Trigger on phrases like "email deliverability", "inbox placement", "sender reputation", "double opt-in", "unsubscribe", "subject line review", "preview text", "lifecycle emails", "onboarding emails", "product update email", "transactional vs marketing", or "email sending best practices". Do not prefer this skill for pure API implementation; use the Loops API skill for integration details.
- metadata.version
- 1.0.0
Email Sending Best Practices
This skill helps review and plan healthy email programs. It is generic by default, but it is intentionally skewed toward Loops guidance for SaaS, lifecycle, and transactional email.
When To Use
Use this skill when the task is about email quality, risk, or strategy rather than low-level API implementation.
Typical use cases:
- diagnose poor inbox placement or sender reputation
- review consent flows, double opt-in, list hygiene, or unsubscribe behavior
- improve subject lines, preview text, sender identity, personalization, or rendering
- choose between campaign, lifecycle automation, and transactional email
- plan onboarding, retention, re-engagement, dunning, or product-update email programs
- review a Loops setup for best-practice gaps
Do not default to this skill for pure implementation tasks like "send an event with the Loops API" or "wire up transactional email in Next.js". Use the loops-api skill for those.
Working Style
When this skill is active:
- Identify the primary problem:
- deliverability
- audience/consent
- content/design
- email type/program strategy
- Loops-specific operational behavior
- Load only the relevant reference files.
- Give generic email best-practice guidance first.
- Add Loops-specific caveats, defaults, and product behavior where relevant.
- If the user is drifting into cold email or promotional use of transactional email, call that out directly and steer toward opt-in lifecycle or marketing sends instead.
Show full SKILL.md (140 more words)Show less
Category Routing
- Deliverability, sender reputation, domain setup, warming, inbox placement, Postmaster, BIMI, or large-list sends:
Read
references/deliverability.md - Consent, list hygiene, double opt-in, preference centers, mailing lists, segmentation, or stale audiences:
Read
references/audience-and-consent.md - Subject lines, preview text, sender fields, personalization, styling, themes, dark mode, or template/design review:
Read
references/content-and-design.md - Campaign vs loop vs transactional, onboarding/lifecycle sequencing, product updates, or email KPI framing:
Read
references/email-types-and-program-strategy.md - Loops-specific behavior such as
addToAudience, transactional tracking differences, attachments, webhooks, or multi-domain constraints: Readreferences/loops-operational-caveats.md
Output Checklist
Aim to leave the user with:
- the most likely root cause or opportunity
- a concrete set of recommended changes
- any Loops-specific caveats that materially change the recommendation
- the metrics or signals that should be watched after the change
When relevant, explicitly separate:
- immediate fixes
- medium-term program improvements
- things that are out of scope or risky to infer from limited evidence
© openinary, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in .agents/skills/loops-email-sending-best-practices of openinary/openinary.
- SKILL.md
- references/audience-and-consent.md
- references/content-and-design.md
- references/deliverability.md
- references/email-types-and-program-strategy.md
- references/loops-operational-caveats.md
Open the folder on GitHubat commit 1f05325
Compare with similar skills
Loops Email Sending 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Loops Email Sending Best Practices this skillopeninary/openinary | 412 | — | ~943 | Automated safety check: Pass | AGPL-3.0 | |
| Stripe Projectsfossasia/eventyay | 1.7k | 5 repos | ~2k | Automated safety check: Notes | Apache-2.0 | |
| WooCommerce Email Editor Developmentwoocommerce/woocommerce | 11k | — | ~893 | Automated safety check: Pass | Custom licence | |
| Email Best Practicesviclafouch/meme-studio | 110 | 7 repos | ~787 | Automated safety check: Pass | None | |
| React Emailviclafouch/meme-studio | 110 | 2 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Pinme Emailglitternetwork/pinme | 3.8k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
WooCommerce Email Editor Development
woocommerce/woocommerce
Sets up a local environment for the WooCommerce block email editor, with a watcher, Mailpit email capture and build and test commands for its PHP and JS packages.
Email Best Practices
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…
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.
Pinme Email
glitternetwork/pinme
A skill your agent uses when a PinMe project (Worker TypeScript) needs to integrate email sending (sendemail).
Email Deliverability Audit
growthenginenowoslawski/coldoutboundskills
Diagnostic audit for a running cold email program. An agent skill from growthenginenowoslawski/coldoutboundskills.
More from openinary/openinary
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.
Loops CLI
openinary/openinary
A skill your agent uses whenever the user wants to work with the Loops CLI from the terminal.
Issue Fixer
openinary/openinary
Implement GitHub issues collaboratively in open-source repositories with explicit approval gates, incremental delivery, atomic commits, and PR-ready validation.
Related
Categories
Questions about Loops Email Sending Best Practices
What does Loops Email Sending Best Practices do?
A skill your agent uses when the user wants to review, audit, improve, or plan email sending best practices. Loops Email Sending Best Practices is an agent skill from openinary/openinary. Use this skill when the user wants to review, audit, improve, or plan email sending best practices.
When should I use Loops Email Sending Best Practices?
Loops Email Sending Best Practices fits situations like: the user wants to review; plan email sending best practices; phrases like email deliverability; inbox placement.
How do I install Loops Email Sending Best Practices in Claude Code?
Run `npx skills add openinary/openinary --skill loops-email-sending-best-practices -a claude-code`. Or copy the skill folder (.agents/skills/loops-email-sending-best-practices in openinary/openinary) into .claude/skills/loops-email-sending-best-practices in your project. Claude Code loads it when a task matches its description.
How do I install Loops Email Sending Best Practices in Codex?
Run `npx skills add openinary/openinary --skill loops-email-sending-best-practices -a codex`. Or copy the skill folder (.agents/skills/loops-email-sending-best-practices in openinary/openinary) into .agents/skills/loops-email-sending-best-practices in your project. Codex loads it when a task matches its description.
Can I use Loops Email Sending 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 openinary/openinary --skill loops-email-sending-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/loops-email-sending-best-practices, .gemini/skills/loops-email-sending-best-practices, .github/skills/loops-email-sending-best-practices and .opencode/skills/loops-email-sending-best-practices in your project.
What does Loops Email Sending Best Practices need to run?
SKILL.md names no scripts, command-line tools or credentials: Loops Email Sending Best Practices is instructions for the agent only.
Does Loops Email Sending 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 Loops Email Sending 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 Loops Email Sending Best Practices use?
Loops Email Sending Best Practices is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Loops Email Sending Best Practices use?
About 943 tokens (SKILL.md is roughly 3.8k 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 3.6k tokens, read only when the agent opens those files.
What are the alternatives to Loops Email Sending Best Practices?
Skills that share tags, products or a category with Loops Email Sending Best Practices: Stripe Projects (fossasia/eventyay, 1.7k stars), WooCommerce Email Editor Development (woocommerce/woocommerce, 11k stars), Email Best Practices (viclafouch/meme-studio, 110 stars) and React Email (viclafouch/meme-studio, 110 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Loops Email Sending Best Practices?
openinary (a GitHub organization) maintains it in openinary/openinary, which has 412 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 4, 2026.
Source: openinary/openinary on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.