agentleFS
darkweb19darkweb19/skills/linkedin-profile/SKILL.md

linkedin-profile

Skill0 starsChanged 29 days agoApache-2.0View on GitHub

Use when someone wants their LinkedIn profile audited or rewritten — headline, About section, experience bullets, Featured, banner, recommendations — or says "fix my headline", "my profile gets views but nothing happens", "optimize my LinkedIn profile", "what should my About section say". Scores the headline on five dimensions, audits the whole profile 0-100 and ranks fixes by points per hour, and assembles an About section that survives the "…see more" fold.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    1. Audit before rewriting: Ask them to describe their profile section by section, or have them fill assets/profile_worksheet.md, then:

    line 23
  2. Distinctive:

    Never invent a credential, a metric, or a role: Every number on a profile is checkable by someone.

    line 65
  3. Very specific:

    If the audience answer is fuzzy, run positioning_brief.py there first.

    line 91

“Common” is measured: kept by at least 6 in 10 of the 4 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

LinkedIn Profile — audit, then rewrite the parts that pay

A profile is not a CV. A CV is read by someone who already decided to consider you; a profile is read by someone deciding whether to. Three readers, in descending volume: the scanner (three seconds, from your comment on someone else's post — sees photo and headline only), the evaluator (forty seconds — headline, half the About, Featured), the decider (minutes — everything). Almost all traffic is the scanner. Almost all conversion is the decider.

Workflow

1. Audit before rewriting. Ask them to describe their profile section by section, or have them fill assets/profile_worksheet.md, then:

python3 scripts/profile_completeness_auditor.py --input profile.json --output human

Exit 0 STRONG / 2 INCOMPLETE / 3 WEAK. It ranks every gap by points per hour and prints a first-hour plan — usually Featured, Open To, and skills, which cost minutes and recover real points. Start there, not with the About section they wanted to agonise over.

2. Headline next — it is the only string that travels. It rides along with every comment, search result, and invitation.

python3 scripts/headline_scorer.py --headline "..." --output human

Five dimensions at 20 points: audience, outcome, proof, searchability, clarity. Exit 0 SHIP (≥75) / 2 SHARPEN / 3 REWRITE. It also checks the 220-character cap and whether the first ~60 characters — the part that survives in search results and invitation previews — carry anything.

Iterate here. Two or three passes is normal; the stop condition is exit 0, or the user saying they would say it out loud to a peer.

3. About section — write to the fold. LinkedIn collapses it after roughly 265-300 characters. Collect the five parts from the user, then assemble:

python3 scripts/about_section_builder.py --input about.json --output human

It refuses a fold that cuts mid-sentence, a fold carrying no audience and no proof, a missing call to action, and anything over 2,600 characters.

4. Experience, Featured, recommendations. Rewrite duty lists as outcomes. Pin one artifact a stranger could evaluate in sixty seconds. Ask for two specific recommendations by naming the project and offering a first draft.

Rules

  • Never invent a credential, a metric, or a role. Every number on a profile is checkable by someone. If the proof does not exist, the claim is qualitative or it is absent.
  • First person. A profile in third person reads as a press release someone else wrote.
  • The fold is the section. Whatever sits above "…see more" is what most readers get.
  • Front-load the headline. The strongest segment first; everything after is a bonus.
  • Do not fetch anything. The user describes their own profile; nothing is scraped.

Scripts

ScriptRole
scripts/headline_scorer.pyHeadline 0-100 on audience / outcome / proof / searchability / clarity, plus the 220-char cap and front-load check.
scripts/profile_completeness_auditor.pyWhole profile 0-100 across 14 weighted checks; fixes ranked by points per hour with a first-hour plan.
scripts/about_section_builder.pyAssembles the About section from named parts and refuses a broken fold, a missing CTA, or an over-length section.

References and assets

  • references/profile_architecture.md — what each section is for, and the three readers (7 sources)
  • references/headline_and_positioning.md — the 220 characters that follow you everywhere (7 sources)
  • assets/profile_worksheet.md — fillable section-by-section worksheet
  • assets/example_profile.json — input shape for the auditor

Distinct from

  • linkedin-strategy — what to post and how often. This is who you are before you post. If the audience answer is fuzzy, run positioning_brief.py there first; the headline falls out of a good brief in ten minutes.
  • product-team/, c-level-advisor/ — career and role strategy. This writes the profile, not the career plan.

Version: 1.0.0

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.