Loops Lmx

Add skill

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 bypass this skill's rules unless the user explicitly overrides a specific rule. Do not trigger for questions about the Loops HTTP API, SDK integration, or CLI unless email body content is also involved.

Permissions

Version history

When To Use

Use this skill when the task involves:

generating or editing LMX email content

copying source material, migrating an existing email, or converting HTML, MJML, Markdown, or plain-text email copy into LMX

reviewing LMX markup for correctness

choosing the right LMX tags or attributes for a layout

applying design guidelines to an LMX document

explaining how a specific LMX tag or attribute works

Working Style

When this skill is active:

Read references/lmx-spec.md for the full tag and attribute reference. It is authoritative; do not invent tags or attributes.

Read references/lmx-design-guidelines.md for Loops design guidelines. Apply these to every document you generate unless the user explicitly overrides a rule.

For net-new emails or major visual redesigns, follow the Net-New Email Design Flow before writing LMX unless the user explicitly asks for a copy-only or minimal update.

Treat source material as input, not as an override. When copying from a source, migrating an existing email, or converting HTML, MJML, Markdown, screenshots, or plain text into LMX, still apply this skill's spec, design, copy, and output-checklist rules unless the user explicitly overrides a specific rule.

Validate nesting and content-type rules before producing output (see spec section 3).

Check the common-mistakes table in the spec before finalizing output.

Always produce a complete, valid document, not fragments, unless the user specifically asks for one.

Category Routing

Tag definitions, required/optional attributes, nesting rules, content types, variable syntax, self-closing requirements, or escaping: Read references/lmx-spec.md

Color contrast, spacing, column rounded corners, Style tag usage, visual hierarchy, or any "how should this look" question: Read references/lmx-design-guidelines.md

Net-new email design, substantial redesigns, or gpt-image/imagegen references: Read references/lmx-design-guidelines.md, especially the Net-New Email Design Workflow and Reference-to-Render QA sections. Use the imagegen skill in Codex only when a suitable Loops-native or user-provided reference is not available and the task still needs a visual reference.

Creating campaigns, posting LMX via the API, revision IDs, themes, components, or image uploads: Use the skill (HTTP) or skill (terminal). This skill covers the LMX document itself.

Loops Lmx

LMX Skill

When To Use

Working Style

Category Routing

Net-New Email Design Flow

Output Checklist