agentleFS
bcharlesonbcharleson/cursor-for-gtm-demo/.cursor/skills/gtm-outreach/SKILL.md

gtm-outreach

Skill2 starsChanged 4 months agoMITView on GitHub

Guides cold outreach strategy for email and LinkedIn using business-agnostic best practices. Use when planning, reviewing, or executing cold outreach, outbound sales, prospecting, GTM motions, or when the user mentions cold email, LinkedIn outreach, lead generation, or sales development.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. mia-cx/skills★ 4same 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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    No small talk, no flattery openers, no novels.

    line 46
  2. Distinctive:

    Ask for missing context rather than inventing specific claims, metrics, or customer names.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

GTM Outreach

When to Use This Skill

Apply this skill as the entry point for any cold outreach work in this project. Route to specialized skills based on the task.

Skill Routing

User needRead and follow
Inbox placement, DNS auth, ESP/SEG setup, sending infrastructurecold-email-deliverability
Writing, editing, or reviewing email copycold-email-copywriting
LinkedIn messaging or connection requestsComing soon — apply email copy principles until dedicated skill exists

Outreach Stack (Mental Model)

Sending infrastructure          Message                    Recipient environment
─────────────────────          ───────                    ─────────────────────
SPF / DKIM / DMARC      →      Plain text, relevant  →    Google / Microsoft / custom ESP
Domain reputation              Hook → Bridge → CTA         SEGs (Proofpoint, Mimecast…)
Plain text, no links           Low-friction ask            Corporate security filters

Agent Workflow

  1. Clarify the goal — Who is the ICP? What is the offer? What outcome does the user want (reply, meeting, asset sent)?
  2. Check infrastructure first — Before drafting or approving send plans, verify deliverability prerequisites via the deliverability skill.
  3. Draft or review copy — Use the copywriting skill. Never approve copy that violates deliverability rules unless the user explicitly opts in.
  4. Validate as a unit — Infrastructure + copy + CTA must align. A great email on a broken domain still fails.

Non-Negotiables

  • Deliverability is always top of mind.
  • Cold email defaults to plain text with no links or images unless the user intentionally chooses otherwise.
  • Missing SPF, DKIM, or DMARC must be flagged immediately — do not treat as optional.
  • No small talk, no flattery openers, no novels.
  • CTAs should be low-friction; hard asks for meetings are the exception, not the rule.

Business-Agnostic Adaptation

These skills define how to outreach. The user supplies what:

  • ICP (ideal customer profile)
  • Value proposition and proof (case studies, outcomes)
  • Sending domain and tooling

Ask for missing context rather than inventing specific claims, metrics, or customer names.

Project Context

For broader project intent and agent behavior defaults, see cursor/gtm-outreach-overview.md.

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.