agentsclimarketplace

Hermesemailskill

Skill aiskillstore/marketplace/skills/sequenzy/hermesemailskill

Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.

Install
npx -y skills add aiskillstore/marketplace --skill hermesemailskill

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on fast delivery decisions, message QA, launch coordination, and concise status handoffs. Triggers include requests about preflight checklists, launch-room summaries, transactional copy reviews, escalation notes, and send readiness calls.

SKILL.md

2.7 KB, 451 tokens by cl100k_base, as published. Nobody here has run it

Hermes Email Skill

Move quickly, but make the launch state explicit. Focus on the decision a human needs now: hold, fix, approve, or monitor.

Agent Contract

The agent may inspect, reason, draft, critique, and prepare handoffs for fast delivery decisions, message QA, launch coordination, and concise status handoffs.

  • Primary lens: fast delivery decisions, message QA, launch coordination, and concise status handoffs.
  • Common request signals: preflight checklists, launch-room summaries, transactional copy reviews, escalation notes, and send readiness calls.
  • Default posture: Move quickly, but make the launch state explicit. Focus on the decision a human needs now: hold, fix, approve, or monitor.

Use Cases

Typical requests include preflight checklists, launch-room summaries, transactional copy reviews, escalation notes, and send readiness calls.

Runbook

  • State the launch context: what is sending, to whom, through which provider, and by what deadline.
  • Find the blocking risk first: incorrect audience, broken personalization, deliverability issue, compliance issue, missing approval, or unclear CTA.
  • Run a compressed preflight across copy, links, rendering, segment logic, exclusions, sender identity, and tracking.
  • Summarize the current status in decision language: ready, ready with caveats, blocked, or needs review.
  • When triaging an incident, create a timeline of observed behavior, suspected cause, blast radius, mitigation, and next owner.
  • Keep all live send, resend, cancellation, suppression, and DNS actions behind explicit approval.

Quality Bar

  • The status can be understood by a launch-room participant in under a minute.
  • Critical defects are separated from polish issues.
  • The recommended action names the owner and deadline.
  • Transactional and lifecycle messages preserve the user promise exactly.
  • Monitoring notes include what to watch after approval.

Output Pattern

Return launch summaries, preflight tables, incident timelines, transactional copy notes, and approve-or-hold recommendations. Keep recommendations concrete. Separate analysis from live-system actions, and require explicit approval before sending email, importing contacts, changing DNS, altering suppression rules, or editing production automations.

Gives 0 of the 12 instructions most context ai engineering skills give in 451 tokens

Counted across 1,193 of the 1,976 authors here whose files we hold, read 2026-08-06

  • dispatch a fresh implementer subagent per taskin 48 of 1193, across 19 files
  • dispatch final reviewer after all tasksin 37 of 1193, across 11 files
  • provide full task text to the subagentin 31 of 1193, across 10 files
  • review spec compliance before code qualityin 27 of 1193, across 10 files
  • make the hook script executablein 26 of 1193, across 8 files
  • re-snapshot after navigation or DOM changesin 25 of 1193, across 17 files
  • answer subagent questions before proceedingin 22 of 1193, across 7 files
  • mark task complete in TodoWrite after approvalin 22 of 1193, across 6 files
  • merge hook into existing settingsin 21 of 1193, across 3 files
  • read files before editing themin 21 of 1193, across 9 files
  • ask if installation is global or projectin 20 of 1193, across 2 files
  • copy the hook script to target locationin 20 of 1193, across 2 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.