analyze-performance
Use when user has been posting on LinkedIn at least 4 weeks and wants to know what is landing, run a quarterly content review, or diagnose dropping engagement.…
Use when user wants to send a LinkedIn message to one specific person rather than post publicly: a connection request note, cold outreach, warm intro reply, follow-up after no response, or reply to someone who DM'd them. Trigger phrases include "write a LinkedIn DM," "write a
$ npx -y skills add warpirate/linkedin-maxxing --skill write-dm --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/write-dmContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when user wants to send a LinkedIn message to one specific person rather than post publicly: a connection request note, cold outreach, warm intro reply, follow-up after no response, or reply to someone who DM'd them. Trigger phrases include "write a LinkedIn DM," "write a
name: write-dm description: | Use when user wants to send a LinkedIn message to one specific person rather than post publicly: a connection request note, cold outreach, warm intro reply, follow-up after no response, or reply to someone who DM'd them. Trigger phrases include "write a LinkedIn DM," "write a connection request," "I need to message [person]," "follow up on the message I sent," "reply to this person." license: MIT
Most LinkedIn DMs are either generic templates ("I'd love to connect and explore synergies") or so over-engineered with fake personalization that the recipient can smell the AI on first read. This skill exists to write DMs that sound like the user, are short enough to actually be read, and ask for something specific instead of dancing around it.
LinkedIn DM volume has exploded with AI-assisted outreach tools, and recipients are now numb to the standard patterns. The "I noticed you went to [school] and I also love [random shared interest], let's hop on a quick call" template is dead. Response rates on templated cold DMs have collapsed.
What still works: short, specific, honest messages from one person to another. This skill exists to write those, not to scale outreach.
Trigger when:
Do NOT trigger when:
1. **Who is the recipient?** Name, role, company, and any context the user has (how they know each other, what the recipient has posted recently, mutual connections, prior interactions). 2. **What is the user trying to get?** A response. A meeting. A specific piece of advice. A job referral. Be honest with yourself; the message will be honest with the recipient. 3. **What kind of message is this?** Connection request (300-char limit, see below), cold DM, warm reply, follow-up.
If voice-profile.md exists, read it. DMs should match the user's voice but in a slightly more direct register than posts.
A few format-specific things:
**Connection requests.** Limited to 300 characters. Most platforms cap personalized note slots, and even when present they should be used. A request with a real note has roughly 3-5x the acceptance rate of one without.
**Standard DMs.** No character limit, but anything over ~200 words is unlikely to be read in full. Aim for 50-150 words.
**Voice and video DMs.** Possible but rare. Skip unless the user specifically asks.
**InMail (Premium feature).** Same rules as a regular DM, slightly more polished register because InMail signals the sender paid for it.
**Be specific in the first sentence.** Not "I came across your profile and was impressed by your background." Specific means: a thing the recipient has done, a post they wrote, a project they shipped. Not generic praise.
**Get to the ask quickly.** A short DM that asks honestly performs better than a long DM that buries the ask. The recipient can decide quickly whether to engage.
**No fake intimacy.** "Hope you are doing well in these trying times" reads as a template even when sincere. Just start with the substance.
**No "quick call" without a reason.** If you ask for a 15-minute call, name what the call is for. "Could I ask you about how you approach X" gives the recipient something concrete to say yes or no to.
**Match the recipient's register.** Look at the recipient's posts. If they write casually, write casually. If they write formally, write formally. If they post in another language, ask the user if they want the DM in that language.
**One ask per message.** Asking for an intro AND advice AND a meeting in one DM signals desperation. Pick one. The others can come if the first lands.
1. Read voice-profile.md.
2. Identify the most specific true thing the user knows about the recipient. (A recent post, a project, a shared connection, a moment from a conference.) This is the opener.
3. State the ask honestly. What is the user actually asking for? A call, a referral, a reply, a piece of advice, an introduction. Say it directly.
4. End with the simplest next step. "Open to a 20-minute call next week?" "Happy to send a one-pager if you want to skim before deciding." Anything that makes the response one tap or one line.
Output must read as written by a human on the first pass. The constraints below are how you write, not a checklist to apply later. Do not narrate this process to the user. Do not show a "before humanizer / after humanizer" sequence. Just produce clean output.
**Hard bans — never appear in output:**
17 Claude Code skills + slash commands for substance-first LinkedIn growth. Profile audit, content drafting (posts, carousels, longform, video, DMs, comments), performance analysis, and a Wikipedia-based humanizer. Anti-template, anti-slop, open source, MIT.
Use when user has been posting on LinkedIn at least 4 weeks and wants to know what is landing, run a quarterly content review, or diagnose dropping engagement.…
Use when user wants to diagnose their current LinkedIn profile before rewriting it: they have not touched it in a while, get few profile views or recruiter…
Use when user has an idea with multiple discrete steps, a framework, a comparison, a before/after, a list of items worth a slide each, or anything where…
Use when user wants to post on LinkedIn but has no concrete idea, has a vague topic that needs a sharper angle, or uploads a work artifact (PR description,…
Use when editing or reviewing text that reads as AI-generated: symptoms include em dashes, "it's not X, it's Y" constructions, AI vocabulary (leverage, delve,…
Use when user wants to think strategically about LinkedIn content rather than post-by-post: starting a LinkedIn presence from scratch, posting feels scattered…