Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Li Inbox

ASecurity

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.

409 stars
0 votes
0 copies
0 views
Added 9/19/2026
ai-agentsgo

Works with

cli

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Li Inbox?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Li Inbox
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jakeschincariol-li-inbox/badge)](https://www.skillsdirectory.com/skills/jakeschincariol-li-inbox)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: li-inbox
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.
---

# 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.
```

Attribution

JakeschincariolJakeschincariol
View sourceMore from Jakeschincariol →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

1023331 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3331 votes

catchup

Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.

611 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →