Skip to content
cccskills
FreePublished on GitHub

linkedin-inbox

Triage a pasted batch of LinkedIn DMs and connection requests into lead, recruiter, peer, ask and spam, name the tell that gives away an automated sequence, and draft only the replies worth sending. Triggers: ordenar mis mensajes de LinkedIn, inbox de LinkedIn, le respondo a este recruiter, triage my DMs, connection requests.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3 stars(GitHub 3 + cccskills 0)
Works withLinkedIn

Run score Not tested

See how to install

Files included (1)

  • SKILL.md4.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

LinkedIn Inbox

Most inboxes are mostly noise, and the cost is that the messages that matter wait a week. This skill separates them, then writes only what is worth writing.

Phase 1: Input

The user pastes the messages or screenshots. Never log into the account or read the inbox with a browser. Read the Voice section and the target roles in 01-Perfiles/ so recruiter messages can be judged against what the user is looking for.

Phase 2: Sort

BucketSignalAction
RECRUITERA role, a company, a salary bandReply if the role is real and fits the target profile; one line if not
LEADDescribes a problem the user solves, or asks about working togetherReply today, full answer
PEERSame field, something to sayReply this week, keep it human
ASKAdvice, 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: "3 recruiters, 1 lead, 41 spam" is most of the value.

Phase 3: Spot sequences

Automated outreach has a shape: an invite with no specifics, a message minutes after the accept, "quick question", "I noticed you're in {industry}", a calendar link in message one, a bump exactly a few days later. Mark it SPAM and say which tell gave it away. The user does not owe a reply to a script.

Phase 4: Replies

  • RECRUITER, role worth it: ask what the message left out (salary band, level, remote or office, the stack) and say what makes the user a fit in one line. Log it in 05-Contactos/ and, when it becomes an application, hand off to /job-aplicar.
  • RECRUITER, not a fit: one line: not looking for this, happy to refer, and mean the refer.
  • LEAD: answer the actual question in full; if it fits, the offer is one sentence at the end.
  • ASK: under ten minutes and specific: do it. "Can I pick your brain": decline in one warm sentence and give the one answer you would have given on the call.
  • Declines are short, warm and final. No "let's revisit in Q3" if there is no Q3.
  • Never invent facts about the user's work. Stack, numbers, timelines and how something was built come from 01-Perfiles/Perfil Maestro.md or from the user. When a reply needs one that is missing, write {{...}} in its place and ask; a made-up detail in public is worse than a shorter reply.

Run every draft through /content-humanizer (.claude/skills/content-humanizer/scripts/humanize.py, then detect.py from the same folder).

Phase 5: Output

INBOX  ·  52 items  ·  2 RECRUITER, 1 LEAD, 4 PEER, 2 ASK, 43 SPAM

RECRUITER
@Ana López - Senior Backend at Acme
> Thanks, Ana. Sounds close to what I'm looking for. What's the salary band, and is it
> remote? I've spent the last two years on Go services at a similar scale.

SPAM  (43) - archive. 38 are the same sequence: no-specifics invite, "quick question"
within 4 minutes of the accept, calendar link in message one.

Protocol

  • The user sends every reply. The User Agreement (section 8.2) forbids bots and automated methods that send messages or add contacts.
  • Ask before writing to 05-Contactos/. Never store salary details or contact data in files that go to a remote without explicit confirmation.
  • Credit: adapted from Jake Schincariol's linkedin-agent-skill (MIT).

Next steps

  • /job-aplicar when a recruiter role turns into an application.
  • /cold-outreach for the follow-up if a recruiter goes quiet.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Plan, design, and implement A/B tests and experiments with statistical rigor. Covers hypothesis frameworks, sample sizing, metrics, and result analysis.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Web/mobile accessibility decision guide: WCAG 2.2 AA, ARIA, keyboard nav, focus management, contrast, testing. Use for: a11y, accessibility, wcag, aria, screen reader, keyboard, contrast.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Generate, iterate, and scale ad creative for paid advertising across Google, Meta, LinkedIn, and X. Covers platform specs, creative frameworks, and quality validation.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Musica interactiva para juegos: layering vertical, re-secuenciacion horizontal, stingers, reglas de transicion con sync points, y mapeo de estados de gameplay a musica. Usar para: musica adaptativa, sistema de musica dinamica, transiciones musicales, combat music.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Design multi-agent systems, create agent architectures, define communication patterns, and build autonomous agent workflows with structured evaluation frameworks.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, response formats, and quality loops.

The English summary is being prepared. Showing the original description.

SebastianLuser/claude-code-arcane3Updated Oct 27, 2026

See all skills by SebastianLuser

Report a problem with this skill