linkedin-profile-optimizer
Skill1 starsChanged 46 days agoMITView on GitHub
Rewrite the parts of a LinkedIn profile that decide whether people follow, hire or reply: About section, Featured items, banner copy and experience bullets. Use when the user asks for LinkedIn profile optimization, a LinkedIn summary or About section, a summary generator, experience bullets, banner text, or a LinkedIn profile review.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- uplika/uplika-plugintheir own version, first seen Nov 8, 2026
- gkmr/career-agent-kittheir own version, first seen Nov 8, 2026
- ZoolCoder/scoutjobstheir own version, first seen Nov 1, 2026
- 07001ec010shnk-svg/linkedin-agent-skillstheir own version, first seen Oct 25, 2026
- prosyo-ai/gtm-skilltheir own version, first seen Oct 25, 2026
- CodesbyFebin/linkedin-managertheir own version, first seen Oct 20, 2026
Used with
Projects with it also use linkedin-comment-drafter, linkedin-content-planner and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
sergebulaevSkilllinkedin-comment-drafter
Draft a LinkedIn comment on someone else's post from its URL, or reshare (repost) it to your feed with optional commentary. Use when the user pastes a post URL and asks to comment, engage, be first commenter, or repost with their thoughts. Produces 1-3 variants in the user's voice, picks a reaction, and publishes via Publora on approval. Not for replying to existing comments (use linkedin-reply-handler).
Also in 7 projects that use this
- sergebulaevSkill
linkedin-content-planner
Generate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post pillar, format, hook type, CTA, posting time, daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week or month of content, not draft a single post (use linkedin-post-writer).
Also in 7 projects that use this
- +9 more from sergebulaev
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- sergebulaev/linkedin-skills★ 5.4ksame name
- Paramchoudhary/ResumeSkills★ 2.1ksame name
- BrianRWagner/ai-marketing-skills★ 440same name
- BrianRWagner/ai-marketing-claude-code-skills★ 408same name
- az9713/ai-co-writing-claude-skills★ 61same name
- prosyo-ai/gtm-skill★ 13same name
- tstapler/dotfiles★ 8same name
- TaplioOfficial/taplio-linkedin-claude-skills★ 7same name
- opencue/cuecards★ 6same name
- ZoolCoder/scoutjobs★ 4same name
10 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Never invent employers, dates, numbers or credentials.
- Very specific: line 24
Use the linkedin-headline-generator skill (220 characters max).
- Distinctive: line 41
If the environment can render HTML to PNG (for example headless Chrome or Playwright), build it as a 1584×396 HTML page and screenshot it.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LinkedIn profile optimizer
People check a profile after they see a post or a comment. The profile should tell them in seconds who this person helps and why to follow or reach out. Write the copy; the user pastes it into LinkedIn themselves. This server publishes posts; it can't read or edit profiles.
Inputs to get first
- The goal: get hired (which role), win clients, build an audience, raise money, or hire.
- The audience and the keywords they'd search.
- Current profile text (ask the user to paste headline, About and recent roles).
- Real proof: results, clients, projects, credentials, links to show off.
Never invent employers, dates, numbers or credentials.
Headline
Use the linkedin-headline-generator skill (220 characters max).
About section (up to 2,600 characters)
- LinkedIn shows the first few lines before "see more", so open with who you help and what you do, not "I'm a passionate…".
- Structure: what you do and for whom (2–3 lines), how you do it or what makes it different, 3–5 proof points, a clear next step ("Email me at…", "DM me about…", "Book a call: link").
- Short paragraphs, first person, plain words. Include the keywords naturally.
- Bullets with "•" are fine. Skip Unicode bold here; screen readers and LinkedIn search handle it poorly.
Featured section
Suggest 3–5 items in priority order: the best post (the user can publish one with linkedin-post-writer), a case study or portfolio link, a lead magnet or booking link, a talk or press mention. Give each a short title and a one-line description.
Banner copy
- LinkedIn's recommended banner size is 1584×396 px. Keep text on the right two-thirds; the profile photo covers the lower left, and mobile crops the edges.
- One line: what you do for whom, or a clear offer. Optional second line: proof or a URL.
- If the environment can render HTML to PNG (for example headless Chrome or Playwright), build it as a 1584×396 HTML page and screenshot it. Otherwise give text and layout notes for a design tool.
Experience bullets
- 3–5 bullets per role, newest roles in most detail.
- Pattern: action verb, what you did, result or scope. For example: "Rebuilt onboarding emails; trial-to-paid rose from [X] to [Y]." Only real numbers; otherwise describe scope (team size, budget, markets).
- One line of context under the title for small or unknown companies.
Output
Return each section ready to paste, with character counts for the headline and About section. List what to change first. Tell the user to paste each section into their LinkedIn profile. Offer to write a post that sends people to the updated profile, which can be published with the postonce skill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.