本文へ移動
cccskills
無料GitHub で公開

cold-outreach-that-isnt-spam

Write cold outreach to potential clients that gets replies — specific, useful, and about them — instead of the templated pitch that gets deleted. Use when asked to write a cold email to a prospect, get clients through outreach, cold pitch help, or reach out to potential customers. Produces a researched, personalized message that leads with their problem, a clear low-friction ask, proof you're credible without bragging, a subject line, and a short follow-up sequence — plus who to target and what to avoid so it lands as a helpful note, not spam.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Cold Outreach That Isn't Spam

Cold outreach works — the templated "I'd love to hop on a call" blast doesn't. The difference is specificity: a message that shows you understand their situation, offers something useful, and asks for one small thing. This writes outreach that reads like a thoughtful note from a competent person, not a mail-merge, so prospects actually reply.

What This Skill Produces

  • A personalized message — opening with their situation/problem (from real research), not your life story
  • A useful angle — a relevant insight, idea, or offer that gives value up front
  • Credibility, lightly — proof you can help (a relevant result/example) without bragging or a wall of credentials
  • A low-friction ask — one small, easy next step (a quick question, a short call, a resource), not a big commitment
  • A subject line — specific and honest, that earns the open
  • A follow-up sequence — a couple of short, non-pushy follow-ups that add value

Required Inputs

Ask for these if not provided:

  • What you offer — your service/product and who it helps
  • The target — the specific prospect or the type of client, and what you know about them
  • Their likely problem — the pain you solve for them
  • Your proof — a relevant result, example, or credibility marker
  • The channel & goal — email/LinkedIn, and the desired next step

Framework: Research, Relevance, Small Ask

  1. Lead with them. Open with something specific about their business/situation that shows you did the homework — the antidote to spam.
  2. Offer value, don't pitch. Give a useful idea, observation, or resource up front; make the message worth reading even if they don't reply.
  3. Prove it lightly. One relevant result or example establishes credibility; skip the brag and the credential dump.
  4. Ask for one small thing. A single low-friction next step (a quick reply, 15 minutes, permission to send something) beats "let's schedule a call to explore synergies."
  5. Subject line earns the open. Specific and honest — not clickbait, not vague.
  6. Follow up with value, briefly. A couple of short follow-ups that add something (not "just bumping this") — then stop.

Output Format

Cold outreach: [offer] → [target] · channel [x]

Subject: [specific, honest]. Message

[Specific opener about them] … [the useful angle/value] … [light proof] … [one small ask] … [easy close].

Target well: [who this fits / signals they need it]. Follow-ups: #1 [value-add, +[days]] · #2 [final light touch]. Then stop. Avoid: generic templates · all-about-you · big asks · fake urgency.

Quality Checks

  • Opens with specific research about the prospect
  • Offers value up front rather than pitching
  • Establishes credibility lightly, without bragging
  • Makes one small, low-friction ask
  • Has a specific, honest subject line
  • Includes a short, value-adding follow-up sequence

Anti-Patterns

  • Mail-merge templates with a [FIRST NAME] and nothing specific.
  • All about you and your services.
  • A big ask ("30-minute call to explore synergies") cold.
  • Clickbait or fake-urgency subject lines.
  • "Just bumping this" follow-ups with no value.

Example Trigger Phrases

  • "Write a cold email to a potential client I want to work with."
  • "Help me get clients through cold outreach without being spammy."
  • "Cold LinkedIn message to a prospect — make it not cringe."
  • "I need a pitch to reach out to local businesses."
  • "Write a follow-up sequence for prospects who didn't reply."

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する