Uses MailHog to capture outbound email in development and test environments through a local SMTP server, browser UI, and JSON API. It is a practical fit for debugging transactional mail, verifying templates, and testing delivery behavior without sending messages to real recipients.
Scanned 6/8/2026
Install to Claude Code
npx -y skills add agentskillexchange/skills --skill mailhog-smtp-testing-server-with-web-ui-and-api --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Mailhog Smtp Testing Server With Web Ui And Api?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/agentskillexchange-mailhog-smtp-testing-server-with-web-ui-and-api)More formats (shields.io, HTML) on the badges page.
---
name: "MailHog SMTP Testing Server with Web UI and API"
slug: "mailhog-smtp-testing-server-with-web-ui-and-api"
description: "Uses MailHog to capture outbound email in development and test environments through a local SMTP server, browser UI, and JSON API. It is a practical fit for debugging transactional mail, verifying templates, and testing delivery behavior without sending messages to real recipients."
github_stars: 15892
verification: "security_reviewed"
source: "https://github.com/mailhog/MailHog"
author: "MailHog"
publisher_type: "open_source_collective"
category: "Calendar, Email & Productivity"
framework: "Multi-Framework"
tool_ecosystem:
github_repo: "mailhog/mailhog"
github_stars: 15892
---
# MailHog SMTP Testing Server with Web UI and API
Uses MailHog to capture outbound email in development and test environments through a local SMTP server, browser UI, and JSON API. It is a practical fit for debugging transactional mail, verifying templates, and testing delivery behavior without sending messages to real recipients.
## Prerequisites
Docker, Homebrew, or Go
## Installation
Use the upstream install or setup path that matches your environment:
- brew update && brew install mailhog
- go install github.com/mailhog/MailHog@latest
Requirements and caveats from upstream:
- #### Docker
- [Run it from Docker Hub](https://registry.hub.docker.com/r/mailhog/mailhog/) or using the provided [Dockerfile](Dockerfile)
- Requires Go 1.4+ to build.
Basic usage or getting-started notes:
- Download and run MailHog
- #### Manual installation
- [Download the latest release for your platform](/docs/RELEASES.md). Then
- Source: https://github.com/mailhog/MailHog
- Extracted from upstream docs: https://raw.githubusercontent.com/mailhog/MailHog/HEAD/README.md
## Documentation
- https://github.com/mailhog/MailHog
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/mailhog-smtp-testing-server-with-web-ui-and-api/)
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.