技能 cold-email-weekly-rhythm
📦
cold-email-weekly-rhythm
內容修訂 r1 安全 ⚙️ 外部命令📁 檔案系統存取
Plan Your Weekly Cold-Email Workflow
Cold-email programs lose consistency when prospect research, replies, and campaign reviews happen irregularly. This skill organizes weekly tasks and metric comparisons into a repeatable Monday, Wednesday, and Friday workflow.
支援: Claude Codex Code(CC)
使用我的智慧代理安裝
將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。
智能體請求
Review the Skillstore skill "cold-email-weekly-rhythm" from https://skillstore.io/skills/cmj-hub-cold-email-weekly-rhythm.md and its manifest at https://skillstore.io/api/skills/cmj-hub-cold-email-weekly-rhythm/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。
測試它
正在使用「cold-email-weekly-rhythm」。 Prepare Monday's queue. I have two hours for personalization, 25 verified prospects, and an infrastructure limit of 30 sends.
預期結果:
- Monday queue: Prepare one sequence for 25 verified prospects, within the provided infrastructure limit.
- Personalization depth: Deep. Confirm that the available two hours covers all 25 prospects before approval.
- List quality: No scoring results were supplied. Check duplicates, role fit, and signal freshness before sending.
- Wednesday: Review drafts and triage replies. Friday: Compare results with the previous week.
正在使用「cold-email-weekly-rhythm」。 Review Friday results: 200 sends, 20 replies, and 8 positive replies. Last week: 200 sends, 16 replies, and 6 positives.
預期結果:
- Reply rate: 10% this week versus 8% last week.
- Positive-reply rate, using sends as the denominator: 4% this week versus 3% last week.
- Four-week trend and buy-signal rate: Not available from the supplied data.
- Next week's single adjustment: Test one new subject line while keeping targeting and email body unchanged.
- Verification metric: Reply rate. The supplied totals cannot identify which messaging pattern caused the improvement.
安全審計
安全v1 • 2026/10/3 開啟版本化報告
All 26 static findings are false positives: Markdown backticks and fixed references to companion skills or scripts, not executable backticks or exploitative traversal. No evidence found of prompt injection, credential theft, or unauthorized data export in the reviewed file. Referenced dependencies and sending infrastructure were not included in this review.
1
已掃描檔案
185
分析行數
0
複核項目
0
已忽略的誤報
風險因素
⚙️ 外部命令 (20)
SKILL.md:20 SKILL.md:40 SKILL.md:43 SKILL.md:46 SKILL.md:52-71 SKILL.md:71-81 SKILL.md:81-83 SKILL.md:83-84 SKILL.md:84-87 SKILL.md:87-88 SKILL.md:88-92 SKILL.md:92-108 SKILL.md:108-129 SKILL.md:129-151 SKILL.md:151-179 SKILL.md:179-180 SKILL.md:180-181 SKILL.md:181-182 SKILL.md:182-183 SKILL.md:183-184
📁 檔案系統存取 (6)
最近一次完成的靜態與語意稽核未偵測到已確認的安全發現。這並不能證明該 Skill 沒有副作用。
審計單位: codex
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/cmj-hub-cold-email-weekly-rhythm/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/cmj-hub-cold-email-weekly-rhythm?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/cmj-hub-cold-email-weekly-rhythm?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cmj-hub-cold-email-weekly-rhythm/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/cmj-hub-cold-email-weekly-rhythm.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 引用
cmj-hub. (2026). cold-email-weekly-rhythm security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cmj-hub-cold-email-weekly-rhythm/audits/1BibTeX 引用
@techreport{cmj-hub-cmj-hub-cold-email-weekly-rhythm-2026,
author = {cmj-hub},
title = {cold-email-weekly-rhythm security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cmj-hub-cold-email-weekly-rhythm/audits/1},
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: "cold-email-weekly-rhythm security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "cmj-hub"
date-released: "2026-10-03"
url: "https://skillstore.io/skills/cmj-hub-cold-email-weekly-rhythm/audits/1"
identifiers:
- type: other
value: "skillstore:cmj-hub-cold-email-weekly-rhythm:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中 55
架構
85
可維護性
87
內容
65
社群
83
規範符合度
你可以打造什麼
Manage Founder Outreach
Plan prospect research, sequence preparation, and weekly reviews around limited personalization time.
Organize Reply Triage
Prepare a Wednesday queue that separates sales opportunities, positive replies, nurture candidates, and contacts to suppress.
Review Campaign Performance
Compare weekly metrics and four-week trends, then choose one measurable adjustment for the next cycle.
試試這些提示
Beginner: Prepare This Week's Tasks
Plan my cold-email rhythm for this week using the attached configuration and campaign notes. List Monday, Wednesday, and Friday tasks. Identify missing inputs.
Intermediate: Build the Monday Queue
Build Monday's queue from these prospect signals, warm-up status, reply trends, and available personalization time. Use available list-quality tools. Flag unverified or stale signals.
Advanced: Prepare Wednesday Triage
Prepare Wednesday's sequence and reply report using these drafts, replies, voice guidance, and routing rules. Use available companion checks. Flag ambiguous replies and failed drafts. Do not send messages.
Advanced: Analyze Friday Trends
Review these weekly logs against last week and the four-week trend. Separate missing data from measured results. Recommend exactly one change and its verification metric. Add a quarterly review if due.
最佳實務
- Provide current configuration, verified prospect signals, and complete campaign logs before requesting a weekly review.
- Review draft failures, ambiguous replies, suppression decisions, and send limits before approving any infrastructure handoff.
- Change one campaign variable per week and define the metric that will verify its effect.
避免
- Treating suggested send volume as permission to bypass infrastructure limits, recipient preferences, or operator approval.
- Requesting precise campaign trends without reliable logs or consistent metric definitions.
- Changing targeting, subject lines, and messaging simultaneously after a weekly review.
常見問題
What does the weekly workflow cover?
Monday covers signals and list refreshes. Wednesday covers sequence preparation and reply triage. Friday covers metrics and one adjustment.
Does this skill send emails automatically?
The file describes a handoff to your sending infrastructure. It contains no standalone sender or background scheduler.
What information should I provide?
Provide brand configuration, prospect sources, warm-up status, personalization time, campaign logs, and recent replies. Wednesday drafting also uses voice guidance.
Are companion skills required?
The workflow delegates specialized checks to companion skills. Their implementation and referenced scoring scripts were not included in this review.
Can I use it with Claude, Codex, or Claude Code?
The marketplace lists all three tools as supported. Actual workflow execution depends on available companion skills, permissions, and campaign inputs.
How does the quarterly review differ?
Every 13 weeks, the playbook reviews audience fit, signals, messaging, infrastructure, and banned phrases. It proposes one broader adjustment.