# Li Inbox

Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters...

- Repository: https://github.com/Jakeschincariol/linkedin-agent-skill (3031 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-09-17
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -g -a claude-code -y`
Codex: `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -g -a codex -y`
Cursor: `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -g -a cursor -y`
Gemini CLI: `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Jakeschincariol/linkedin-agent-skill`

## Description

Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending. Use when the user says "my inbox is a mess", "triage my DMs", "should I reply to this", pastes a batch of LinkedIn messages, or is drowning in connection requests.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# li-inbox

Most LinkedIn inboxes are 80% noise, and the cost of that noise is that the
20% goes unanswered for a week. This skill separates them, then writes only
what is worth writing.

## Input

The user pastes the messages. Screenshots are fine. Do not log into their
account or read their inbox with a browser tool.

## Sort into five

| bucket | signal | action |
| --- | --- | --- |
| **LEAD** | describes a problem the user solves, or asks about working together | reply today, full answer |
| **RECRUITER** | a role, a company, a salary band | reply if the role is real, one line if not |
| **PEER** | someone in the same field with something to say | reply this week, keep it human |
| **ASK** | wants advice, time, an intro, a favour | reply if it is cheap and specific, decline cleanly if not |
| **SPAM** | agency pitch, lead-gen sequence, crypto, "quick question" with no question | archive, no reply |

Print the counts first. Seeing "3 leads, 2 recruiters, 41 spam" is most of the
value.

## Detecting a sequence

Automated outreach has a shape: an invite note with no specifics, a message
that arrives within minutes of the accept, "quick question", "I noticed you're
in {industry}", a calendar link in message one, then a bump exactly four days
later. When you see it, mark it SPAM and say which tell gave it away. The user
does not owe a reply to a script.

## Replies

The rest: https://github.com/Jakeschincariol/linkedin-agent-skill/blob/HEAD/skills/li-inbox/SKILL.md