agentleFS
holaroluwaholaroluwa/outbound-skills/skills/outreach-strategist/SKILL.md

outreach-strategist

Skill0 starsChanged 49 days agoMITView on GitHub

Act as a virtual Head of Growth that coordinates the other outbound skills into a single composite plan, from a situation, a goal, and constraints. Use when the user describes a goal ("we want X meetings", "launch outbound for this product", "fix our pipeline") rather than a single task, or asks "where do I start", "what's the plan", or "put it all together". This is the orchestrator, it decides which skills to run, in what order, and stitches their outputs into one strategy.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read outreach-brief.md. Note which sections are filled and which are empty.

    line 16
  2. Distinctive:

    Do the funnel math: given the goal and rough conversion rates, how many to reach, at what volume, on which channels, within the constraints.

    line 23

≈ “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

Outreach Strategist

This is the Head of Growth in the room. When the user has a goal rather than a single task, this skill plans the campaign and pulls the other skills together into one coherent move.

Input needed

  • Situation, where things stand now: product, stage, what exists, what's been tried.
  • Goal, the outcome and timeframe (e.g., "10 qualified meetings in 30 days").
  • Constraints, budget, team, tools, time, channels available.

Method

  1. Read outreach-brief.md. Note which sections are filled and which are empty.
  2. Diagnose the gap between the goal and the current state. What's actually missing: targeting, message, volume, or follow-through?
  3. Sequence the work, calling the right skills in order. For a cold start, foundations first:
    • Foundations: deep-company-analyser → offer-definer → icp-definer → persona-definer → value-prop-lister → pain-identifier → competitor-finder → tam-sam-som-sizer.
    • Message: copywriting-first-touch → copywriting-follow-up → copywriting-linkedin-dm → cold-call-script.
    • Scale & learn: n8n-workflow-builder, then pipeline-analyser and reply-rate-analyser once data exists. Skip steps already done. Don't rebuild what the brief already has.
  4. Do the funnel math: given the goal and rough conversion rates, how many to reach, at what volume, on which channels, within the constraints.
  5. Lay out a phased plan with owners and a first-week action list.

Output

  • A one-paragraph diagnosis of the real gap.
  • A phased plan: which skills to run in what order, and why.
  • The funnel math (reach → replies → meetings → outcome) against the goal.
  • A first-week action list the user can start today.

Be decisive. Recommend, don't survey. If the goal isn't realistic under the constraints, say so and show the trade-off: more time, fewer meetings, higher-value targets, or a bigger budget.

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.