emails
Create Lifecycle Email Sequences
Email campaigns can lose focus when timing, audience needs, and conversion goals are unclear. This skill creates structured sequences with practical copy and measurement guidance.
使用我的智慧代理安裝
將此請求複製給你的智慧代理,其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "emails" from https://skillstore.io/skills/coreyhaines31-emails.md and its manifest at https://skillstore.io/api/skills/coreyhaines31-emails/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫,並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時,請使用這些連結。
測試它
正在使用「emails」。 Write a welcome email for a project management trial. The first action is creating a project.
預期結果:
- Send: Immediately after signup.
- Subject: Create your first project in Taskboard
- Preview: Give your team one place to organize its next project.
- Body: Welcome to Taskboard. Start with one project your team is working on today. Add its name and first task to begin organizing the work.
- CTA: Create my first project. Destination: Project creation page.
正在使用「emails」。 Plan a three-email re-engagement sequence for consenting subscribers inactive for 60 days.
預期結果:
- Trigger: 60 days without recorded engagement. Goal: Confirm interest. Exit: A subscriber confirms interest or unsubscribes.
- Email 1, day 0: Share a useful recent resource. Subject: Your next weekly planning template. CTA: View the template.
- Email 2, day 4: Explain relevant improvements. Subject: Two updates to your planning toolkit. CTA: Explore the updates.
- Email 3, day 10: Ask whether to continue. Subject: Would you like to keep receiving our emails? CTA: Keep my subscription.
- End condition: Stop marketing sends to nonresponders after the final confirmation window. Track clicks, confirmations, and unsubscribes.
安全審計
安全All 24 static findings are false positives caused by marketing terminology, Markdown formatting, or documentation links. No evidence found of reconnaissance, shell execution, data exfiltration, or prompt injection targeting the audit. Linked integration guides are outside the reviewed five-file scope.
風險因素
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據,不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/coreyhaines31-emails/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/coreyhaines31-emails?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/coreyhaines31-emails?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/coreyhaines31-emails/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/coreyhaines31-emails.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
coreyhaines31. (2026). emails security audit report (audit version 1) [Author version 2.1.1]. Skillstore. https://skillstore.io/skills/coreyhaines31-emails/audits/1BibTeX 引用
@techreport{coreyhaines31-coreyhaines31-emails-2026,
author = {coreyhaines31},
title = {emails security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/coreyhaines31-emails/audits/1},
note = {Author version 2.1.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "emails security audit report (audit version 1)"
version: "2.1.1"
type: report
authors:
- name: "coreyhaines31"
date-released: "2026-10-05"
url: "https://skillstore.io/skills/coreyhaines31-emails/audits/1"
identifiers:
- type: other
value: "skillstore:coreyhaines31-emails:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Guide Trial Users Toward Activation
Create onboarding emails that lead new trial users toward a first project, team invitation, or other defined activation step.
Nurture Report Downloads Into Demo Requests
Plan educational follow-ups after a report download, building toward a demo request with relevant content and verified customer examples.
Reconnect With Inactive Subscribers
Draft a re-engagement sequence that explains current value, invites subscribers to stay, and defines when to stop sending.
試試這些提示
Write the first welcome email for [product] aimed at [audience]. Include a subject, preview, body, and one CTA for [first action].
Create five onboarding emails for [product] with a [duration]-day trial. Target [activation action]. Include timing, copy, CTA destinations, and exit conditions.
Review [sequence] for [audience] and [goal]. Identify weak timing, unclear CTAs, and repetitive copy. Rewrite weak emails and propose single-variable tests.
Design onboarding, retention, and win-back flows for [product]. Segment by [behavior] and [plan]. Define triggers, exclusions, exits, copy, metrics, and test priorities.
最佳實務
- Provide the product, audience, entry trigger, conversion goal, and verified facts before requesting a sequence.
- Give each email one primary purpose and CTA, with explicit segment conditions and sequence exit rules.
- Test one variable at a time and assess conversions and unsubscribes alongside opens and clicks.
避免
- Do not combine several unrelated offers or competing primary CTAs in one email.
- Do not use fake reply prefixes, invented customer results, or unsupported urgency.
- Do not publish drafts without checking consent, suppression rules, unsubscribe access, and actual destination links.
常見問題
What does this skill produce?
Does it send emails or configure automations?
What information should I provide?
Can it use existing product context?
Can it improve an existing sequence?
Does it cover cold outreach or in-app onboarding?
開發者詳細資訊
授權
MIT
作者版本
v2.1.1
Skillstore 修訂
r1
引用
881b30037edb912e12cb45a2d6b8610e6cf64ec1
維護新鮮度
2026/10/6
使用量
0 次下載 · 0 次瀏覽
檔案結構