agentleFS
Sign inStart free
uplikauplika/uplika-plugin/skills/linkedin-profile-optimizer/SKILL.md

linkedin-profile-optimizer

Skill3 starsChanged 34 days agoMITView on GitHub

Audit and rewrite a LinkedIn profile end to end: headline, About, Featured, banner, photo, Experience, Skills, custom URL, recommendations.

20 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use linkedin-marketing.

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.
  • sergebulaevSkill

    linkedin-marketing

    Plan, draft, audit, and publish LinkedIn posts and comments. Use when the user wants to write a viral LinkedIn post, draft a comment or reply on any LinkedIn post URL, audit a draft against 2026 algorithm heuristics, remove AI tells, extract hook formulas from viral posts, or plan a week of content. Powered by the Publora API for publishing. User provides post/comment URLs, skill drafts content, user approves, then publishes.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If only a URL arrived and Handlus is not connected, ask for the text before scoring anything.

    line 28
  2. Distinctive:

    Never "passionate thought leader" / "driven professional" / "results-oriented" (profile-specific AI vocab)

    line 81
  3. Distinctive:

    Avoid wall-of-text. Use line breaks in About section

    line 82

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Adapted from sergebulaev/linkedin-skills (MIT). Not affiliated with the original author.

LinkedIn Profile Optimizer

Audit the nine components of a LinkedIn profile (photo, banner, headline, About, Featured, Experience, Skills, custom URL, recommendations) against 2026 best practices, then rewrite each section that needs it. Optimized profiles get ~3.9x more views and convert visitors 3-5x better than default/resume-style profiles.

When to use

  • User asks for an audit of their own profile, read through Handlus or pasted (see Input)
  • User wants to rewrite their headline, About section, or Featured section
  • User is launching a content strategy and needs the profile to match
  • Any of: "review my profile", "fix my headline", "optimize bio", "profile audit", "LinkedIn optimization"

Input

Read the user's own profile, or have it pasted. If Handlus is connected (see ../../references/handlus-read-layer.md), open https://www.linkedin.com/in/me/ in the user's own signed-in Chrome and read the headline, About, Experience and the other sections it shows, read only. Only the user's own profile: opening someone else's shows up in their viewer list. The Apify read layer has no profile actor, so without Handlus the user opens the profile, copies the sections and pastes them in. Screenshots of the visual parts work too.

  • Profile text: headline, About, Experience entries, Skills, custom URL
  • The visual three (photo, banner, Featured): screenshots, or a sentence describing each
  • Goal: clients / job seeking / authority, Featured and CTA vary by goal
  • Optional: draft content to grade against the existing profile

If only a URL arrived and Handlus is not connected, ask for the text before scoring anything. Never score a section you have not read or been shown, and never infer profile content from the URL slug.

Output

A structured audit + rewrite in this shape:

  1. Scorecard (9 sections, pass/fail/needs-work)
  2. Priority fixes (ranked by impact)
  3. Before → After rewrites for each failing section
  4. Expected uplift (based on benchmark data)

Steps

  1. Intake. Collect profile state + goal. If only a URL arrived, read it through Handlus (own profile only) or ask for the pasted text first. Flag missing sections.
  2. Score each of 9 sections against the checklist (see references/).
  3. Rewrite headline using [What You Do] | [Who You Help] [Achieve What Result], fit all 220 chars.
  4. Rebuild About with 7-step structure; verify first 265-275 chars hook before "see more".
  5. Curate Featured (3 strong items) matched to the goal:
    • Clients: lead magnet + case study with results + calendar link
    • Job seeking: portfolio + best work samples + top-performing post
    • Authority: best content + media/podcast features + newsletter signup
  6. Rewrite Experience bullets as action verb + specific metric. Add 5+ skills per role. Pin top 3 skills.
  7. Claim custom URL (linkedin.com/in/firstnamelastname, not the -123abc456 default).
  8. Draft recommendation requests with specifics ("about [project/skill]"), don't send LinkedIn's generic template.
  9. Deliver before/after diff + expected uplift (3.9x views, 3-5x conversion, 71% more likely to land interviews).

Nine-component scorecard

#SectionPass criteria (2026)
1Photo≥400x400, face fills 60% of frame, <3 years old, natural light, slight smile
2Banner1584x396, text in right 2/3, high contrast, includes value prop + CTA, tests well on mobile
3HeadlineUses all 220 chars; format `[What You Do][Who You Help] [Result]`
4About200-300 words, first-person, 7-step structure, hook in first 265-275 chars
5Featured3 items, matched to goal, custom 1200x627 thumbnails
6ExperienceEvery bullet = action verb + metric, 5+ skills per role, media attached
7Skills50 listed, top 3 pinned, mirrors target job descriptions, ≥1 endorsement each
8Custom URLlinkedin.com/in/firstnamelastname (not the default hash)
9RecommendationsAt least 3 recent, specific (not generic), from diverse contexts

Key benchmarks (from co.actor research)

  • Optimized About sections: 3.9x more views
  • 5+ listed skills: 3x more connection requests
  • Comprehensive profile: 71% more likely to land interviews
  • Featured section content: 30% longer viewing time
  • Personal founder profile vs company page: 315% more engagement, 270% more conversions

Hard rules

Global voice rules: see ../../references/voice-rules.md. Additional skill-specific rules:

  • First person ("I help...") never third person ("Jane is a passionate...")
  • Never "passionate thought leader" / "driven professional" / "results-oriented" (profile-specific AI vocab)
  • Avoid wall-of-text. Use line breaks in About section
  • 80% of users leave Featured empty. Filling it is a free edge

Reference files

  • references/profile-headline-formulas.md: 220-char formula + before/after examples
  • references/about-section-templates.md: 7-step structure with character budgets
  • references/featured-section-playbook.md: goal-matched content types
  • references/banner-photo-specs.md: dimensions, composition, mobile test
  • references/experience-skills-rules.md: bullet rewriting + skills strategy + custom URL + recommendations

Related skills

  • linkedin-content-planner: post pillars should echo the profile's headline/About thesis
  • linkedin-post-writer: Featured section rotates quarterly; pin your flagship post
  • linkedin-humanizer: scrub profile copy for the same AI tells we scrub from posts

Tools

None from Uplika. Uplika has no tool that reads or edits a LinkedIn profile; the profile is read through Handlus or pasted, and the user makes each change in LinkedIn.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free