Menu

Individual skill

handle-linkedin-connection-request-signal

0upvotes

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through dedup / internal / relationship / ICP checks, attaches the signal to the CRM, and scores it with active-signal overrides: a decision maker at a serious company is MQL-eligible on this lone signal, a weak persona caps at the awareness tier, and a request from a closed-lost account is treated as a reactivation candidate rather than ignored. Every ICP-relevant outcome posts to a visibility channel; replies and accepts stay human. It never sends outreach.

skills/ariel-cohen/handle-linkedin-connection-request-signal/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 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)
237
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
Read excerpt

## Template placeholders

Replace every `{{...}}` before enabling. See the setup checklist reference for the full setup list.

- `{{PROFILE_OWNER}}` — Team member whose inbound connection requests are processed
- `{{CRM}}` — Your CRM (e.g. HubSpot, Attio)
- `{{INTERNAL_DOMAINS}}` — Your company domain(s); requests from these stop silently
- `{{VISIBILITY_CHANNEL}}` — Slack channel that gets one visibility post per processed request
- `{{CRM_HYGIENE_SKILL}}` — Sub-skill reference: how to create/update companies & contacts in your CRM
- `{{LEAD_SCORING_SKILL}}` — Sub-skill reference: your lead scoring & qualification methodology (its normal MQL alerting stays on)
- `{{REACTIVATION_SKILL}}` — Sub-skill reference: how you handle closed-lost account reactivation (optional — skip the reactivation branch's owner notification if you don't have one)
- `{{SELF_SERVE_THRESHOLD}}` — Company profile below which accounts route self-serve rather than MQL (default: fewer than 50 employees AND ≤$10M raised)
- `{{REACTIVATION_WINDOW}}` — Minimum time since a closed-lost deal before a request counts as a reactivation signal (default: ~90 days)
Back to top