jirawatp/resume-career-toolkit / skills/linkedin-optimizer
LinkedIn Optimizer
VerifiedOptimize a LinkedIn profile for recruiter search visibility and professional branding. Use this skill when someone wants to improve their LinkedIn profile, write a LinkedIn headline, create a LinkedIn summary/about section, sync resume with LinkedIn, increase profile views, attract recruiters, or improve LinkedIn searchability. Trigger for any mention of LinkedIn, recruiter visibility, or professional social media optimization.
LinkedIn Optimizer
Make a LinkedIn profile findable by recruiters and compelling to visitors.
How LinkedIn Search Works
Recruiters search by job title, skills, location, and company. LinkedIn ranks results by profile completeness, keyword match, connection proximity, and activity. Optimization means placing the right keywords in the right fields.
Section-by-Section Guide
Headline (220 characters max)
The headline is the single most important field for search. It appears in every search result, connection request, and comment.
Formula: [Current or Target Title] | [Top 2-3 Skills or Specialties] | [Value Statement or Differentiator]
Weak: "Looking for new opportunities" Strong: "Senior Data Engineer | Python, Spark, AWS | Building Pipelines That Process 500M+ Events Daily"
Include the job title recruiters search for. If your official title is "Associate III" but the market calls it "Software Engineer", use "Software Engineer" in your headline.
About Section (2,600 characters max)
Only the first 300 characters show before the "see more" fold. The first line must hook the reader.
Structure:
- First line: One sentence stating what you do and why it matters
- Second paragraph: 2-3 sentences on your track record with specific numbers
- Third paragraph: Your key skills or specialties as a scannable list
- Final line: How to reach you or what you are looking for
Place keywords naturally throughout. The About section is indexed for search.
Experience Section
Unlike a resume, LinkedIn experience can be longer and more conversational. Include:
- A 2-sentence role summary explaining scope and context
- 4-6 achievement bullets with metrics (same quality as resume bullets)
- Relevant skills tagged to each role
- Media attachments if available (presentations, articles, press)
Skills Section
LinkedIn allows 50 skills. Use all 50. Order matters: the first 3 are "featured" and most visible.
Strategy: Start with the exact job titles and skills that recruiters search for. Fill remaining slots with supporting skills, tools, and methodologies.
Recommendations
Target 5-10 recommendations from a mix of managers, peers, and direct reports. Recommendations from managers carry the most weight.
To get them: write a recommendation for someone first, then ask if they would be willing to reciprocate. Provide 2-3 talking points they can reference.
Profile Completeness Checklist
- Professional headshot (profiles with photos get 21x more views)
- Custom background banner
- Headline with keywords (not just job title)
- About section filled (1,500+ characters)
- Current position with description and bullets
- At least 2 past positions
- Education listed
- 50 skills added
- 5+ recommendations received
- Featured section with 2-3 items
- 500+ connections
- Custom profile URL (linkedin.com/in/yourname)
Resume vs. LinkedIn Differences
- LinkedIn is broader: optimize for your industry, not one specific job
- LinkedIn is more personal: use first person, show personality
- LinkedIn is always on: keep it updated regardless of job search status
- LinkedIn allows multimedia: add presentations, articles, projects
- LinkedIn shows activity: commenting and posting increases visibility
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: 470k | 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 |