📦
content-creator
88Create Brand-Consistent Marketing Content
Marketing teams need content that stays consistent across channels. This skill helps plan, write, analyze, and optimize content for brand voice and SEO.
Writing & Content View
Skills email-systems
📦
email-systems
Content revision r2 High Risk ⚙️ External commands🌐 Network access
Build Reliable Email Systems
Email systems often fail through weak deliverability, missing consent controls, or unreliable sending. This skill provides patterns for dependable transactional and marketing email infrastructure.
Supports: Claude Codex Code(CC)
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "email-systems" from https://skillstore.io/skills/sickn33-email-systems.md and its manifest at https://skillstore.io/api/skills/sickn33-email-systems/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.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.
Test it
Using "email-systems". Review our password reset email flow, which sends directly during the web request.
Expected outcome:
- Priority: move delivery to a durable queue so provider latency does not block the request.
- Add bounded retries, idempotency, expiration monitoring, and delivery alerts.
- Authenticate bounce and delivery webhooks before changing recipient state.
Using "email-systems". Plan deliverability for a new marketing domain sending 20,000 weekly messages.
Expected outcome:
- Configure SPF, DKIM, and DMARC before the first campaign.
- Warm sending volume gradually using recently engaged, consented recipients.
- Track hard bounces, complaints, inbox placement, unsubscribes, and provider limits.
Using "email-systems". Audit an HTML-only newsletter without an unsubscribe header.
Expected outcome:
Add a readable plain-text part, visible one-click unsubscribe, List-Unsubscribe headers, meaningful preview text, and accessible image alternatives.
Security Audit
High Riskv5 • 7/23/2026 Open versioned report
All 24 static detections are false positives caused by Markdown fences, placeholder URLs, or defensive email guidance. A separate high-severity issue remains: the bounce webhook example trusts an unsigned request body, enabling forged suppression events if implemented directly.
1
Files scanned
684
Lines analyzed
0
Review items
0
False positives ignored
Confirmed security concerns (1)
High
Unauthenticated Bounce Webhook Example
The example trusts a request body and changes recipient state without verifying a provider signature. Forged events could invalidate addresses and remove them from lists.
The complete webhook example reads req.body and performs destructive list changes without authentication. Exploitability depends on users implementing the example directly.
Risk Factors
⚙️ External commands (17)
🌐 Network access (2)
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.
Copy report link
https://skillstore.io/skills/sickn33-email-systems/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-email-systems?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-email-systems?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-email-systems/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-email-systems.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
sickn33. (2026). email-systems security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-email-systems/audits/5BibTeX citation
@techreport{sickn33-sickn33-email-systems-2026,
author = {sickn33},
title = {email-systems security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-email-systems/audits/5},
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: "email-systems security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-email-systems/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-email-systems:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 55
Architecture
85
Maintainability
87
Content
69
Community
78
Spec Compliance
What You Can Build
Launch Transactional Email
Plan reliable password resets, receipts, confirmations, queues, retries, and bounce processing.
Improve Campaign Deliverability
Review authentication, consent, list hygiene, warm-up, unsubscribe, and monitoring practices.
Audit Email Architecture
Identify reliability, accessibility, compliance, and reputation risks across an existing email system.
Try These Prompts
Review One Email Flow
Review this email flow: [describe flow]. Identify reliability, deliverability, consent, and accessibility gaps. Recommend the three highest-priority improvements.
Design Transactional Delivery
Design a transactional email system for [product]. Include provider separation, queue behavior, retries, idempotency, authenticated webhooks, bounce handling, and monitoring.
Plan Marketing Operations
Create an email operations plan for [audience and volume]. Cover consent, segmentation, preferences, authentication, warm-up, rate limits, complaints, and success metrics.
Audit a Production System
Audit this email architecture: [details]. Build a prioritized risk register covering security, deliverability, privacy, reliability, recovery, observability, and provider dependencies.
Best Practices
- Separate critical transactional messages from marketing traffic and reputation.
- Authenticate domains and provider webhooks before processing production email events.
- Monitor each send, suppress hard bounces, and honor complaints or unsubscribes immediately.
Avoid
- Do not send marketing email to purchased, scraped, or unconsented contacts.
- Do not send large volumes from a new domain or IP without gradual warm-up.
- Do not trust webhook payloads or update recipient state without signature verification.
Frequently Asked Questions
Does this skill send email directly?
No. It provides architecture, implementation patterns, validation checks, and operational guidance.
Which email providers does it support?
The guidance is provider-neutral, with examples mentioning services such as Postmark, Resend, SendGrid, ConvertKit, and Customer.io.
Does it cover transactional and marketing email?
Yes. It explains their different reliability, consent, reputation, and infrastructure requirements.
Can it guarantee inbox placement?
No. Inbox placement depends on authentication, sender reputation, content, recipient engagement, provider policy, and ongoing operations.
Does it provide legal advice?
No. It highlights consent and unsubscribe practices, but regional requirements require qualified legal review.
Are the code examples production-ready?
No. Add provider authentication, input validation, error handling, idempotency, privacy controls, and environment-specific tests before production use.
Developer Details
Author
sickn33License
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Maintenance freshness
7/26/2026
Usage
10 downloads · 112 views
File structure
📄 SKILL.md
More from sickn33
View all📦
prompt-engineering-patterns
85Improve LLM Prompts With Proven Patterns
Inconsistent prompts waste time and make AI outputs hard to trust. This skill guides prompt design with reusable patterns, examples, evaluation steps, and optimization workflows.
Productivity View
📦
senior-fullstack
82Build Fullstack Apps with Senior Patterns
Teams need consistent setup, architecture, and review guidance for modern web applications. This skill provides scaffolders, workflow references, and quality prompts for React, Next.js, Node.js, GraphQL, and PostgreSQL projects.
Coding & Development View
📦
senior-architect
81Design Scalable Software Architectures
Architecture decisions are hard to compare across web, mobile, backend, and cloud systems. This skill provides structured guides and local scaffold scripts for reports, dependency review, and trade-off documentation.
Coding & Development View
📦
prompt-engineer
81Optimize AI Prompts With Prompt Engineer
Writing clear prompts is hard when goals are vague or complex. This skill turns rough requests into structured prompts using proven prompt frameworks.
Productivity View
📦
product-manager-toolkit
80Prioritize Product Work With Research Insights
Product teams need faster ways to rank features, synthesize interviews, and document decisions. This skill provides RICE scoring, interview analysis, and PRD templates for structured planning.
Productivity View
Related Skills
View all📦
gws-gmail
81Manage Gmail with Google Workspace CLI
by googleworkspace
Managing Gmail through API commands requires accurate resource names and parameters. This skill guides Claude and Codex through supported Gmail CLI workflows.
Communication View
📦
converting-email-templates
81Convert Email Templates to Mailtrap
by mailtrap
Moving templates between email providers can break variables, conditionals, and send calls. This skill converts provider syntax to Mailtrap Handlebars and flags changes that need review.
Communication View
📦
email-drafter
80Draft Professional Business Emails
by shubhamsaboo
Writing clear workplace email can take time and create tone concerns. This skill helps draft structured messages for common business situations.
Communication View
📦
follow-up
78Write Better Follow-Up Emails
by humanizerai
Unanswered outreach needs tactful persistence, not repeated messages. This skill creates short follow-ups with fresh value and one clear ask.
Communication View
📦
subject-line-lab
78Create Test-Ready Email Subject Lines
by aaron-he-zhu
Weak subject lines can waste email test cells and obscure a useful offer. This skill creates and ranks subject and preheader variants with clear heuristic flags before a campaign test.
Communication View
📦
sending-emails
77Send Mailtrap Emails Correctly
by mailtrap
Mailtrap send paths can be confusing when transactional, bulk, batch, and campaigns overlap. This skill maps the right path and gives implementation references.
Communication View