sinch-mailgun-inspect

Validate email HTML and assets with Mailgun Inspect pre-send QA.

9|4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/sinch/skills --skill sinch-mailgun-inspect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sinch-mailgun-inspect
Source: https://github.com/sinch/skills/tree/main/skills/sinch-mailgun-inspect
Command: npx skills add https://github.com/sinch/skills --skill sinch-mailgun-inspect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many email campaigns fail or underperform because of broken links, inaccessible HTML, missing or oversized images, or rendering issues across clients; this Skill centralizes pre-send QA to catch those problems before they reach recipients.

Core Features & Use Cases

  • Accessibility testing: Run Mailgun Inspect accessibility checks to detect WCAG issues and missing alt text.
  • Link and image validation: Validate URL lists, HTML-embedded links, and uploaded images to find broken resources or insecure URLs.
  • Code analysis and previews: Analyze HTML/CSS compatibility and generate client previews (V2 content-checking can run multiple checks in one request).
  • CI/CD gating and optimization: Automate create-then-poll workflows to gate builds, fail on critical issues, and optionally optimize images after validation.
  • Operational guidance: Region-aware base URLs (US/EU), async polling patterns, and secrets handling for safe automation.

Quick Start

Run a full Mailgun Inspect pre-send QA on my email HTML to check accessibility, links, images, code analysis, and generate previews while polling until all tests are completed.

Frequently Asked Questions about sinch-mailgun-inspect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate email HTML for accessibility and broken links before sending?

Email HTML validation detects WCAG issues, missing alt text, broken links, and insecure URLs before sending. It analyzes HTML/CSS compatibility and generates client previews by applying pre-send QA checks to catch rendering issues across email clients.

What is the best way to automate email QA checks in a CI/CD pipeline?

Automating email QA in a CI/CD pipeline uses create-then-poll asynchronous jobs to gate builds. It initiates validation jobs, polls until completion, and fails builds when critical accessibility, link, or image issues are detected, preventing broken emails from deploying.

Does pre-send email testing support uploaded files and URL lists?

Pre-send email testing supports HTML strings, URL lists, and file uploads as input. It validates embedded links and uploaded images to find broken resources, applying region-aware base URLs to route requests correctly for asynchronous polling workflows.

How does asynchronous polling work for email rendering previews?

Asynchronous polling for email previews creates a validation job, then repeatedly checks its status until Completed or Failed. This pattern handles long-running accessibility, code analysis, and image validation tasks, returning rendering previews and issue reports when finished.

Why do email campaigns fail or underperform despite passing basic HTML checks?

Email campaigns underperform due to inaccessible HTML, broken links, missing or oversized images, and rendering issues across clients. Pre-send QA centralizes accessibility testing, link validation, and image checks to catch these problems before recipients see them.

Do I need Mailgun API credentials to run email accessibility and image validation?

Mailgun API credentials are required to run email accessibility and image validation. The workflow uses region-aware base URLs for US and EU endpoints, handling secrets safely while submitting HTML or file uploads for asynchronous content checking and preview generation.