borghei/Claude-Skills / tools/linkedin/linkedin-profile-optimizer
linkedin-profile-optimizer
VerifiedAudits and rewrites a LinkedIn profile from pasted text: headline, About, experience, skills, Featured, banner and photo. Use when reviewing a profile, fixing a headline or About, or preparing a profile before posting more.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.3 KB |
| assets/profile_rewrite_worksheet.md | markdown | 4.3 KB |
| assets/profile_template.json | config | 1.5 KB |
| assets/sample_profile.json | config | 2.4 KB |
| assets/sample_profile_rewritten.json | config | 4.7 KB |
| references/experience-skills-and-credibility.md | markdown | 9.6 KB |
| references/featured-and-visuals.md | markdown | 9.4 KB |
| references/headline-and-about.md | markdown | 10.7 KB |
| scripts/profile_auditor.py | script | 15.1 KB |
| scripts/profile_rules.py | script | 15.2 KB |
references/headline-and-about.md
View on GitHub# Headline and About
The two pieces of profile text that do most of the work, and how to write them.
Everything here is editorial judgement plus a few platform mechanics. The
mechanics (character limits, where text is cut off) are current as of writing;
verify them in the product before treating them as fixed.
## Contents
1. Where each piece of text is actually read
2. The headline: three blocks
3. Headline patterns by goal
4. Three tests before a headline ships
5. The About section: five moves
6. Writing the preview
7. Search terms without keyword stuffing
8. Worked example
9. Editing checklist
## 1. Where each piece of text is actually read
Most people who read a headline never visit the profile. The headline travels:
it appears under the name beside every comment, in search results, in
connection requests, in "people also viewed" lists and in message previews. In
most of those places it is cut short, often to a single line on a phone.
Two consequences follow.
- The headline is written for a reader who has no other context. It cannot rely
on the banner, the About or the employer's reputation to explain it.
- The opening words matter far more than the rest. Whatever is in the first
line on a small screen is the whole headline for most readers.
The About section is the opposite. Only profile visitors see it, and they see a
short preview with a control to expand it. The preview decides whether the rest
is read. The exact cut-off varies by device and changes over time; the auditor
assumes about 260 characters and lets you change that with `--about-preview`.
## 2. The headline: three blocks
A headline is assembled from blocks. Use two or three; four is usually one too
many.
| Block | Job | Good raw material | Bad raw material |
|-------|-----|-------------------|------------------|
| Anchor | Makes you findable and classifiable | The role or field in the words a searcher types | An internal job title nobody outside the company uses |
| Audience | Tells the right reader "this is for you" | A role, a sector, a company stage | "businesses", "people", "organisations" |
| Reason | Gives a ground for believing the first two | An outcome you produce, a scale you have worked at, a named artefact | Adjectives about yourself |
| Specialism (optional) | Narrows the field | A method, a tool, a niche | A second and third job title |
Order the blocks by what the truncated version needs to say. If you want to be
found for a role, the anchor goes first. If you want prospects in a comment
thread to recognise themselves, the audience goes first.
**Recommendation:** keep the anchor. Advice to drop the job title entirely in
favour of a benefit statement produces headlines that read well and cannot be
found, and it makes the reader work out what you actually are. The fix for a
title-only headline is to add blocks, not to remove the title.
On the current employer: include it when the name does work for you (it is
known to your audience, or it is the thing you are hiring for). Leave it out
when it is the only thing in the headline, because the experience section
already shows it.
On length: the limit is 220 characters as of writing. A headline does not need
to fill it. It needs enough room for the second and third block, which a
forty-character title does not leave.
## 3. Headline patterns by goal
These are shapes, not templates to paste. Write the blocks first, then pick the
order.
| Goal | Lead with | Follow with | Avoid |
|------|-----------|-------------|-------|
| Clients | Audience or the problem you fix | Anchor, then one proof point | Listing every service |
| Job search | Anchor in the exact wording of the roles you want | Scale or domain, then a specialism | "Seeking new opportunities" as the whole headline |
| Authority | The subject you are known for | Anchor, then the vehicle (book, newsletter, talk series) | Self-awarded titles |
| Hiring | Anchor and employer | What the team is building, then "hiring" plus the role family | A bare "We're hiring!" with no indication of what for |
Illustrations with invented people:
- Clients, audience first: "Finance teams closing the month in spreadsheets |
I rebuild the close so it takes 4 days, not 12 | Fractional controller"
- Job search, anchor first: "Staff backend engineer, payments and ledgers |
Go, Postgres, event-driven systems | Previously led settlement at a 300-person fintech"
- Authority, subject first: "Writing about how hospitals buy software |
Health-tech procurement adviser | Author of a weekly procurement briefing"
- Hiring, employer first: "Engineering manager at Corrin Freight | Building
route planning for regional hauliers | Hiring backend and data engineers"
## 4. Three tests before a headline ships
**The comment-thread test.** Cover everything after the first sixty characters.
Does what remains say something a stranger can use? If the visible part is
"Helping ambitious companies unlock sustainable", it fails.
**The swap test.** Could a competitor, or anyone with the same title, paste the
headline onto their own profile without changing a word? If yes, it contains no
information about you. Add the block that only you could write.
**The search test.** Write down the phrase your target reader would type into
search. Is that phrase, or its obvious short form, in the headline? Being
discoverable for a term you never use is not something to count on.
## 5. The About section: five moves
Think of the About as an argument in five moves. Each move has one job, and the
section is finished when all five are present, not when a word count is hit.
| Move | Job | Rough share of the text | Fails when |
|------|-----|-------------------------|------------|
| Stake | Give the visitor a reason to expand the section | The preview | It opens with a greeting, a biography or the year you graduated |
| Fit | Say who you work with and in what situation | A short paragraph | The audience is "companies of all sizes" |
| Proof | Show two or three things that happened | The largest part | Every claim is an adjective |
| Method | Describe what working with you is like | A short paragraph | It becomes a list of services |
| Door | Ask for one action | One or two sentences | It ends with "feel free to connect" |
A sixth, optional move is a human detail: one line about life outside work. It
earns its place when it is specific and brief. It does not replace proof.
Write in the first person. A profile written as "Jordan is an accomplished
leader who..." reads as though somebody else wrote it, because somebody else
usually did. First person is also shorter.
Length: long enough for all five moves, short enough that proof is not buried.
For most people that is somewhere between a hundred and fifty and three hundred
and fifty words. The product caps the field (2,600 characters as of writing);
if you are near the cap you have written a CV.
## 6. Writing the preview
The preview is the stake. Four openings that work, and what each needs:
| Opening | Needs | Example with an invented detail |
|---------|-------|---------------------------------|
| The reader's problem | You must know the problem precisely | "Most month-end closes take twelve days because three people re-key the same numbers." |
| A result | A real figure you can stand behind | "I have taken four finance teams from a twelve-day close to four." |
| A position | Something a reasonable peer would disagree with | "Month-end should be boring. If yours is dramatic, the process is wrong, not the team." |
| A plain statement of fit | A narrow, recognisable audience | "I work with finance leads at 50 to 300 person companies who have outgrown their spreadsheets." |
Openings that waste the preview: a welcome, a thank-you for visiting, a list of
adjectives, a statement of years of experience, a quotation, a restatement of
the headline.
After drafting, read only the preview on a phone. If it ends mid-clause in a
way that makes the reader want the rest, good. If the stake arrives after the
cut, move it up.
## 7. Search terms without keyword stuffing
Pick two to four terms a real searcher would use. Find them by reading how your
audience describes what they need: job postings for the roles you want, the
wording clients used in their first message to you, the session titles at the
events your audience attends.
Place them where they read naturally:
- one in the headline, in the first half;
- each of them once in the About, inside an ordinary sentence;
- each of them in the skills list, where repetition is expected.
Do not end the About with a "Specialties:" line that lists twenty terms. It
reads as padding, and whether it affects ranking is not something you can
verify from outside. Terms in sentences cost nothing and survive any change to
how search works.
## 8. Worked example
An invented profile, before:
> Dedicated finance professional with over 12 years of experience across
> multiple industries. Strong communicator and team player with a passion for
> process improvement. Open to connecting with like-minded professionals.
What is wrong, move by move: no stake (the preview is adjectives); no fit
("multiple industries"); no proof; no method; a door that asks for nothing.
After, in five moves:
> Most month-end closes take twelve days because three people re-key the same
> numbers. I take finance teams to a four-day close without replacing their
> ERP.
>
> I work with finance leads at companies of 50 to 300 people, usually just
> after the first audit that went badly.
>
> Recent work: a logistics company went from a 13-day close to 4 in two
> quarters. A software company cut its audit adjustments from 41 to 6. A
> charity produced board accounts on time for the first time in three years.
>
> I start with a two-week review of where the days actually go, then fix the
> three largest causes with your team, not around them.
>
> If your close takes more than a week, message me with your ERP and team size
> and I will tell you what I would look at first.
Every figure in that text would need to be true and publishable. If a figure
cannot be published, keep the scope ("a 200-person logistics company") and drop
the number rather than inventing a rounder one.
## 9. Editing checklist
Validate the draft against each line before it goes live.
- [ ] Headline keeps a searchable anchor and adds at least one more block
- [ ] First sixty characters of the headline stand alone
- [ ] No self-description that a competitor could reuse unchanged
- [ ] About is in the first person
- [ ] The stake is inside the preview on a phone
- [ ] Fit names an audience narrow enough to exclude someone
- [ ] Proof contains at least two specifics, each one true and cleared for publication
- [ ] Method says what happens first
- [ ] Door asks for one action and says what to send
- [ ] Target terms appear in sentences, not in a trailing list
- [ ] Limits re-checked in the product on the day of publishing
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |