Email automations can become hard to trace when triggers, exits, and owners are unclear. This skill maps routes and produces review-ready workflow guidance.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "emailworkflowskill" from https://skillstore.io/skills/sequenzy-emailworkflowskill.md and its manifest at https://skillstore.io/api/skills/sequenzy-emailworkflowskill/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.
Static analysis found no suspicious patterns in this prompt-only skill. Manual review found no prompt injection, data exfiltration intent, or unsafe email automation behavior.
3
Files scanned
70
Lines analyzed
0
Review items
0
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.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Sequenzy. (2026). emailworkflowskill security audit report (audit version 3) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sequenzy-emailworkflowskill/audits/3
BibTeX citation
@techreport{sequenzy-sequenzy-emailworkflowskill-2026,
author = {Sequenzy},
title = {emailworkflowskill security audit report (audit version 3)},
institution = {Skillstore},
year = {2026},
number = {3},
url = {https://skillstore.io/skills/sequenzy-emailworkflowskill/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: "emailworkflowskill security audit report (audit version 3)"
version: "unspecified"
type: report
authors:
- name: "Sequenzy"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sequenzy-emailworkflowskill/audits/3"
identifiers:
- type: other
value: "skillstore:sequenzy-emailworkflowskill:audit:3"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this scoreEvidence Confidence: Medium
41
Architecture
85
Maintainability
87
Content
67
Community
83
Spec Compliance
What You Can Build
Audit Lifecycle Routing
Review an existing email lifecycle map for unclear triggers, missing exits, ownership gaps, and duplicate enrollment risks.
Plan Sequence Handoffs
Define how contacts move between marketing, sales, product, and support messages without conflicting automation paths.
Prepare QA Notes
Convert workflow plans into operator-ready QA checks before template edits, imports, or production automation changes.
Try These Prompts
Map a Basic Workflow
Map this email workflow in text. Include the trigger, eligibility, wait steps, messages, exclusions, exits, owner, and reporting checkpoints.
Review Trigger Logic
Review these trigger and suppression rules. Identify ambiguous source data, duplicate enrollment risks, missing exits, and approval questions before launch.
Create a Handoff Plan
Create a handoff plan for this lifecycle sequence. Show ownership, route boundaries, CRM or product data dependencies, QA checks, and escalation points.
Audit a Multi-Path Lifecycle
Audit this multi-path email lifecycle. Produce a routing diff, collision risks, suppression checks, reporting checkpoints, and the smallest safe change set.
Best Practices
Start by defining the workflow boundary and every entry source.
Name one source of truth for each routing decision.
Keep live sends, imports, DNS changes, and production automation edits behind explicit approval.
Avoid
Changing production automations before mapping triggers, exits, and suppression rules.
Using hidden intent or broad segments when explicit events or properties are available.
Measuring only opens and clicks while ignoring enrollment, branch split, drop-off, and conversion by path.
Frequently Asked Questions
What email work is this skill designed for?
It supports workflow maps, lifecycle routing, trigger reviews, handoff plans, collision audits, and QA notes for email operations.
Can it make live changes in an email platform?
No. It produces plans and review artifacts, and it requires explicit approval before any live-system action.
What inputs make the review more useful?
Provide workflow exports, trigger rules, lifecycle definitions, suppression rules, ownership details, and recent examples of routing problems.
Does it help with compliance decisions?
It can surface consent and suppression checkpoints, but it does not replace legal review for email compliance.
Which tools can use this skill?
The report lists support for Claude, Codex, and Claude Code.
How does it handle high-risk email actions?
It treats live sends, contact imports, suppression edits, DNS changes, migrations, and destructive cleanup as approval-gated work.