connections-optimizer
SKILL.md
Connections Optimizer
Reorganize the user's network instead of treating outbound as a one-way prospecting list.
This skill handles:
- X following cleanup and expansion
- LinkedIn follow and connection analysis
- review-first prune queues
- add and follow recommendations
- warm-path identification
- Apple Mail, X DM, and LinkedIn draft generation in the user's real voice
When to Activate
- the user wants to prune their X following
- the user wants to rebalance who they follow or stay connected to
- the user says "clean up my network", "who should I unfollow", "who should I follow", "who should I reconnect with"
- outreach quality depends on network structure, not just cold list generation
Required Inputs
Collect or infer:
- current priorities and active work
- target roles, industries, geos, or ecosystems
- platform selection: X, LinkedIn, or both
- do-not-touch list
- mode:
light-pass,default, oraggressive
If the user does not specify a mode, use default.
Tool Requirements
Preferred
x-apifor X graph inspection and recent activitylead-intelligencefor target discovery and warm-path ranking- Exa / deep research for person and company enrichment
brand-voicebefore drafting outbound
Fallbacks
- browser control for LinkedIn analysis and drafting
- browser control for X if API coverage is constrained
- Apple Mail or Mail.app drafting via desktop automation when email is the right channel
Safety Defaults
- default is review-first, never blind auto-pruning
- X: prune only accounts the user follows, never followers
- LinkedIn: treat 1st-degree connection removal as manual-review-first
- do not auto-send DMs, invites, or emails
- emit a ranked action plan and drafts before any apply step
Platform Rules
X
- mutuals are stickier than one-way follows
- non-follow-backs can be pruned more aggressively
- heavily inactive or disappeared accounts should surface quickly
- engagement, signal quality, and bridge value matter more than raw follower count
- API-first if the user actually has LinkedIn API access
- browser workflow must work when API access is missing
- distinguish outbound follows from accepted 1st-degree connections
- outbound follows can be pruned more freely
- accepted 1st-degree connections should default to review, not auto-remove
Modes
light-pass
- prune only high-confidence low-value one-way follows
- surface the rest for review
- generate a small add/follow list
default
- balanced prune queue
- balanced keep list
- ranked add/follow queue
- draft warm intros or direct outreach where useful
aggressive
- larger prune queue
- lower tolerance for stale non-follow-backs
- still review-gated before apply
Scoring Model
Use these positive signals:
- reciprocity
- recent activity
- alignment to current priorities
- network bridge value
- role relevance
- real engagement history
- recent presence and responsiveness
Use these negative signals:
- disappeared or abandoned account
- stale one-way follow
- off-priority topic cluster
- low-value noise
- repeated non-response
- no follow-back when many better replacements exist
Mutuals and real warm-path bridges should be penalized less aggressively than one-way follows.
Workflow
- Capture priorities, do-not-touch constraints, and selected platforms.
- Pull the current following / connection inventory.
- Score prune candidates with explicit reasons.
- Score keep candidates with explicit reasons.
- Use
lead-intelligenceplus research surfaces to rank expansion candidates. - Match the right channel:
- X DM for warm, fast social touch points
- LinkedIn message for professional graph adjacency
- Apple Mail draft for higher-context intros or outreach
- Run
brand-voicebefore drafting messages. - Return a review pack before any apply step.
Review Pack Format
CONNECTIONS OPTIMIZER REPORT
============================
Mode:
Platforms:
Priority Set:
Prune Queue
- handle / profile
reason:
confidence:
action:
Review Queue
- handle / profile
reason:
risk:
Keep / Protect
- handle / profile
bridge value:
Add / Follow Targets
- person
why now:
warm path:
preferred channel:
Drafts
- X DM:
- LinkedIn:
- Apple Mail:
Outbound Rules
- Default email path is Apple Mail / Mail.app draft creation.
- Do not send automatically.
- Choose the channel based on warmth, relevance, and context depth.
- Do not force a DM when an email or no outreach is the right move.
- Drafts should sound like the user, not like automated sales copy.
Related Skills
brand-voicefor the reusable voice profilelead-intelligencefor weighted target and warm-path discoveryx-apifor X graph access, drafting, and optional apply flowscontent-enginewhen the user also wants public launch content around network moves
Weekly Installs
19
Repository
affaan-m/everyt…ude-codeGitHub Stars
131.2K
First Seen
Today
Security Audits
Installed on
codex18
opencode17
kimi-cli16
gemini-cli16
deepagents16
antigravity16