Skills hermesemailskill

📦

hermesemailskill

Name: hermesemailskill
Author: Sequenzy

Content revision r1 Safe

Coordinate Email Launch Readiness

Email launches can fail when teams miss audience, copy, link, or approval risks. This skill helps Claude, Codex, and Claude Code produce fast QA checks, launch summaries, and approval-ready handoffs.

Supports: Claude Codex Code(CC)

📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "hermesemailskill" from https://skillstore.io/skills/sequenzy-hermesemailskill.md and its manifest at https://skillstore.io/api/skills/sequenzy-hermesemailskill/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sequenzy-hermesemailskill.md Signed manifest GET /api/skills/sequenzy-hermesemailskill/manifest Signed lockfile GET /api/skills/sequenzy-hermesemailskill/lockfile

Test it

Using "hermesemailskill". Review a campaign brief with final copy, test-send links, audience count, exclusions, and launch deadline.

Expected outcome:

A readiness summary that marks the send as ready with caveats, lists two link checks, confirms exclusions, and names the approval owner.

Using "hermesemailskill". Audit a password reset email before deployment.

Expected outcome:

A copy review that compares the subject, CTA, fallback text, footer, and user promise, then flags missing merge-tag evidence.

Using "hermesemailskill". Summarize notes from a delayed promotional send incident.

Expected outcome:

An incident timeline with observed behavior, likely cause, affected audience, current mitigation, next owner, and monitoring window.

Security Audit

Safe

v3 • 7/6/2026 Open versioned report

Static analysis reported no suspicious patterns across the three prompt-only files. Manual review found no prompt injection attempts, data exfiltration intent, executable code, network behavior, or requests to bypass approval gates.

Files scanned

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sequenzy-hermesemailskill/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sequenzy-hermesemailskill/security.svg)](https://skillstore.io/skills/sequenzy-hermesemailskill?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sequenzy-hermesemailskill?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sequenzy-hermesemailskill/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sequenzy-hermesemailskill.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

Sequenzy. (2026). hermesemailskill security audit report (audit version 3) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sequenzy-hermesemailskill/audits/3

BibTeX citation

@techreport{sequenzy-sequenzy-hermesemailskill-2026,
  author = {Sequenzy},
  title = {hermesemailskill security audit report (audit version 3)},
  institution = {Skillstore},
  year = {2026},
  number = {3},
  url = {https://skillstore.io/skills/sequenzy-hermesemailskill/audits/3},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "hermesemailskill security audit report (audit version 3)"
version: "unspecified"
type: report
authors:
  - name: "Sequenzy"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sequenzy-hermesemailskill/audits/3"
identifiers:
  - type: other
    value: "skillstore:sequenzy-hermesemailskill:audit:3"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Preflight a Marketing Send

Check audience, exclusions, copy, links, sender identity, tracking, and approval status before launch.

Review Transactional Copy

Compare the message promise, subject line, CTA, merge tags, and fallback values before deployment.

Summarize an Email Incident

Create a concise timeline, blast radius, mitigation status, next owner, and monitoring plan.

Try These Prompts

Basic Send Readiness Check

Use $hermesemailskill to review this email send brief. Tell me if it is ready, blocked, or needs review. Include copy, links, audience, exclusions, sender identity, tracking, and approval checks.

Transactional Message QA

Use $hermesemailskill to audit this transactional email. Check whether the subject, CTA, body copy, merge tags, fallback values, footer, and user promise are consistent.

Launch Room Status Handoff

Use $hermesemailskill to turn these notes into a launch-room handoff. Separate blockers, caveats, owner actions, approval status, deadline, and post-send monitoring.

Incident Timeline and Mitigation Plan

Use $hermesemailskill to analyze this email incident evidence. Build a timeline, identify suspected causes, estimate blast radius, name mitigation options, and list approval gates before live changes.

Best Practices

Provide the full send brief, audience rules, exclusions, test links, deadline, and approval chain.
Ask for a decision summary that separates blockers from polish issues.
Keep live sends, imports, DNS changes, and suppression edits behind explicit human approval.

Avoid

Do not ask the skill to approve a live send without test evidence and an approval owner.
Do not treat draft copy feedback as compliance, legal, or deliverability clearance.
Do not combine incident diagnosis with live production changes in one unapproved step.