Canonical weighted graph-ranking layer for network-aware outreach.
Use this when the user needs to:
lead-intelligence or connections-optimizer
Choose this skill when the user primarily wants the ranking engine:
Do not use this by itself when the user really wants:
lead-intelligence
connections-optimizer
Collect or infer:
Given:
T = weighted target setM = your current mutuals / direct connectionsd(m, t) = shortest hop distance from mutual m to target t
w(t) = target weight from signal scoringBase bridge score:
B(m) = Σ_{t ∈ T} w(t) · λ^(d(m,t) - 1)
Where:
λ is the decay factor, usually 0.5
Second-order expansion:
B_ext(m) = B(m) + α · Σ_{m' ∈ N(m) \\ M} Σ_{t ∈ T} w(t) · λ^(d(m',t))
Where:
N(m) \\ M is the set of people the mutual knows that you do notα discounts second-order reach, usually 0.3
Response-adjusted final ranking:
R(m) = B_ext(m) · (1 + β · engagement(m))
Where:
engagement(m) is normalized responsiveness or relationship strengthβ is the engagement bonus, usually 0.2
Interpretation:
R(m) and direct bridge paths -> warm intro asksR(m) and one-hop bridge paths -> conditional intro asksR(m) or no viable bridge -> direct outreach or follow-gap fillWeight targets before graph traversal with whatever matters for the current priority set:
Weight mutuals after traversal with:
R(m).SOCIAL GRAPH RANKING
====================
Priority Set:
Platforms:
Decay Model:
Top Bridges
- mutual / connection
base_score:
extended_score:
best_targets:
path_summary:
recommended_action:
Conditional Paths
- mutual / connection
reason:
extra hop cost:
No Warm Path
- target
recommendation: direct outreach / fill graph gap
lead-intelligence uses this ranking model inside the broader target-discovery and outreach pipelineconnections-optimizer uses the same bridge logic when deciding who to keep, prune, or addbrand-voice should run before drafting any intro request or direct outreachx-api provides X graph access and optional execution paths