agentleFS
prosyo-aiprosyo-ai/gtm-skill/skills/linkedin-profile-optimizer/SKILL.md

linkedin-profile-optimizer

Skill13 starsChanged 21 days agoMITView on GitHub

Use this skill when a seller, founder or SDR needs a LinkedIn profile that converts prospects instead of reading like a resume: \"optimise my LinkedIn profile\", \"rewrite my headline\", \"make my profile buyer-focused\", \"why don't prospects accept my requests\". Rewrites the headline, About section, featured items, banner message and experience entries around the buyer's problem and proof, and checks the profile from a prospect's point of view. Built for social selling and outbound.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use linkedin-comment-drafter, linkedin-content-planner and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sergebulaevSkill

    linkedin-comment-drafter

    Draft a LinkedIn comment on someone else's post from its URL, or reshare (repost) it to your feed with optional commentary. Use when the user pastes a post URL and asks to comment, engage, be first commenter, or repost with their thoughts. Produces 1-3 variants in the user's voice, picks a reaction, and publishes via Publora on approval. Not for replying to existing comments (use linkedin-reply-handler).

    Also in 7 projects that use this

  • sergebulaevSkill

    linkedin-content-planner

    Generate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post pillar, format, hook type, CTA, posting time, daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week or month of content, not draft a single post (use linkedin-post-writer).

    Also in 7 projects that use this

  • +9 more from sergebulaev

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 6

    Distinctive

    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:

    Use this before running LinkedIn outreach.

    line 16
  2. Distinctive:

    Read references/profile-templates.md for the About structure and three examples.

    line 33
  3. Distinctive:

    Read the top of the profile as a target buyer, on a phone, for five seconds.

    line 48
  4. Distinctive:

    MUST keep every claim true and approved for public use.

    line 59
  5. Distinctive:

    MUST write the first lines of the headline and About for the buyer.

    line 60
  6. Distinctive:

    NEVER invent clients, results or titles.

    line 61

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

Use this before running LinkedIn outreach. Prospects look at your profile before accepting or replying; a resume-style profile tells them you want something from them, a buyer-focused one tells them why talking to you is useful.

Inputs

  • The current profile text: headline, About, experience, featured.
  • Who you sell to and the problem you solve.
  • Proof: results, customers you can name, content you have made.

The play

1. Headline: who you help and with what

Formula: I help <who> <achieve outcome or fix problem> | proof or specialism. Under 220 characters, front-loaded because only the first part shows in search and invitations.

  • Resume: "Account Executive at Acme"
  • Buyer-focused: "Helping restaurant groups close payroll in a day, not a week | Account Executive at Acme"

2. About section: the buyer's story

Read references/profile-templates.md for the About structure and three examples. Short version:

  1. A first line about the reader's problem (only the first lines show before "see more").
  2. What you have seen working with people like them.
  3. How you help, in plain words.
  4. Proof: one or two results.
  5. A low-pressure invitation to talk.

3. Featured and banner

  • Banner: one line on what you help with, plus a visual cue of the product or result. Not a stock skyline.
  • Featured: a customer story, a useful resource and your best post. No product brochure as the first item.

4. Experience

Current role written for buyers: what customers get from working with you, not your quota attainment. Earlier roles: one line each unless they add credibility with this buyer.

5. The prospect test

Read the top of the profile as a target buyer, on a phone, for five seconds. Do they know who you help and why it matters to them?

What good looks like

  • The headline names the buyer and the outcome.
  • The first two lines of About are about the reader.
  • Proof is specific and true.
  • The common mistake is "President's Club 3x, 147% of quota", which impresses your manager and signals to buyers that they are a target.

Rules

  • MUST keep every claim true and approved for public use.
  • MUST write the first lines of the headline and About for the buyer.
  • NEVER invent clients, results or titles.

Example prompts

  • "Rewrite my LinkedIn profile. I'm an SDR selling cybersecurity to mid-market IT leaders."
  • "Give me 5 headline options for a founder selling to restaurant groups."
  • "Review my profile as if you were a VP Sales I'm prospecting."

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.