Individual skill
multi-sender-rotation
Use this skill when one LinkedIn campaign needs more volume than a single account can safely send: scaling outreach across several sender accounts, sizing a sender pool, splitting a lead list between profiles, or reacting when one account in the pool gets a warning. Produces a rotation plan with per-account caps and an incident playbook.
skills/imad-badreddine/multi-sender-rotation/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 235
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,154 bytes
Read excerpt
Run this when campaign volume exceeds what one account can safely send. It produces a sender-pool plan: how many accounts, how leads are split, per-account caps, and what happens when an account degrades.
## The play
1. Size the pool from the target, not the other way around: divide required daily connection requests by 20, the safe steady-state ceiling per warmed account. A 100-invite-per-day campaign is a 5-account pool.
2. Only rotate warmed accounts. A new profile joins the pool after a full warm-up ramp, never on day one. Keep one warmed spare per five active senders: the bench rule. When an account degrades, the bench replaces it the same day.
3. Split the lead list by account, never round-robin per message. Each prospect belongs to exactly one sender for the entire relationship: the one-voice rule. Dedupe by person and by company before launch so two senders never hit the same account.
4. Stagger sending windows so the pool does not fire in one burst: each account keeps its own working hours, matched to its own timezone and history.
5. Keep per-account caps individual. An account fresh off warm-up sends less than a veteran; never apply the pool average to every profile.
6. On any warning: pull that account from rotation immediately, pause it 48-72 hours, and let the bench absorb its remaining volume. Never redistribute a paused account's leads mid-conversation; conversations wait for their owner.
7. Review the pool weekly: acceptance rate and reply rate per account. One account trending down while others hold is an account problem; all accounts trending down together is a targeting or copy problem.
## What good looks like
