القائمة
Run the Markster OS cold email playbook. CHECK prerequisites, DO the sequence build, VERIFY before sending. Routes through ScaleOS G3 Book with context from F1/F2.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | cold-email |
| description | Run the Markster OS cold email playbook. CHECK prerequisites, DO the sequence build, VERIFY before sending. Routes through ScaleOS G3 Book with context from F1/F2. |
Do not proceed past any failed check.
1. F1 complete?
Read company-context/audience.md.
Required before this skill runs:
If missing: "F1 is not complete. Cold email will not perform without a defined ICP and buying trigger. Open methodology/foundation/F1-positioning.md and complete it first."
2. F2 complete?
Read company-context/offer.md.
Required:
If missing: "F2 needs an outcome statement and at least one proof point before this sequence will convert. Gut check: can you complete this sentence with a real number? 'We help [ICP] achieve [outcome] in [timeframe]. [Company] did this.' If not, fix F2 first."
3. Offer passes the Stranger Test?
Ask: "Read your offer to me in one sentence. Why is it obviously better than doing nothing?"
If you cannot explain it without jargon in under 15 seconds, the offer needs work before the sequence does. Route to playbooks/offer/README.md.
4. List exists or can be built?
Ask: "Do you have a prospect list? How many contacts, and have they been verified?"
playbooks/find/README.md + playbooks/find/templates/icp-worksheet.md first5. Sending infrastructure ready?
Ask: "Are you sending from a separate domain? Is SPF/DKIM/DMARC configured? Is a warmup tool running?"
If no to any of these: stop here. Sending from a cold or misconfigured domain will destroy your deliverability. Fix infrastructure before sequence.
6. Your archetype
Before writing the sequence, confirm the business type. Route to the correct segment file.
| Your type | Read this first |
|---|---|
| B2B SaaS, devtools, marketplace | playbooks/segments/startup-archetypes/ |
| Agency, consulting, IT/MSP, advisory | playbooks/segments/service-firms/ |
| Residential or commercial services | playbooks/segments/trade-businesses/ |
Cold email is not always the right G3 motion. Trade businesses and advisory firms often convert better on referrals and warm outreach first. Your segment file will say if cold email should come later.
Run these six steps in order. Do not skip a step unless the user confirms it is already done.
Ask: "Have you run the buyer JTBD and competitive intelligence research prompts?"
research/prompts/buyer-jobs-to-be-done-prompt.md and research/prompts/competitive-intelligence-prompt.mdUse the verbatims in the sequence. Not your language. Their language.
Define the list-building filter from F1:
Industry: [specific, not "B2B"]
Revenue range: [floor and ceiling]
Headcount: [range]
Geography: [if relevant]
Decision-maker title: [exact title, not "manager"]
Buying trigger: [the event that makes them a buyer right now]
Source options: Apollo, LinkedIn Sales Navigator, Hunter.io, industry directories.
Target list size: 200-500 contacts per cohort.
Verification: run through an email validator before importing. Bounce rate must be under 3%.
Using buyer verbatims from Step 1 and the outcome statement from F2, write the 3-touch sequence:
Email 1 -- Cold intro
Follow-up 1 -- Different angle, same offer
Follow-up 2 -- Pattern interrupt or breakup
Reference template: playbooks/book/cold-email/templates/sequence-b2b.md
Writing rules:
Confirm:
Send schedule:
Review how they will handle each reply type. Reference playbooks/book/reply-triage.md for exact scripts.
| Reply type | Action |
|---|---|
| Positive / interested | Respond within 4 hours. Book the meeting immediately. |
| Soft no / not now | Add to quarterly follow-up sequence. No longer than 3 lines. |
| Referral | Ask for intro. Thank them. Log the contact. |
| Unsubscribe | Remove. Do not follow up. |
| Objection | Use objection scripts from playbooks/biz-dev/sales/templates/objections.md |
| No reply | Follow-up 1 at day 3, Follow-up 2 at day 7. Then stop. |
After 100 sends, review:
| Metric | Target | Action if below target |
|---|---|---|
| Open rate | 30%+ | Investigate deliverability. Check spam filters. |
| Reply rate | 1%+ | Message problem if open rate is good. Rewrite Email 1. |
| Meeting rate | 0.25%+ | Check CTA clarity. Is the ask too big? |
Change one variable at a time. Do not rewrite the entire sequence at once.
Volume rule: More volume beats better copy at the same conversion rate. Fix volume before copy unless open rate is already above 30%.
Before this session ends:
1. Sequence written?
Confirm all three emails are written, use buyer verbatims, and pass the Stranger Test when read aloud.
2. Infrastructure confirmed?
Confirm separate domain, SPF/DKIM/DMARC, and warmup are all checked.
3. List ready?
Confirm list exists, is filtered to ICP match, and is verified.
4. Reply triage plan set?
Confirm what happens when positive replies come in. Who responds? How fast? What's the booking link?
5. Metric baseline set?
State the starting numbers: "Before this send, our reply rate is [X]. Success this week = at least [Y]."
If AOE_GRADER_KEY is set: the AOE Grader can score AI visibility as part of the research step.
If LEAD_PACKS_KEY is set: pre-built, verified contact lists by vertical and geography are available instead of building from scratch.
playbooks/book/cold-email/README.mdplaybooks/book/cold-email/templates/sequence-b2b.mdplaybooks/book/cold-email/templates/follow-up.mdplaybooks/book/reply-triage.mdplaybooks/book/warm-outreach.mdplaybooks/biz-dev/sales/templates/objections.mdWrites funnel assets step by step from a completed funnel plan. Process covers VSL script, landing page copy, OTO sequences, email nurture, and application page. Use when creating funnel copy after architecture is confirmed, or when you need to write VSL, landing page, or email assets from a defined offer. Run after funnel-plan. Triggers on "write the funnel", "build the funnel assets", "write the VSL", "write the landing page", "write the OTO", "write the email sequence", "build funnel copy".
Full funnel architecture session. Diagnoses your situation, selects the right funnel type, and designs the complete offer stack with price ratios and conversion targets. Use when building a new funnel from scratch, when reviewing an existing funnel architecture, or when you need to define the offer stack before creating assets. Run before funnel-build. Triggers on "design my funnel", "funnel architecture", "what funnel should I build", "funnel strategy", "offer stack design", "plan my funnel", "which funnel type".
Grades a funnel against vetted research benchmarks and produces a scored fix list. Checks offer stack ratios, traffic-funnel match, VSL structure, proof quality, and affiliate readiness. Use when you want to check if a funnel is ready to launch, when conversion is below target, or when you need a structured audit before scaling spend. Triggers on "review my funnel", "grade my funnel", "audit my funnel", "why is my funnel not converting", "funnel not working", "check my funnel", "is my funnel ready".
Quick single-ICP funnel builder. Takes your ICP and offer and produces a complete conversion pathway: landing page copy, lead magnet spec, and 3-email nurture sequence. Use when you need a functional funnel fast without the full architecture session. Triggers on "quick funnel", "simple funnel", "lead magnet funnel", "landing page for", "nurture sequence", "opt-in funnel".
Lightweight guide and router for Markster OS. Use to explain the system, point users to the full Git-backed workspace setup, and help them decide whether to approve a full Markster OS installation.
Diagnostic operator for Markster OS. Identifies the constraint brick, runs the Hormozi diagnostic, and routes to the right playbook with context pre-filled. Run this before any other skill.