Workflow·Sales & CRM

Connections Optimizer

Reorganize the user's X and LinkedIn network with review-first pruning, add/follow recommendations, and channel-specific warm outreach…

You say
Buy it · $79 Read it before you buy $79 Written by affaan-m · unverified publisher
Context cost
1.4k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 5.5 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
no release on file
Servers it uses
Noneruns standalone

What it does

Reorganize the user's X and LinkedIn network with review-first pruning, add/follow recommendations, and channel-specific warm outreach drafted in the user's real voice. Use when the user wants to clean up following lists, grow toward current priorities, or rebalance a social graph around higher-signal relationships.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

social media
Filed under

Sales & CRM

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md5.5 kB · 191 lines
--- name: connections-optimizer description: Reorganize the user's X and LinkedIn network with review-first pruning, add/follow recommendations, and channel-specific warm outreach drafted in the user's real voice. Use when the user wants to clean up following lists, grow toward current priorities, or rebalance a social graph around higher-signal relationships. metadata: origin: ECC ---
8# Connections Optimizer
9
10Reorganize the user's network instead of treating outbound as a one-way prospecting list.
11
12This skill handles:
13
14- X following cleanup and expansion
15- LinkedIn follow and connection analysis
16- review-first prune queues
17- add and follow recommendations
18- warm-path identification
19- Apple Mail, X DM, and LinkedIn draft generation in the user's real voice
20
21## When to Activate
22
23- the user wants to prune their X following
24- the user wants to rebalance who they follow or stay connected to
25- the user says "clean up my network", "who should I unfollow", "who should I follow", "who should I reconnect with"
26- outreach quality depends on network structure, not just cold list generation
27
28## Required Inputs
29
30Collect or infer:
31
32- current priorities and active work
33- target roles, industries, geos, or ecosystems
34- platform selection: X, LinkedIn, or both
35- do-not-touch list
36- mode: light-pass, default, or aggressive
37
38If the user does not specify a mode, use default.
39
40## Tool Requirements
41
42### Preferred
43
44- x-api for X graph inspection and recent activity
45- lead-intelligence for target discovery and warm-path ranking
46- social-graph-ranker when the user wants bridge value scored independently of the broader lead workflow
47- Exa / deep research for person and company enrichment
48- brand-voice before drafting outbound
49
50### Fallbacks
51
52- browser control for LinkedIn analysis and drafting
53- browser control for X if API coverage is constrained
54- Apple Mail or Mail.app drafting via desktop automation when email is the right channel
55
56## Safety Defaults
57
58- default is review-first, never blind auto-pruning
59- X: prune only accounts the user follows, never followers
60- LinkedIn: treat 1st-degree connection removal as manual-review-first
61- do not auto-send DMs, invites, or emails
62- emit a ranked action plan and drafts before any apply step
63
64## Platform Rules
65
66### X
67
68- mutuals are stickier than one-way follows
69- non-follow-backs can be pruned more aggressively
70- heavily inactive or disappeared accounts should surface quickly
71- engagement, signal quality, and bridge value matter more than raw follower count
72
73### LinkedIn
74
75- API-first if the user actually has LinkedIn API access
76- browser workflow must work when API access is missing
77- distinguish outbound follows from accepted 1st-degree connections
78- outbound follows can be pruned more freely
79- accepted 1st-degree connections should default to review, not auto-remove
80
81## Modes
82
83### light-pass
84
85- prune only high-confidence low-value one-way follows
86- surface the rest for review
87- generate a small add/follow list
88
89### default
90
91- balanced prune queue
92- balanced keep list
93- ranked add/follow queue
94- draft warm intros or direct outreach where useful
95
96### aggressive
97
98- larger prune queue
99- lower tolerance for stale non-follow-backs
100- still review-gated before apply
101
102## Scoring Model
103
104Use these positive signals:
105
106- reciprocity
107- recent activity
108- alignment to current priorities
109- network bridge value
110- role relevance
111- real engagement history
112- recent presence and responsiveness
113
114Use these negative signals:
115
116- disappeared or abandoned account
117- stale one-way follow
118- off-priority topic cluster
119- low-value noise
120- repeated non-response
121- no follow-back when many better replacements exist
122
123Mutuals and real warm-path bridges should be penalized less aggressively than one-way follows.
124
125## Workflow
126
1271. Capture priorities, do-not-touch constraints, and selected platforms.
1282. Pull the current following / connection inventory.
1293. Score prune candidates with explicit reasons.
1304. Score keep candidates with explicit reasons.
1315. Use lead-intelligence plus research surfaces to rank expansion candidates.
1326. Match the right channel:
133 - X DM for warm, fast social touch points
134 - LinkedIn message for professional graph adjacency
135 - Apple Mail draft for higher-context intros or outreach
1367. Run brand-voice before drafting messages.
1378. Return a review pack before any apply step.
138
139## Review Pack Format
140
141```text
142CONNECTIONS OPTIMIZER REPORT
143============================
144
145Mode:
146Platforms:
147Priority Set:
148
149Prune Queue
150- handle / profile
151 reason:
152 confidence:
153 action:
154
155Review Queue
156- handle / profile
157 reason:
158 risk:
159
160Keep / Protect
161- handle / profile
162 bridge value:
163
164Add / Follow Targets
165- person
166 why now:
167 warm path:
168 preferred channel:
169
170Drafts
171- X DM:
172- LinkedIn:
173- Apple Mail:
174```
175
176## Outbound Rules
177
178- Default email path is Apple Mail / Mail.app draft creation.
179- Do not send automatically.
180- Choose the channel based on warmth, relevance, and context depth.
181- Do not force a DM when an email or no outreach is the right move.
182- Drafts should sound like the user, not like automated sales copy.
183
184## Related Skills
185
186- brand-voice for the reusable voice profile
187- social-graph-ranker for the standalone bridge-scoring and warm-path math
188- lead-intelligence for weighted target and warm-path discovery
189- x-api for X graph access, drafting, and optional apply flows
190- content-engine when the user also wants public launch content around network moves
191
In the file
SKILL.md834 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈100
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,275
on trigger
The instruction body, read only when the skill fires.
0.69%
of a 200k window
Ten skills this size would take about 7% of the window before you open a file.
050k100k150k200k context window

1.4k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 5.5 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md5.5 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$79 once
Connections Optimizer · MIT · affaan-m
one-time
Price$79 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Versionnot versioned
Publishedno release date on file
Price$79
Referenceaffaan-m/connections-optimizer

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v
  • No earlier releases have been published to the marketplace.
Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0