- Sales
- v1.0.0
- outreach
- sales
7-day LinkedIn warm-up
Use this skill when a LinkedIn account needs warming up before outreach: a brand-new account, a dormant one coming back, or a fresh sender being added to a campaign pool. Produces a day-by-day ramp schedule that takes the account from zero activity to full outreach volume in seven days without triggering verification prompts or restrictions.
SKILL.md
Run this before any new or dormant LinkedIn account sends its first campaign. It produces a seven-day activity schedule and a go/no-go decision for opening full outreach.
The play
- Confirm the account's starting state: brand new, dormant, or returning from a warning. A returning account restarts this plan from day 1, never mid-way.
- Days 1-2: 3-5 likes and 1 comment per day, up to 5 connection requests per day. Nothing else. The account is being watched hardest here.
- Days 3-4: 3-5 likes and 1-2 comments per day, up to 10 connection requests per day.
- Days 5-7: start light conversations with accepted connections, up to 15-20 connection requests per day.
- After day 7, settle into the steady state: 20 connection requests per day reached gradually, 5-10 likes and 2-3 comments daily, small profile updates weekly. Open full outreach.
- Send links only after a prospect has replied, never in a first message.
- If the account receives any warning or verification prompt at any point: pause all activity for 48-72 hours, then resume one level below where the warning happened.
What good looks like
- The operators who keep accounts alive treat a warning as a hard stop, not noise. The mediocre version shrugs it off, keeps sending, and turns a warning into a restriction.
- Consistency beats speed. Seven steady days outperform three aggressive ones: identical daily behavior is what makes the account look human, and rushed ramps are the number-one cause of verification prompts.
- Engagement is not filler. The likes and comments in the early days are what makes the connection requests that follow look like a person, not a script. Skipping them to "save time" defeats the plan.
- Done well, the account reaches 20 connection requests per day with zero verification prompts, and the first replies are already arriving from the day 5-7 conversations.
Rules
- MUST pause 48-72 hours after any warning or verification prompt, then resume one level down.
- MUST keep daily activity consistent; never compress two days of the ramp into one.
- NEVER send identical messages across prospects; vary every message.
- NEVER include a link before the prospect has replied.
- NEVER skip the engagement activity (likes, comments) and run connection requests alone.
Files
1 file ship with this skill. They are installed beside the SKILL.md.
NOTICE1.4 KB
7-day LinkedIn warm-up
Imported from the GTM Skills library by Swan (https://www.gtmskills.com), skills/imad-badreddine/linkedin-7-day-warmup
at https://github.com/swan-gtm/gtm-skills/commit/5d786aad0c7b2ca59b1abf1f601f9407ca261996. Written by Imad Badreddine (https://www.linkedin.com/in/imad-ngl/).
The skill is shared under the MIT License below; this notice must stay with any copy.
MIT License
Copyright (c) 2026 Swan
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.