Skip to content

borghei/Claude-Skills / tools/linkedin/linkedin-profile-optimizer

linkedin-profile-optimizer

Verified

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

references/experience-skills-and-credibility.md

View on GitHub
# Experience, Skills and Credibility

How to turn a CV-shaped work history into evidence, how to choose skills, and
how to earn the smaller trust signals (recommendations, public URL). Platform
details are current as of writing; verify them in the product.

## Contents

1. What the experience section is for
2. Anatomy of a role entry
3. Rewriting a duty into a result
4. When there is no number
5. What you are allowed to publish
6. Older roles, gaps and career changes
7. Skills: choosing, ordering, pruning
8. Recommendations
9. Public profile URL
10. Section-by-section review checklist

## 1. What the experience section is for

A CV is read by someone who has to read it. A profile is read by someone who
can leave. The experience section therefore has a narrower job than a CV: back
up the claims made in the headline and About, for the two or three roles a
visitor will actually open.

That changes what to write. The current role and the one before it carry almost
all of the weight. Anything older exists to show a coherent path, and one line
is usually enough.

## 2. Anatomy of a role entry

| Part | Content | Length |
|------|---------|--------|
| Remit line | What you owned and at what scale, in one sentence | One sentence |
| Result lines | What changed because you were there | Three to five for recent roles, one or two for older |
| Skills | The skills this role actually exercised, attached to the role | Three to five |
| Artefact | Something a visitor can open: a talk, a write-up, a launch page, a public repository | One is enough |

The remit line prevents a common failure: result bullets that are impressive
but leave the reader unsure what the job was. "Owned planning and systems for a
62-seller sales team" tells the reader how to weigh everything under it.

## 3. Rewriting a duty into a result

A duty says what the job description said. A result says what was different
afterwards. To convert one into the other, answer four questions about each
line.

| Question | What it produces |
|----------|------------------|
| What changed? | The verb |
| By how much? | The figure |
| Across what? | The scope: people, accounts, systems, regions |
| Over how long? | The period |

A result line needs the verb and at least one of the other three.

Converted examples (all invented):

| Duty as written | Result after four questions |
|-----------------|-----------------------------|
| Looked after onboarding for new customers | Cut time from contract to first use from 34 days to 11 across 80 accounts a year |
| Involved in the warehouse system replacement | Moved 3 warehouses to a new stock system in 5 months with no missed dispatch day |
| In charge of the support team | Grew support from 4 to 15 people while holding first-response time under an hour |
| Supported the annual audit | Reduced audit adjustments from 41 to 6 in two cycles by reconciling monthly instead of annually |
| Part of the pricing project | Designed the three-tier price list now used for every new contract |

Openers that signal a duty, and should start no line: responsible for, worked
on, helped, assisted, participated in, handled, tasked with, involved in,
supported, in charge of, contributed to. The auditor flags these (rule EX-04).

Verbs that name a change: built, cut, reduced, grew, replaced, moved, designed,
introduced, negotiated, recovered, shortened, opened, closed, wrote, launched.
Choose the plainest verb that is accurate. "Spearheaded" is not more
impressive than "led", only longer.

## 4. When there is no number

Many good roles produce no quotable figure. A line can still be specific.

| Substitute | Example |
|------------|---------|
| Scope | "Ran incident response for a platform serving every hospital in the region" |
| Frequency | "Published the weekly risk note the executive team read before every Monday meeting" |
| First or only | "First designer hired; set up the research practice the team still uses" |
| Named artefact | "Wrote the onboarding guide that became the company standard" |
| Before and after in words | "Took month-end from a process only one person understood to a documented checklist" |
| Adoption | "The review template I introduced is now used by all six product teams" |

What does not substitute for a number: adjectives ("significant",
"substantial"), and percentages with no base. "Improved efficiency by 40%"
with no statement of what was measured is weaker than a plain description.

## 5. What you are allowed to publish

A profile is public. Before a figure goes in, check three things.

- **Is it yours to share?** Revenue, churn, customer counts and customer names
  usually belong to the employer. Ask, or use scope instead.
- **Is it already public?** Figures in a press release, an annual report or a
  conference talk are safe to repeat with the same wording.
