loops-cli

Estrelas11

Forks0

Atualizado7 de julho de 2026 às 14:57

Use this skill whenever the user wants to work with the Loops CLI from the terminal. This includes installing or updating the CLI, authenticating, storing and selecting API keys, validating credentials, and running commands for contacts, contact properties, lists, events, transactional email, campaigns, email messages, themes, components, and uploads. Trigger on phrases like "Loops CLI", "loops auth login", "loops campaigns create", "loops uploads create", "loops email-messages update", "loops themes list", "loops components get", "loops contacts create", "loops events send", "loops transactional send", "loops api-key", "loops agent-context", "brew install loops-so/tap/loops", or any time the user wants to use Loops from the shell instead of application code.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

loops-so

loops-so/skills

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	loops-cli
description	Use this skill whenever the user wants to work with the Loops CLI from the terminal. This includes installing or updating the CLI, authenticating, storing and selecting API keys, validating credentials, and running commands for contacts, contact properties, lists, events, transactional email, campaigns, email messages, themes, components, and uploads. Trigger on phrases like "Loops CLI", "loops auth login", "loops campaigns create", "loops uploads create", "loops email-messages update", "loops themes list", "loops components get", "loops contacts create", "loops events send", "loops transactional send", "loops api-key", "loops agent-context", "brew install loops-so/tap/loops", or any time the user wants to use Loops from the shell instead of application code.
metadata	{"version":"1.1.1"}

Loops CLI Skill

This skill helps with Loops terminal workflows. Use it for installation, auth and configuration, command selection, and shell-first operational tasks.

When To Use

Use this skill when the user needs to:

install, update, or troubleshoot the Loops CLI
authenticate with Loops from the terminal
manage stored team keys or switch between them
run one-off contact, list, event, or transactional-email commands
create draft campaigns, update email-message content, and upload images from the shell
list/get themes and reusable components for LMX
inspect CLI output in text or JSON locally

This skill is for command-line usage, not application integrations or email-strategy review.

Working Style

When this skill is active:

Prefer loops agent-context for exact flags and the latest command shape.
Prefer the CLI for shell workflows, one-off operational tasks, credential validation, and quick troubleshooting.
Use --output json when the result needs to feed another tool or script.
Use named stored keys plus --team when the user works across multiple Loops teams.
Avoid printing secrets. Prefer keyring-backed auth or environment variables over hardcoded API keys.
If the task becomes application-code integration or exact HTTP payload design, use the separate loops-api skill.

Official references:

CLI docs: https://loops.so/docs/cli
CLI repo: https://github.com/loops-so/cli
CLI README: https://github.com/loops-so/cli/blob/main/README.md

Category Routing

Installation, auth flows, config resolution, global flags, and common Loops CLI workflows: Read references/cli.md
Campaigns, email messages, themes, components, revision handling, LMX file flags, and uploads: Read references/cli.md. For LMX markup itself, also use the loops-lmx skill.

If the task becomes application-code integration or exact HTTP payload design beyond the CLI, use the loops-api skill.

Output Checklist

Aim to leave the user with:

the right command or install path for the task
any auth or team-selection caveats that affect behavior
safe handling of credentials
the next validation step, such as loops --help, loops auth status, loops api-key, or loops agent-context

Mais deste repositório

mesmo repositório

loops-api

loops-so/skills

Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. This includes the Loops HTTP API and official SDKs for server-side contact, contact-property, mailing-list, event, API-key-validation, transactional-email, content editing (campaigns, campaign groups, transactional groups, audience segments, email messages, themes, and components), and workflow graph/node inspection and mutation. Trigger on phrases like "Loops API", "Loops SDK", "create a campaign via API", "update email message LMX", "create a workflow via API", "add a workflow node", "send a Loops event from my app", "add a contact to Loops in a webhook", "send a transactional email from backend code", or any time the user wants to integrate Loops into their app, backend, webhook, or automation. Do not trigger for CLI or shell-only requests.

2026-07-2311

loops-email-sending-best-practices

loops-so/skills

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.

2026-07-2211

loops-lmx

loops-so/skills

Use this skill whenever LMX is used, produced, reviewed, migrated, or modified. This includes composing campaigns, loops, lifecycle emails, or email-message bodies for the Loops editor or Content API. LMX (Loops Markup Language) is the format used for Loops email content. Trigger on phrases like "create a campaign", "generate an email", "write a welcome email", "draft a lifecycle email", "build an email template", "create an onboarding email", "copy this into LMX", "migrate this email", "convert this email to LMX", "design a new Loops email", "use imagegen for a Loops email", "use gpt-image for an LMX reference", "visual reference for a Loops email", "LMX", "Loops email", or any request to produce, copy, migrate, convert, review, or modify email body content intended for Loops. For net-new emails or major visual redesigns, follow this skill's Net-New Email Design Flow before generating or sourcing new visual assets. Source copy, existing HTML, MJML, Markdown, screenshots, and migration instructions do not byp

2026-07-2211

name	loops-cli
description	Use this skill whenever the user wants to work with the Loops CLI from the terminal. This includes installing or updating the CLI, authenticating, storing and selecting API keys, validating credentials, and running commands for contacts, contact properties, lists, events, transactional email, campaigns, email messages, themes, components, and uploads. Trigger on phrases like "Loops CLI", "loops auth login", "loops campaigns create", "loops uploads create", "loops email-messages update", "loops themes list", "loops components get", "loops contacts create", "loops events send", "loops transactional send", "loops api-key", "loops agent-context", "brew install loops-so/tap/loops", or any time the user wants to use Loops from the shell instead of application code.
metadata	{"version":"1.1.1"}

Loops CLI Skill

This skill helps with Loops terminal workflows. Use it for installation, auth and configuration, command selection, and shell-first operational tasks.

When To Use

Use this skill when the user needs to:

install, update, or troubleshoot the Loops CLI
authenticate with Loops from the terminal
manage stored team keys or switch between them
run one-off contact, list, event, or transactional-email commands
create draft campaigns, update email-message content, and upload images from the shell
list/get themes and reusable components for LMX
inspect CLI output in text or JSON locally

This skill is for command-line usage, not application integrations or email-strategy review.

Working Style

When this skill is active:

Prefer loops agent-context for exact flags and the latest command shape.
Prefer the CLI for shell workflows, one-off operational tasks, credential validation, and quick troubleshooting.
Use --output json when the result needs to feed another tool or script.
Use named stored keys plus --team when the user works across multiple Loops teams.
Avoid printing secrets. Prefer keyring-backed auth or environment variables over hardcoded API keys.
If the task becomes application-code integration or exact HTTP payload design, use the separate loops-api skill.

Official references:

CLI docs: https://loops.so/docs/cli
CLI repo: https://github.com/loops-so/cli
CLI README: https://github.com/loops-so/cli/blob/main/README.md

Category Routing

Installation, auth flows, config resolution, global flags, and common Loops CLI workflows: Read references/cli.md
Campaigns, email messages, themes, components, revision handling, LMX file flags, and uploads: Read references/cli.md. For LMX markup itself, also use the loops-lmx skill.

If the task becomes application-code integration or exact HTTP payload design beyond the CLI, use the loops-api skill.

Output Checklist

Aim to leave the user with:

the right command or install path for the task
any auth or team-selection caveats that affect behavior
safe handling of credentials
the next validation step, such as loops --help, loops auth status, loops api-key, or loops agent-context