Skills emailautomationskill

📦

emailautomationskill

Name: emailautomationskill
Author: Sequenzy

Content revision r1 Safe

Audit Email Automation Workflows

Email automations can create duplicate sends, stale journeys, or consent mistakes. This skill helps agents review triggers, QA plans, and approval gates.

Supports: Claude Codex Code(CC)

📊 74 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 "emailautomationskill" from https://skillstore.io/skills/sequenzy-emailautomationskill.md and its manifest at https://skillstore.io/api/skills/sequenzy-emailautomationskill/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-emailautomationskill.md Signed manifest GET /api/skills/sequenzy-emailautomationskill/manifest Signed lockfile GET /api/skills/sequenzy-emailautomationskill/lockfile

Test it

Using "emailautomationskill". Audit an abandoned-cart journey before launch.

Expected outcome:

Journey contract with trigger, eligibility, waits, exits, suppression checks, and success metric.
QA checklist covering test contacts, branch coverage, delayed events, and rollback ownership.
Approval gate for activation, suppression edits, and any production automation change.

Using "emailautomationskill". Review a stale reactivation flow.

Expected outcome:

Risk summary for stale contacts, missing exits, weak event freshness, and frequency pressure.
Recommended cleanup plan with owner, approval path, and recovery metric.
Evidence list showing which supplied fields or metrics support each recommendation.

Using "emailautomationskill". Plan governance for a lifecycle automation library.

Expected outcome:

Naming rules, owner fields, change log expectations, and scheduled review cadence.
Risk gates for drafts, segment recommendations, imports, suppression edits, and live changes.
Handoff notes that separate analysis from actions requiring approval.

Security Audit

Safe

v3 • 7/6/2026 Open versioned report

Static analysis reported no suspicious patterns across 3 scanned files. Manual context review found prompt-only guidance for email automation governance and approval gates. No semantic security findings were identified.

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-emailautomationskill/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sequenzy-emailautomationskill.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). emailautomationskill security audit report (audit version 3) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sequenzy-emailautomationskill/audits/3

BibTeX citation

@techreport{sequenzy-sequenzy-emailautomationskill-2026,
  author = {Sequenzy},
  title = {emailautomationskill security audit report (audit version 3)},
  institution = {Skillstore},
  year = {2026},
  number = {3},
  url = {https://skillstore.io/skills/sequenzy-emailautomationskill/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: "emailautomationskill security audit report (audit version 3)"
version: "unspecified"
type: report
authors:
  - name: "Sequenzy"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sequenzy-emailautomationskill/audits/3"
identifiers:
  - type: other
    value: "skillstore:sequenzy-emailautomationskill: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

Audit a Lifecycle Journey

Review a welcome, onboarding, or reactivation journey for missing exits, stale contacts, and unclear success metrics.

Create an Automation QA Plan

Turn branches, waits, suppressions, and test contacts into a practical pre-launch checklist.

Govern Production Changes

Define approval gates, ownership, rollback notes, and review cadence before a live automation is changed.

Try These Prompts

Map a Journey Contract

Use this skill to write a journey contract for my email automation. Include trigger, eligibility, waits, exits, suppression checks, and success event.

Build a Trigger Inventory

Use this skill to inventory my automation triggers. Group them by lifecycle stage, source event, owner, status, and production risk.

Review Launch QA

Use this skill to create a launch QA plan. Cover test contacts, branches, exits, event delays, suppression rules, and rollback steps.

Audit Overlapping Automations

Use this skill to audit overlapping journeys. Find duplicate sends, conflicting offers, frequency-cap pressure, stale enrollment, and approval gaps.

Best Practices

Provide trigger sources, event schema, suppression rules, and current journey status before asking for recommendations.
Ask for evidence notes so each recommendation links back to supplied data.
Use explicit approval gates before imports, live sends, suppression edits, or production journey changes.

Avoid

Do not ask the skill to activate, deactivate, or edit a live journey without human approval.
Do not assume missing consent, suppression, or event fields are valid.
Do not optimize copy before confirming triggers, exits, branch coverage, and rollback planning.