Li inbox skill
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending.
by Jakeschincariol·MIT license·★ 1,856 Stars on the repo·GitHub ↗
Use now
npx degit Jakeschincariol/linkedin-agent-skill/skills/li-inbox#main ~/.claude/skills/li-inboxChecked ·commit main
Inside this skill
SKILL.md · the author's own words# 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 |
Word-for-word excerpt, not a result. Read the full SKILL.md ↓
Files of Li inbox
SKILL.md
Show the full text68 lines
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
- LEAD - answer the actual question in the message, in full, for free. If it is a fit, the offer is one sentence at the end. If it is not, say so and point them somewhere useful. Both outcomes are good.
- RECRUITER - if the role is genuinely interesting, ask the three things the message left out: comp band, level, and whether it is in-office. If it is not, one line: not looking, happy to refer, and mean the refer.
- ASK - if it costs under ten minutes and is specific, do it. If it is "can I pick your brain", decline in one warm sentence and give them the one answer you would have given on the call. That is the polite version and it is also the more useful one.
- DECLINES are short, warm and final. No "let's revisit in Q3" if there is no Q3.
Output
Grouped by bucket, counts first, drafts only for the buckets that get replies, each one humanized. Then the gate: the user sends them.
INBOX · 52 items · 3 LEAD, 2 RECRUITER, 4 PEER, 2 ASK, 41 SPAM
SPAM (41) - archive. 38 are the same sequence: no-specifics invite,
"quick question" within 4 minutes of accept, calendar link in message one.
| 1 | |
| 2 | name li-inbox |
| 3 | description >- |
| 4 | Triage the LinkedIn inbox - sort connection requests and DMs into leads, |
| 5 | recruiters, peers and spam, and draft the replies worth sending. Use when the |
| 6 | user says "my inbox is a mess", "triage my DMs", "should I reply to this", |
| 7 | pastes a batch of LinkedIn messages, or is drowning in connection requests. |
| 8 | |
| 9 | |
| 10 | # li-inbox |
| 11 | |
| 12 | Most LinkedIn inboxes are 80% noise, and the cost of that noise is that the |
| 13 | 20% goes unanswered for a week. This skill separates them, then writes only |
| 14 | what is worth writing. |
| 15 | |
| 16 | ## Input |
| 17 | |
| 18 | The user pastes the messages. Screenshots are fine. Do not log into their |
| 19 | account or read their inbox with a browser tool. |
| 20 | |
| 21 | ## Sort into five |
| 22 | |
| 23 | | bucket | signal | action | |
| 24 | | --- | --- | --- | |
| 25 | | **LEAD** | describes a problem the user solves, or asks about working together | reply today, full answer | |
| 26 | | **RECRUITER** | a role, a company, a salary band | reply if the role is real, one line if not | |
| 27 | | **PEER** | someone in the same field with something to say | reply this week, keep it human | |
| 28 | | **ASK** | wants advice, time, an intro, a favour | reply if it is cheap and specific, decline cleanly if not | |
| 29 | | **SPAM** | agency pitch, lead-gen sequence, crypto, "quick question" with no question | archive, no reply | |
| 30 | |
| 31 | Print the counts first. Seeing "3 leads, 2 recruiters, 41 spam" is most of the |
| 32 | value. |
| 33 | |
| 34 | ## Detecting a sequence |
| 35 | |
| 36 | Automated outreach has a shape: an invite note with no specifics, a message |
| 37 | that arrives within minutes of the accept, "quick question", "I noticed you're |
| 38 | in {industry}", a calendar link in message one, then a bump exactly four days |
| 39 | later. When you see it, mark it SPAM and say which tell gave it away. The user |
| 40 | does not owe a reply to a script. |
| 41 | |
| 42 | ## Replies |
| 43 | |
| 44 | **LEAD** - answer the actual question in the message, in full, for free. If |
| 45 | it is a fit, the offer is one sentence at the end. If it is not, say so and |
| 46 | point them somewhere useful. Both outcomes are good. |
| 47 | **RECRUITER** - if the role is genuinely interesting, ask the three things |
| 48 | the message left out: comp band, level, and whether it is in-office. If it |
| 49 | is not, one line: not looking, happy to refer, and mean the refer. |
| 50 | **ASK** - if it costs under ten minutes and is specific, do it. If it is |
| 51 | "can I pick your brain", decline in one warm sentence and give them the one |
| 52 | answer you would have given on the call. That is the polite version and it |
| 53 | is also the more useful one. |
| 54 | **DECLINES** are short, warm and final. No "let's revisit in Q3" if there is |
| 55 | no Q3. |
| 56 | |
| 57 | ## Output |
| 58 | |
| 59 | Grouped by bucket, counts first, drafts only for the buckets that get replies, |
| 60 | each one humanized. Then the gate: the user sends them. |
| 61 | |
| 62 | |
| 63 | INBOX · 52 items · 3 LEAD, 2 RECRUITER, 4 PEER, 2 ASK, 41 SPAM |
| 64 | |
| 65 | SPAM (41) - archive. 38 are the same sequence: no-specifics invite, |
| 66 | "quick question" within 4 minutes of accept, calendar link in message one. |
| 67 | |
| 68 |
Discussion
Browse more free Claude skills.