Need help implementing this on your team?
We'll install the skills, customize them to your workflow, and run the output through your team's combined LinkedIn network. Skills do the research, Linkd does the motion.
Drop in a LinkedIn URL or paste the profile text. The skill returns 3–5 specific hooks, every one tied to a quote from the source. The generic "saw you've been busy lately" stuff gets dropped, not dressed up.
Generic personalization is worse than none, it signals automation. Fabricated personalization (claiming experience they don't have, naming companies they never worked at) is a disqualifier that ends conversations before they start.
The skill scores each candidate hook on three dimensions: specificity (could this ONLY apply to this person?), recency (last 90 days = strong, 2+ years old = drop), and engageability (gives the user something to actually say, not just acknowledge).
Recent activity ranks highest, posts they authored, comments they engaged with, their Featured section. Static credentials like skills endorsements rank last. Everyone has those; referencing them signals automation.
Tries web_fetch first; falls back to pasted content when LinkedIn blocks. Tells you plainly when it can only see partial data.
Recent activity → career narrative → About/Headline → static credentials. In that priority. Everyone has skills; not everyone has a recent opinionated post.
Specificity, recency, engageability. Drops LOW-specificity hooks even if they're real. "Your impressive career in B2B SaaS" applies to millions.
Thin profile, no recent posts, partial fetch, surfaced as gaps. Doesn't fill them with invention.
Each hook ships with source, signal, an example opener, and a strength rating. Plus a "hooks not included and why" block.
If you can't see a "recent post about pricing", the skill won't claim there is one. Login-walled fetches get surfaced as such; nothing gets quietly paraphrased.
Degrees, certifications, skills endorsements. Everyone has them. Referencing them in cold outreach signals templated work, so the skill flags them as weak and won't lead with them.
Every hook ships with HIGH/MEDIUM/LOW specificity. The user picks which to use. Nothing gets silently promoted to "strong" to pad the count.
Health journeys, family situations, activism, layoffs, flagged and skipped. Never used as cold-outreach openers, even when they'd "personalize" well.
Three parts per hook: where it came from, what's specifically true about this person, one concrete way to open with it. Plus the draft opener so the user can decide whether the hook is actually usable.
The download is a zip containing two things: the .skill file (what you upload to Claude) and a SKILL.md sidecar (the human-readable instructions). Unzip first, then follow the steps for your Claude.
.skill file from the unzipped bundle..skill file too (it's also a zip).~/.claude/skills/web_search and file output enabled.This is exactly what Claude reads when the skill triggers. No hidden prompts, no separate config. What you see here is what you get.
We'll install the skills, customize them to your workflow, and run the output through your team's combined LinkedIn network. Skills do the research, Linkd does the motion.