Ak Dev New Messaging Integration
yaalalabs/agent-kernel
Step-by-step guide for adding a new messaging platform integration to Agent Kernel.
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending.
Install Li Inbox
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-inbox --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/li-inbox .claude/skills/li-inbox && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "li-inbox" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-inbox into .claude/skills/li-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-inbox", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-inboxType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-inbox --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/li-inbox .agents/skills/li-inbox && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "li-inbox" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-inbox into .agents/skills/li-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-inbox", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-inbox --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/li-inbox .cursor/skills/li-inbox && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "li-inbox" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-inbox into .cursor/skills/li-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-inbox", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Jakeschincariol/linkedin-agent-skill.git --path skills/li-inbox--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-inbox --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/li-inbox .gemini/skills/li-inbox && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "li-inbox" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-inbox into .gemini/skills/li-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-inbox", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-inboxInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/li-inbox .github/skills/li-inbox && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "li-inbox" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-inbox into .github/skills/li-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-inbox", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-inbox --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/li-inbox .opencode/skills/li-inbox && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "li-inbox" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-inbox into .opencode/skills/li-inbox/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-inbox", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
li-inbox- GitHub stars
- 1.7k
- Token cost
- ~723 tokens
- SKILL.md length
- 398 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending.
- The user says my inbox is a mess
- SKILL.md covers Input, Sort into five, Detecting a sequence and Replies, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Should I reply to this
What it does
Li Inbox is an agent skill from Jakeschincariol/linkedin-agent-skill. 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.
Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Email management, Recruiting and HR and Messaging and chat bots. It works with LinkedIn. The repository describes itself as: Eleven free Claude skills that run a LinkedIn account: posts off 21 hook formulas, comments, replies, profile score, weekly plan, and a humanizer that strips the AI fingerprint… The licence is MIT.
When your agent uses it
- The user says my inbox is a mess
- Should I reply to this
- Pastes a batch of LinkedIn messages
- Is drowning in connection requests
Example prompts
- “my inbox is a mess”
- “triage my DMs”
- “should I reply to this”
- “/li-inbox”
What it can do on your machine
Read from SKILL.md and the folder at commit add2c23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Li Inbox loads about 723 tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 398 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Jakeschincariol/linkedin-agent-skill at commit add2c23, republished under its MIT licence (© Jakeschincariol). 398 words, ~723 tokens.
Download SKILL.mdSave it as
.claude/skills/li-inbox/SKILL.md (or your agent's skills folder).- 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.
Show full SKILL.md (170 more words)Show less
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.© Jakeschincariol, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/li-inbox of Jakeschincariol/linkedin-agent-skill.
Open the folder on GitHubat commit add2c23
Compare with similar skills
Li Inbox next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Li Inbox this skillJakeschincariol/linkedin-agent-skill | 1.7k | — | ~723 | Automated safety check: Pass | MIT | |
| Ak Dev New Messaging Integrationyaalalabs/agent-kernel | 192 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| X Use Inboxihuzaifashoukat/x-use | 171 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Media WritershareAI-lab/lab-skills | 315 | — | ~870 | Automated safety check: Pass | Apache-2.0 | |
| X Dm Auto Chatbrowser-act/skills | 6.1k | — | ~3.9k | Automated safety check: Pass | MIT | |
| X Use Threadsihuzaifashoukat/x-use | 171 | — | ~725 | Automated safety check: Pass | MIT |
Similar skills
X Use Inbox
ihuzaifashoukat/x-use
Read X direct messages, triage inbox and request folders, send contextual reviewed messages, and inspect notifications with x-use.
Media Writer
shareAI-lab/lab-skills
Create platform-native content that resonates with each community's culture.
X Dm Auto Chat
browser-act/skills
X (Twitter) DM automated chat end-to-end Skill: scan DM inbox to identify pending-reply conversations, read message history, generate persona-based replies and send; also supports searching users…
X Use Threads
ihuzaifashoukat/x-use
Read visible X post/reply threads and prepare or resume multi-post drafts with x-use.
Engagement Inbox Manager
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"…
More from Jakeschincariol/linkedin-agent-skill
All 11 skills in this repoLi Audit
Jakeschincariol/linkedin-agent-skill
Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing.
Li Carousel
Jakeschincariol/linkedin-agent-skill
Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload.
Li Comment
Jakeschincariol/linkedin-agent-skill
Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot.
Li Dm
Jakeschincariol/linkedin-agent-skill
Write connection notes and DM follow-ups that get replies - the 200-character invite, the first message, and the two follow-ups.
Li Human
Jakeschincariol/linkedin-agent-skill
Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a five-check detection panel before it goes out.
Li Plan
Jakeschincariol/linkedin-agent-skill
Build the week on LinkedIn - what to post, when to post it, and who to engage with.
Related
Works with
Categories
Questions about Li Inbox
What does Li Inbox do?
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending. Li Inbox is an agent skill from Jakeschincariol/linkedin-agent-skill. Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending.
When should I use Li Inbox?
Li Inbox fits situations like: the user says my inbox is a mess; should I reply to this; pastes a batch of LinkedIn messages; is drowning in connection requests.
How do I install Li Inbox in Claude Code?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -a claude-code`. Or copy the skill folder (skills/li-inbox in Jakeschincariol/linkedin-agent-skill) into .claude/skills/li-inbox in your project. Claude Code loads it when a task matches its description.
How do I install Li Inbox in Codex?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -a codex`. Or copy the skill folder (skills/li-inbox in Jakeschincariol/linkedin-agent-skill) into .agents/skills/li-inbox in your project. Codex loads it when a task matches its description.
Can I use Li Inbox in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-inbox -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/li-inbox, .gemini/skills/li-inbox, .github/skills/li-inbox and .opencode/skills/li-inbox in your project.
What does Li Inbox need to run?
SKILL.md names no scripts, command-line tools or credentials: Li Inbox is instructions for the agent only.
Does Li Inbox access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Li Inbox safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Li Inbox use?
Li Inbox is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Li Inbox use?
About 723 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Li Inbox?
Skills that share tags, products or a category with Li Inbox: Ak Dev New Messaging Integration (yaalalabs/agent-kernel, 192 stars), X Use Inbox (ihuzaifashoukat/x-use, 171 stars), Media Writer (shareAI-lab/lab-skills, 315 stars) and X Dm Auto Chat (browser-act/skills, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Li Inbox?
Jakeschincariol (a GitHub user) maintains it in Jakeschincariol/linkedin-agent-skill, which has 1,688 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 17, 2026.
Source: Jakeschincariol/linkedin-agent-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.