cold-email-weekly-rhythm
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.
Instalar com meu Agente
Copie esta solicitação para o seu Agente. Ela inclui a página canônica do Skill e o manifesto.
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.Seu Agente ainda deve apresentar o plano e solicitar qualquer confirmação exigida pela política de segurança.
Recursos legíveis por agentes
Use estes links quando um agente de IA, crawler ou script precisar de contexto limpo em vez de ler a página completa.
Testar
Usando "cold-email-weekly-rhythm". Prepare Monday's queue. I have two hours for personalization, 25 verified prospects, and an infrastructure limit of 30 sends.
Resultado esperado:
- 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.
Usando "cold-email-weekly-rhythm". Review Friday results: 200 sends, 20 replies, and 8 positive replies. Last week: 200 sends, 16 replies, and 6 positives.
Resultado esperado:
- 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.
Auditoria de segurança
SeguroAll 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.
Fatores de risco
⚙️ Comandos externos (20)
📁 Acesso ao sistema de arquivos (6)
Compartilhar e citar este relatório
Compartilhe o relatório de avaliação versionado, o badge neutro, o cartão incorporável e as citações. A Skillstore apresenta evidências sem decidir se este Skill é seguro.
Copiar link do relatório
https://skillstore.io/skills/cmj-hub-cold-email-weekly-rhythm/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/cmj-hub-cold-email-weekly-rhythm?utm_source=security_passport_badge)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>Cartão incorporável
<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>Citações acadêmicas (APA · BibTeX · CFF)
Citação 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/1Citação BibTeX
@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"
Pontuação do Skillstore
Por que esta pontuação Confiança das evidências: MédioO que você pode criar
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.
Teste estes prompts
Plan my cold-email rhythm for this week using the attached configuration and campaign notes. List Monday, Wednesday, and Friday tasks. Identify missing inputs.
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.
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.
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.
Boas práticas
- 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.
Evitar
- 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.