agentleFS
Sign inStart free
postzen-devpostzen-dev/linkedin-agent-skill/skills/li-inbox/SKILL.md

li-inbox

Skill3 starsChanged 30 days agoMITView on GitHub

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.

7 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 2 are common, 0 are distinctive, and 0 are very specific to this project.

  • 2

    Common

    Most of the 7 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    RECRUITER: - if the role is genuinely interesting, ask the three things the message left out: comp band, level, and whether it is in-office.

    line 50
  2. Common:

    ASK: - if it costs under ten minutes and is specific, do it.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

PostZen cannot read the LinkedIn inbox or send messages yet (waiting on LinkedIn's approval), so this stays paste-based even with PostZen connected.

Sort into five

bucketsignalaction
LEADdescribes a problem the user solves, or asks about working togetherreply today, full answer
RECRUITERa role, a company, a salary bandreply if the role is real, one line if not
PEERsomeone in the same field with something to sayreply this week, keep it human
ASKwants advice, time, an intro, a favourreply if it is cheap and specific, decline cleanly if not
SPAMagency pitch, lead-gen sequence, crypto, "quick question" with no questionarchive, 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free