- **Is it accurate as stated?** A profile claim can be checked by a former
  colleague in seconds. Round down, not up, and claim your part of a team
  result, not the whole of it.

When in doubt, keep the scope and drop the figure. "Led the migration for a
62-seller team" reveals little; "grew revenue from 8.2M to 14.6M" may reveal a
great deal.

## 6. Older roles, gaps and career changes

- **Older than ten years:** title, employer, dates and at most one line. Detail
  here competes with recent proof for attention.
- **Several roles at one employer:** list them separately so progression is
  visible; put the detail on the latest.
- **Gaps:** an honest one-line entry (caring, study, travel, redundancy) reads
  better than unexplained missing years. No justification is needed.
- **Career change:** rewrite the remit lines of earlier roles to bring forward
  the part that transfers, without changing what the job was. A teacher moving
  into learning design did design courses; say so.
- **Side projects and volunteering:** include when they evidence a skill the
  target reader cares about and the main roles do not.

## 7. Skills: choosing, ordering, pruning

The skills section is a list of search terms that you vouch for. Treat it as
one.

**Choose** from the target reader's vocabulary. Collect the terms in five job
postings or five client briefs for the work you want; the terms that recur are
your candidates. Keep only the ones a role on your profile can evidence.

**Order.** The product lets you place a small number of skills at the top
(three, as of writing). Most visitors see only those. They should be the three
that best mirror your target terms, not the three with the most endorsements.

**Attach** each important skill to the role that used it. A skill evidenced by
a role is a claim with support; a skill in a bare list is an assertion.

**Prune.** Remove:

- tools you would not want to be hired for;
- skills not used in years;
- generic traits (teamwork, communication, leadership) that every profile
  lists and no one searches for on their own;
- near-duplicates that split endorsements across three spellings.

The product caps the list, and the cap has changed over time; check the current
figure. Filling the cap is not a goal. A focused list of fifteen to twenty-five
evidenced skills is easier to defend than a full list of everything touched
once.

**Endorsements.** Ask people who have seen the skill used. Do not trade
endorsements in bulk; a column of endorsements from people who never worked
with you is visible as exactly that.

## 8. Recommendations

A recommendation is useful when it describes a specific piece of work from a
specific vantage point. It is close to worthless when it says the person is
"a pleasure to work with".

**Who to ask.** Aim for different vantage points over time: someone you
reported to, someone who bought from you or was your client, a peer, someone
who reported to you. Two recent, specific ones outweigh ten old, general ones.

**How to ask.** Ask personally, outside the product's default request, and make
it easy to be specific. Give the person the project, the outcome and the aspect
of your work you would like them to speak to. Do not write it for them; a
recommendation in your own phrasing is recognisable.

A request you can adapt:

```
Hi [name], I'm updating my profile and would value a short recommendation
from you, since you saw the [project] work at close range.

If you're willing, the most useful thing would be a few sentences on
[the specific part: how the migration was planned / how the team was run /
what changed for your department]. Two or three sentences is plenty.

No pressure at all if the timing is bad.
```

**When to ask.** At the end of a project, on leaving a role, or when a client
has just told you something went well. Not in a batch of fifteen on one
afternoon.

**Giving them.** Write recommendations for others when you have something
specific to say. Do it because it is deserved, not as a trade.

## 9. Public profile URL

New profiles receive a URL ending in a string of letters and digits. The public
profile settings let you replace it with a readable one. Use your name; if it
is taken, add a middle initial or your field, not a number. It takes a minute
and it is what appears on a CV, an email signature and a slide.

## 10. Section-by-section review checklist

- [ ] Current role has a remit line and three to five result lines
- [ ] No line opens with duty language
- [ ] At least one line in three carries a figure, scope or before-and-after
- [ ] Every figure is accurate, attributable to you and cleared for publication
- [ ] Roles older than ten years are compressed to a line
- [ ] Top skill slots mirror the target terms
- [ ] Important skills are attached to the roles that evidence them
- [ ] Generic and unused skills removed
- [ ] At least two recommendations describe specific work, one from the last three years
- [ ] Public URL is name-based
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall