agentleFS
openparallaxopenparallax/skills/sales-outreach/SKILL.md

sales-outreach

Skill0 starsChanged 7 months agoApache-2.0View on GitHub

Cold email frameworks, follow-up sequences, objection handling, and outreach personalization

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. CatCatUncle/openworkbuddy★ 398same name
    2. crustdata/skills★ 11same name
    3. clawdbartell-wq/owl-skills★ 1same name
    4. poorvith-mp/skills-sales-support★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every cold email has four components:

    line 8
  2. Distinctive:

    Call to action: One specific, low-commitment ask.

    line 13
  3. Distinctive:

    Do not: attach files to cold emails, use "I hope this finds you well," include multiple CTAs, write walls of text, use generic templates …

    line 17
  4. Distinctive:

    Always use level 2 or higher.

    line 27
  5. Distinctive:

    After the sequence: stop. Do not continue emailing.

    line 43
  6. Distinctive:

    Never argue. Acknowledge their concern, ask a clarifying question, then offer a specific perspective.

    line 57
  7. Distinctive:

    Update the deal stage if it changed

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cold Email Framework

Every cold email has four components:

  1. Subject line: 3-7 words. Specific to the recipient. No clickbait. No ALL CAPS.
  2. Opening line: Reference something specific about the recipient (recent post, company news, mutual connection). Proves you did research.
  3. Value proposition: One sentence explaining what you offer and why it matters to THEM specifically. Not features, outcomes.
  4. Call to action: One specific, low-commitment ask. "Would a 15-minute call this week make sense?" not "Let me know if you want to learn more."

Total length: Under 125 words. Three short paragraphs maximum. Mobile-friendly.

Do not: attach files to cold emails, use "I hope this finds you well," include multiple CTAs, write walls of text, use generic templates without personalization.

Personalization

Three levels of personalization:

  1. Basic: Use their name, company name, and industry. Minimum viable effort.
  2. Contextual: Reference a specific initiative, blog post, job listing, or company event. Shows you researched them.
  3. Insight: Connect their specific situation to a relevant case study or data point. Shows you understand their problem.

Always use level 2 or higher. Level 1 personalization is transparent and ineffective.

Where to research: LinkedIn profile and posts, company blog, recent press releases, job listings (signal priorities), earnings calls (for public companies), industry reports.

Follow-Up Sequence

Timing and approach for a 5-touch sequence:

  • Day 1: Initial email (value-focused)
  • Day 3: Short follow-up adding a relevant data point or case study
  • Day 7: Different angle. New insight, different value prop, or relevant trigger event
  • Day 14: Social proof. Brief mention of a similar company you helped
  • Day 21: Breakup email. "Looks like the timing isn't right. I'll stop reaching out, but here's a resource you might find useful."

Each follow-up should add new value, not just ask "did you see my last email?"

After the sequence: stop. Do not continue emailing. Revisit in 3-6 months with a new trigger event.

Objection Handling

Common objections and how to address them:

"We already have a solution": "That makes sense. What I've been hearing from teams using [competitor] is [specific pain point]. Is that something you've experienced?"

"Not a priority right now": "Understood. When do you typically evaluate [category]? I'd love to reconnect at the right time."

"Send me more info": Often a brush-off. Respond with a specific question that qualifies them: "Happy to. To send the most relevant info, can you share what your biggest challenge is with [area]?"

"Too expensive": "What are you comparing it to? Let me understand your budget framework and see if there is a way to make this work."

Never argue. Acknowledge their concern, ask a clarifying question, then offer a specific perspective.

CRM Hygiene

After every touchpoint:

  • Log the interaction (date, channel, summary, next step)
  • Update the deal stage if it changed
  • Set a specific follow-up date and task
  • Tag the contact with relevant attributes (industry, company size, pain points mentioned)

Pipeline review: Weekly. For each deal, answer: What is the next concrete action? When will it happen? What could block it?

Metrics That Matter

  • Reply rate: Aim for 5-15% on cold outreach. Below 5% means your messaging or targeting is off.
  • Positive reply rate: What percentage of replies express interest? This is more important than raw reply rate.
  • Meetings booked per 100 emails: The ultimate efficiency metric.
  • Sequence completion rate: If most prospects drop off after email 2, your follow-ups need work.

Optimize messaging before optimizing volume. Sending more bad emails does not help.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.