본문으로 건너뛰기
cccskills
무료GitHub에 공개

outbound-prospecting

Finds, qualifies, and reaches prospects through cold outreach — list building, qualification criteria, cold email and multi-channel sequences, and the follow-up that actually gets replies. Use this to build a prospect list, write cold outreach, fix a sequence that is not getting responses, define qualification criteria, or decide whether a segment is worth pursuing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(2)

  • SKILL.md4.0 KB
  • references/sources.md2.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Outbound prospecting

Reply rates are set by list quality far more than by copy. Most outbound problems are targeting problems being solved as writing problems.

Build the list before writing anything

Define the qualifying signal — the observable fact that means this account probably has the problem you solve, right now. Hiring for a role, using a specific tool, a recent funding or expansion announcement, a public complaint about the thing you fix.

Without a signal you are sending to a demographic, and a demographic has no reason to reply.

Then qualify each account against: do they have the problem, can they afford it, can this person act, and is there a reason for now. Missing the last one is why good-fit prospects go quiet.

Writing

  • Under a hundred words. Longer gets skimmed and deleted.
  • Open with the signal, specifically. Show you looked. Generic personalization tokens are worse than none — they signal automation while pretending otherwise.
  • One problem, in their language, not your feature.
  • Ask for something small. A specific question or a fifteen-minute call. "Interested in learning more" asks the recipient to do the work of defining the next step.
  • No attachments, minimal links in a first message. Both hurt deliverability and trust.

Sequencing

Three to five touches over two to three weeks. Each one adds something new — a different angle, a relevant case, a useful resource. Never "just bumping this to the top of your inbox," which communicates that the first message was not worth reading either.

Multi-channel works when the channels are coordinated and the sender is a person. It reads as harassment when the same message arrives everywhere at once.

Stop after the sequence ends. Persistence past that converts nothing and costs reputation.

Deliverability

Domain warmed, authentication configured, volume per mailbox kept low, list validated. A technically broken send makes perfect copy irrelevant, and the damage to a sending domain takes months to repair.

Use a subdomain for outbound so a reputation problem cannot take down your transactional mail.

Reading results

  • No opens — deliverability or subject line. Check deliverability first.
  • Opens, no replies — the message is not landing. Usually the ask, or an unclear problem statement.
  • Replies, no meetings — a qualification problem: you are reaching people who cannot act.
  • Meetings, no pipeline — the segment is wrong.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Tooling

Sequencing: Outreach, Salesloft, Apollo, Lemlist, Instantly, and similar.

Contact data: ZoomInfo, Apollo, Clay, LinkedIn Sales Navigator, and similar. Every provider's data decays; verify before you send, whichever you buy.

Deliverability: a separate sending domain, plus warmup and monitoring — Instantly, Smartlead, Google Postmaster Tools, and similar.

Never

  • Send before the list is qualified. A good message to the wrong person is still a bad message.
  • Send outbound from the domain that carries your customer and billing mail. Prospecting burns sender reputation; keep it on a separate domain.
  • Keep sequencing someone who replied. Pull them out the moment a human is in the thread.
  • Judge a sequence on open rates. Opens are unreliable and unactionable; judge on replies and meetings held.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

cbrock84/headcount2.1천2026년 10월 19일 업데이트

cbrock84의 스킬 모두 보기

이 스킬의 문제 신고