agentleFS
sami2919sami2919/SignalForce/skills/multi-channel-writer/SKILL.md

multi-channel-writer

Skill9 starsChanged 3 months agoMITView on GitHub

Use when generating coordinated outreach across email and LinkedIn, when building staggered multi-channel sequences, or when a prospect hasn't responded to single-channel outreach

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    Call select_primary_channel(has_email, has_linkedin) from scripts/multi_channel_sequencer.py.

    line 17
  2. Very specific:

    Call build_sequence(channels, signal_type).

    line 27
  3. Distinctive:

    Never: "I hope this email finds you well", "touching base", "I noticed your company".

    line 54

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

Multi-Channel Writer

Input

  • Contact data: name, title, company, email (yes/no), LinkedIn URL (yes/no)
  • Signal type: github | arxiv | hiring | funding | huggingface
  • Signal payload: specific detail (repo name, paper title, job title, etc.)
  • Company research from prospect-researcher

Step 1 — Determine Channels

Call select_primary_channel(has_email, has_linkedin) from scripts/multi_channel_sequencer.py.

AvailableSequence
Email + LinkedInDual channel (6 steps)
Email onlyEmail only (3 steps)
LinkedIn onlyLinkedIn only (3 steps)

Step 2 — Build Sequence

Call build_sequence(channels, signal_type). This returns the ordered SequenceStep list with days, channels, actions, and template names.

Step 3 — Generate Copy

For each step, write the actual message using the mapped template:

Email templates → config/templates/email-sequences/ LinkedIn templates → config/templates/linkedin-sequences/

Fill all placeholders from the signal payload and contact data. Never leave a placeholder unfilled.

Connection request notes must be ≤300 characters. Count before outputting.

Step 4 — Present the Full Plan

Output a single table showing the complete sequence:

DayChannelActionSubject / Opening line

Then present the full copy for each step in order.

Voice Rules

  • Email: 4 sentences max on Day 0. Reference the specific signal. Low-friction CTA.
  • LinkedIn connection: ≤300 chars, zero product mention, peer-to-peer tone.
  • LinkedIn follow-ups: lead with a resource or insight, no pitch unless they ask.
  • Never: "I hope this email finds you well", "touching base", "I noticed your company".

Quality Checklist

Before outputting, verify:

  • Connection request notes are ≤300 characters
  • Day 0 email is ≤4 sentences
  • No placeholder left as {{placeholder}}
  • No product mention in LinkedIn connection note
  • Steps are in ascending day order
  • Each step references the specific signal, not generic domain interest

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.