사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/jakeschincariol/linkedin-agent-skill --skill li-inbox시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
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.
