agentleFS
prateeks367prateeks367/voicemoat-skills/skills/fix-my-linkedin-profile/SKILL.md

fix-my-linkedin-profile

Skill0 starsChanged 42 days agoMITView on GitHub

Go through headline, about and featured in the order a visitor reads them, and rewrite whichever one is losing the click. Use when someone asks for a profile review, has a new role or a new offer, says their profile gets views and nothing else, or wants their headline rewritten. Do not stuff keywords, do not promise search placement, and do not rewrite the parts that are already working.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Distinctive:

    Ask which of these dominates before rewriting anything.

    line 26
  2. Distinctive:

    Test it by reading it aloud directly after the person's name.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fix my LinkedIn profile

A profile is read in a fixed order by somebody who has already decided to be curious. They saw a post or a comment, they clicked the name, and now they are deciding in a few seconds whether this person is worth following.

Most profiles answer a different question. They are written as a CV, for a recruiter, in the third person, and the visitor who arrived from a post is not that reader.

Step 1: work out who lands here, and from where

The arrival changes what the first line has to do:

  • From a post or a comment. They liked one thing you said. The profile has to tell them whether there is more of it.
  • From search. They have a problem and are checking whether you solve it.
  • From a message or an introduction. They are checking whether to reply.
  • From your own link. They were sent, and the profile is a landing page.

Ask which of these dominates before rewriting anything.

Step 2: the headline

This is the only part that travels. It sits under your name on every post and every comment you leave, so it is read far more often than the profile itself.

It has two jobs: say what you do in the words the reader uses, and give them a reason to click. Common failures:

  • The job title alone, which means nothing outside the company
  • A row of nouns separated by pipes, which reads as a search query
  • An abstraction about helping people unlock their potential
  • Keywords packed in until the line stops being a sentence

Test it by reading it aloud directly after the person's name. If it does not survive being said out loud, it will not survive a feed.

Step 3: the first two lines of About

Everything after them is behind "see more", and most About sections open with a warm-up paragraph nobody gets past. Those two lines carry the whole section.

They should say who you help and what changes. Not your career history, which is what the experience section is for.

Step 4: the rest of About

In this order, in first person, in actual sentences: who you work with, what changes for them, the proof, and what to do next.

Proof means something checkable. A number you can source, a name you have permission to use, a thing somebody can go and read. Adjectives are not proof.

Step 5: featured

Three items at most, each earning its slot. Ask one question: if a stranger read exactly one thing here, which would you want it to be? Then check whether that thing is first.

Step 6: say what to leave alone

Name the parts that are already working and say why. A review that rewrites everything is not a review, and it usually ends with a profile that sounds less like the person than the one they started with.

What this will not do

It will not promise search placement. LinkedIn does not publish how its search ranks people, and anyone quoting you a formula for it is guessing.

It will not stuff keywords. A headline written for a matching algorithm reads exactly like one to the human who arrived from a post, and that human is the one who was going to follow you.

What changes when VoiceMoat is connected

A profile written in a voice the posts do not share is the mismatch a visitor notices first:

  • get_voice_profile gives your LinkedIn register, so the About section sounds like the post that brought them here.
  • get_voice_insights shows the subjects and patterns you actually publish on, which is usually a sharper answer to "what do you do" than the one people give when asked directly.
  • score_voice_match scores the rewritten About against your profile, which catches the drift into brochure voice that this exercise invites.

VoiceMoat also runs three free LinkedIn profile tools at voicemoat.com/tools: a headline analyzer, a headline generator and a summary generator. No account is needed for those either.

VoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.

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.