agentleFS
postzen-devpostzen-dev/linkedin-agent-skill/skills/li-profile/SKILL.md

li-profile

Skill3 starsChanged 30 days agoMITView on GitHub

Score a LinkedIn profile out of 100 against a 12-part rubric and rewrite the parts that lose points - headline, about, experience, featured, banner. Use when the user says "optimize my profile", "score my LinkedIn", "rewrite my headline", "fix my about section", or pastes their profile and asks how it reads.

7 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 1

    Common

    Most of the 7 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Ask the user to paste: headline, about section, current role and the last two experience entries, plus whether they have a banner and …

    line 19
  2. Very specific:

    Read rubric.json in this folder.

    line 26

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

li-profile

A profile is not a resume. A resume answers "what have you done". A profile answers "should I message this person", and it answers it in about four seconds, from the headline and the first two lines of the about.

Input

Ask the user to paste: headline, about section, current role and the last two experience entries, plus whether they have a banner and featured section. A screenshot of the top card is enough for the first pass. Do not log into LinkedIn on their behalf.

Score it

Read rubric.json in this folder. Twelve items, 100 points, each with what full marks looks like. Score every item, show the table, and give the total. Be honest - most profiles land in the 30s and 40s on the first pass, and a generous score is useless.

PROFILE SCORE  41/100

  headline            3/12   job title only, no outcome, no audience
  about first 2 lines 2/10   opens with "passionate about"
  about body          4/10   history, not offer
  featured            0/8    empty
  banner              0/6    default blue
  ...

Then rewrite, in this order

Fix in descending order of points lost. Do not rewrite everything at once - the user has to actually paste each of these in.

1. Headline (220 characters). The formula that works: {what you do for whom} | {proof} | {how to start}. Not your job title. Not "Helping X do Y" as the first three words, which every second profile now opens with. Give three options.

2. About, first two lines. Everything after line 2 is behind "see more" on mobile, so those two lines are the whole about section for most readers. They must state who you help and what changes. No "passionate", no "results-driven", no third-person bio, no opening with your own name.

3. About body. Written to one reader, in the second person. Structure: the problem they have, what you do about it, one piece of proof with a number, what to do next. Under 1,400 characters even though the limit is 2,600.

4. Featured. Three items: the best post, the proof asset, the way to contact. An empty featured section is eight points and the only place on the profile you fully control.

5. Experience. Each role gets one line of scope and two to three bullets that are outcomes with numbers, not duties. Cut anything older than ten years to a single line.

6. Banner. One sentence of positioning and one way to reach you. The default blue gradient is the clearest signal on the page that nobody is home.

Output

Score table, then the rewrites as copy-ready blocks in fix-first order, each one already run through /li-human. Re-score at the end and show the delta honestly - if the rewrite gets to 88 and not 98, say 88, and say what the remaining points need (usually recommendations, a real banner and posting history, none of which a rewrite can create).

Nothing is saved to LinkedIn by this skill. The user pastes each section in. That stays true with PostZen connected: PostZen publishes posts, it does not edit profiles.

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.