davepoon/buildwithclaude / plugins/all-skills/skills/linkedin-profile-refresh
linkedin-profile-refresh
VerifiedRefresh a LinkedIn profile for a job search from the user's own resume — pick and check the profile photo, crop it locally to LinkedIn, Slack and GitHub sizes, and write a headline and About section grounded in the resume, then check that LinkedIn, GitHub and the resume tell the same story. Use when the user asks to "update my LinkedIn", "write my LinkedIn headline/About", "is this a good LinkedIn photo", "resize my headshot for LinkedIn", or shares a resume or profile photo for job-search feedback. Uses the free ProfessionalHeadshot.io MCP for official photo specs and photo scores when connected; works without it.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.1 KB |
| SKILL.md | skill md | 4.9 KB |
| references/headline-and-about.md | markdown | 1.1 KB |
| references/photo-checklist.md | markdown | 1.5 KB |
| references/platform-specs.md | markdown | 1.3 KB |
| references/report-template.md | markdown | 547 B |
| scripts/crop_headshot.py | script | 4.7 KB |
references/headline-and-about.md
View on GitHub# Headline and About
## Facts first
- Every claim must come from the resume or the user's messages. Never invent employers, titles, numbers, certifications, or tools.
- Keep the user's numbers exactly as given. If a number is missing, write the sentence without one and ask for it — do not estimate.
- Mark inferred labels (for example "Senior") with [confirm].
## Headline (LinkedIn allows up to 220 characters)
Pattern: role or target role | specialty or domain | one proof point or audience.
- Lead with the words a recruiter would search for the target role.
- One proof point beats a list of adjectives.
- Avoid: "passionate", "guru", "ninja", "results-driven", emoji strings, "open to work" (LinkedIn has a separate feature for that).
## About
Three short paragraphs, first person, under ~1,500 characters (LinkedIn allows 2,600):
1. What you do and for whom, in one or two sentences.
2. Two or three concrete results from the resume, with the user's numbers.
3. What you are looking for next and how to reach you (if the user wants that public).
End with 5–8 skills the user actually listed, as plain words, not hashtags.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |