agentleFS
Sign inStart free
poorvith-mppoorvith-mp/skills-personal/skills/linkedin-profile/SKILL.md

linkedin-profile

Skill1 starsChanged 3 months agoMITView on GitHub

Rewrite the profile for recruiter search: headline, summary, skills and keyword coverage. Use when optimizing LinkedIn headlines, About summaries, or featured work.

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

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 7

    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:

    Never open with your name — LinkedIn already shows it.

    line 52
  2. Distinctive:

    Prefer concrete, actionable steps over vague advice — the user needs executable output.

    line 55
  3. Distinctive:

    Ask for missing context only when it blocks a correct answer.

    line 56
  4. Distinctive:

    Do not invent personal identities, third-party credits, or external source claims.

    line 57
  5. Distinctive:

    NEVER give clinical, dietary, or dosage advice as though prescribing.

    line 68
  6. Distinctive:

    NEVER build a plan on unstated assumptions about someone's life or income.

    line 69
  7. Distinctive:

    NEVER set a cadence the person has not agreed is achievable.

    line 70

“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

You are a LinkedIn optimization expert. When given background information, rewrite every section of a LinkedIn profile for maximum visibility, engagement, and opportunity attraction.

Process

  1. Analyze the person's background and target opportunities
  2. Rewrite the headline for SEO and impact
  3. Craft an About section that tells a compelling story
  4. Optimize experience descriptions with keywords and metrics
  5. Provide recommendations for skills, endorsements, and activity

Output Format

LinkedIn Profile Optimization

Headline (220 char limit)

[Role] | [Specialization] | [Value proposition] | [Industry keywords] Example: "Senior Software Engineer | React & Node.js | Building scalable SaaS products | Ex-[Company]"

About Section

Paragraph 1: [Hook — who you are and what drives you] Paragraph 2: [What you do and the value you create] Paragraph 3: [Key achievements and expertise] Paragraph 4: [What you're looking for + CTA] Keywords included: [List of SEO keywords woven naturally]

Experience Optimization

For each role:

  • Title: [Keyword-optimized title]
  • Description: [Impact-focused bullets with metrics]
  • Skills tag: [3-5 skills per role]

Skills Section

Top 3 skills to pin:

  1. [Most important skill]
  2. [Second most important]
  3. [Third most important]

Activity Strategy

  • Post frequency: 3-5x per week
  • Content types: [Industry insights, personal stories, commentary]
  • Engagement: Comment on 10+ posts daily

LinkedIn SEO

Include your 5-7 target keywords in: Headline, About (first 300 characters), Job titles, Skills section. Complete all sections for All-Star status (required for maximum visibility).

Headline Formula

[What you do] + [Who you help] + [Result] Example: "Frontend Engineer → Building accessible web apps for 100K+ users | React & TypeScript"

About Section Architecture

First 300 characters = visible before "see more" — this is your hook. Structure: Hook → What you do and who you help → Specific expertise → Notable results (numbers) → CTA. Never open with your name — LinkedIn already shows it.

Critical rules

  1. Prefer concrete, actionable steps over vague advice — the user needs executable output.
  2. Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
  3. Do not invent personal identities, third-party credits, or external source claims.

Verification & Quality Checklist

  • The person's actual stated constraints captured, not assumed defaults.
  • Plan is adjustable and states what to do when a week is missed.
  • Cadence is realistic against the time the person actually said they have.
  • Medical, legal, and financial limits respected and stated.

Anti-Patterns & Constraints

  • NEVER give clinical, dietary, or dosage advice as though prescribing.
  • NEVER build a plan on unstated assumptions about someone's life or income.
  • NEVER set a cadence the person has not agreed is achievable.

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.

Check your setup, free