update-linkedin-for-a-career-change
Skill0 starsChanged 4 days agoMITView on GitHub
Rewrite a LinkedIn profile (headline, About section, experience and featured work) for the job someone wants next, and choose who to ask for references. Use for "update my LinkedIn for a career change", "write my LinkedIn headline", "LinkedIn About section" or "who should I ask for a reference".
In this repository17 other files it gives its agents.
- after-a-layoffSkill
- answer-application-questionsSkill
- choose-a-path-as-a-studentSkill
- find-career-directionsSkill
- follow-up-on-applicationsSkill
- future-proof-against-aiSkill
- go-public-after-a-layoffSkill
- informational-interviewsSkill
- negotiate-a-job-offerSkill
- plan-a-career-changeSkill
- prepare-for-interviewSkill
- return-to-work-after-a-breakSkill
- share-your-work-in-publicSkill
- start-a-new-jobSkill
- tailor-cv-to-jobSkill
- test-a-careerSkill
- write-cover-letterSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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
- Distinctive: line 17
Featured: put new-field evidence near the top, such as a case study, a prototype, a write-up or a portfolio link.
- Distinctive: line 18
Experience: keep the titles true; rewrite two or three bullets per role to show the transferable work, with results where they exist.
- Distinctive: line 25
Ask people who have seen their work recently and can describe it in detail: ideally a current or recent manager, then a senior colleague, …
- Distinctive: line 29
Never invent titles, employers, dates or results.
- Distinctive: line 30
Keep their voice: plain words, no buzzwords.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Update a LinkedIn profile for a career change
A profile for a career change is written for the job they want, while staying true about the job they have.
How to rewrite it
- Headline: the target role plus the bridge. For example: "Operations lead moving into product: shipping internal tools teams actually use". Not "Seeking opportunities".
- About section, three short paragraphs in the first person:
- What they do now that the new field needs, in the new field's words.
- The evidence they've built in the new direction: a project, a course with a finished piece of work, a test they ran.
- What they're looking for and how to reach them.
- Featured: put new-field evidence near the top, such as a case study, a prototype, a write-up or a portfolio link.
- Experience: keep the titles true; rewrite two or three bullets per role to show the transferable work, with results where they exist.
- Skills: list the ones the target job posts ask for, but only those they can show.
Show every rewritten section as before and after.
References
Ask people who have seen their work recently and can describe it in detail: ideally a current or recent manager, then a senior colleague, client or project lead. Ask before listing them, and tell them about the role so they know what to highlight.
Rules
- Never invent titles, employers, dates or results.
- Keep their voice: plain words, no buzzwords.
If the OffLadder tools are connected
find_career_guide covers LinkedIn for a career change, who to ask for a reference, and CVs for a career change.
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.

