Loops Email (Loops.so)
Disambiguation: This skill is about Loops.so (email product). It is not Content Factory workflow loops under .cursor/loops/ (debugging-loop, video-generation-loop, etc.).
If the user said “loop skills” / CF loops / video loop / debug loop → stop and load @loop-skills instead (.cursor/skills/loop-skills/SKILL.md).
Do not vendor full Loops skill bodies into this repo. Install and point agents at the official packages.
Install (official)
Docs: https://loops.so/docs/skills
# CLI + every agent skill
curl -fsSL https://install.loops.so/wizard | sh
# Skills only (API, CLI, LMX, email best practices)
curl -fsSL https://install.loops.so/skills | sh
# Alternative
npx skills add loops-so/skills
After install, Cursor should see the four skills under ~/.cursor/skills/ (loops-api, loops-cli, loops-lmx, loops-email-sending-best-practices). This repo also keeps this thin router skill at .cursor/skills/loops-email/ for discovery and disambiguation.
What each Loops skill covers
| Skill |
Use for |
| API |
Campaigns, contacts, properties, lists, events, transactional email in-app |
| CLI |
Real Loops calls from terminal, IDs, smoke tests |
| LMX |
Loops markup for create/update email templates |
| Email best practices |
Deliverability, lifecycle, consent, transactional vs marketing setup |
When to use (CF / product)
| Scenario |
Guidance |
| Transactional (receipts, magic links, alerts) |
Loops transactional API/events; keep marketing tags off |
| Marketing / campaigns |
Lists + consent; never mix into transactional streams casually |
| Deliverability audit |
Use Loops email best practices skill; check SPF/DKIM/DMARC, bounce/complaint handling |
| CF pipeline notifications |
Prefer existing CF observability first; use Loops only when product email is in scope |
Secrets
- Requires a Loops account and API key
- Store keys in env / secret manager — never commit API keys,
.env, or webhook secrets
- Do not print keys in logs or PR bodies
Agent workflow
- Confirm user wants Loops.so (not
.cursor/loops/)
- Ensure install completed (wizard or skills installer)
- Follow the installed Loops skill for the task (API vs CLI vs LMX vs audit)
- Keep CF path truth: app code under
api/, pipelines/, etc. — no phantom src/
Related
1---2name: ivx-cf-loops-email3description: Installs and routes to official Loops.so agent skills (API, CLI, LMX, email best practices) for transactional and marketing email. Use when integrating Loops, sending transactional mail, auditing deliverability, or when the user mentions Loops.so — not for Content Factory `.cursor/loops/` workflow loops.4---5
6# Loops Email (Loops.so)
7
8**Disambiguation:** This skill is about **Loops.so** (email product). It is **not** Content Factory workflow loops under `.cursor/loops/` (debugging-loop, video-generation-loop, etc.).
9
10If the user said **“loop skills”** / CF loops / video loop / debug loop → **stop** and load `@loop-skills` instead (`.cursor/skills/loop-skills/SKILL.md`).
11
12Do **not** vendor full Loops skill bodies into this repo. Install and point agents at the official packages.
13
14## Install (official)
15
16Docs: https://loops.so/docs/skills
17
18```bash
19# CLI + every agent skill
20curl -fsSL https://install.loops.so/wizard | sh
21
22# Skills only (API, CLI, LMX, email best practices)
23curl -fsSL https://install.loops.so/skills | sh
24
25# Alternative
26npx skills add loops-so/skills
27```
28
29After install, Cursor should see the four skills under `~/.cursor/skills/` (`loops-api`, `loops-cli`, `loops-lmx`, `loops-email-sending-best-practices`). This repo also keeps this thin router skill at `.cursor/skills/loops-email/` for discovery and disambiguation.
30
31## What each Loops skill covers
32
33| Skill | Use for |
34|-------|---------|
35| **API** | Campaigns, contacts, properties, lists, events, transactional email in-app |
36| **CLI** | Real Loops calls from terminal, IDs, smoke tests |
37| **LMX** | Loops markup for create/update email templates |
38| **Email best practices** | Deliverability, lifecycle, consent, transactional vs marketing setup |
39
40## When to use (CF / product)
41
42| Scenario | Guidance |
43|----------|----------|
44| Transactional (receipts, magic links, alerts) | Loops transactional API/events; keep marketing tags off |
45| Marketing / campaigns | Lists + consent; never mix into transactional streams casually |
46| Deliverability audit | Use Loops **email best practices** skill; check SPF/DKIM/DMARC, bounce/complaint handling |
47| CF pipeline notifications | Prefer existing CF observability first; use Loops only when product email is in scope |
48
49## Secrets
50
51- Requires a Loops account and API key
52- Store keys in env / secret manager — **never commit** API keys, `.env`, or webhook secrets
53- Do not print keys in logs or PR bodies
54
55## Agent workflow
56
571. Confirm user wants **Loops.so** (not `.cursor/loops/`)
582. Ensure install completed (wizard or skills installer)
593. Follow the installed Loops skill for the task (API vs CLI vs LMX vs audit)
604. Keep CF path truth: app code under `api/`, `pipelines/`, etc. — no phantom `src/`
61
62## Related
63
64- Official docs: https://loops.so/docs/skills
65- CF workflow loops (different): `.cursor/loops/`
intelli-verse-x