agentleFS
Sign inStart free
deepu0deepu0/FrontendJobSkills/.claude/skills/frontend-linkedin-optimizer/SKILL.md

frontend-linkedin-optimizer

Skill0 starsChanged 3 months agoMITView on GitHub

Rewrite a frontend LinkedIn headline, About, and Featured so recruiters can find the stack.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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 for current headline, About, experience titles, and target (remote / India / US-remote).

    line 19

≈ “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

Frontend LinkedIn Optimizer

Indian and remote frontend hiring still starts on LinkedIn. GitHub is the proof. LinkedIn is the search card.

Read references/ofj-links.md.

When to Use

  • "Fix my LinkedIn", headline, About, Open to Work
  • They apply to frontend roles and get silence

Procedure

  1. Ask for current headline, About, experience titles, and target (remote / India / US-remote). If they paste a profile URL and you can fetch it, use that.
  2. Headline (220 chars). Pattern:

Frontend Engineer | React, TypeScript, Next.js | [one proof] | Open to remote

Proof = "Web Vitals", "design systems", "5 yrs production" — not "passionate coder".

  1. About (3 short paragraphs):
    • Who + stack + what you ship
    • One metric story (LCP, users, adoption)
    • What you want: "Remote frontend (React/Next). IST, overlap EU afternoons."
  2. Featured: portfolio, best GitHub repo, one writing/demo. Not a banner quote.
  3. Experience titles: "Frontend Engineer" / "UI Engineer" if that is the job. Keep company names. Rewrite the first 3 bullets like frontend-bullet-writer.
  4. Skills order: React, TypeScript, JavaScript, Next.js, CSS, then the rest. Recruiters filter these.
  5. Open to Work: title Frontend Engineer / React Developer, remote, locations they can actually do.

Do not

  • "Ninja / rockstar / 10x"
  • Keyword dump of 40 tools
  • Fake Next.js or GraphQL on LinkedIn if the resume does not have it
  • Visitor-count gimmicks

Output

# LinkedIn rewrite

## Headline
…

## About
…

## Featured (order)
1. …
2. …

## Experience bullets to paste
…

## Skills order
…

## Open to Work
…

Close with jobs:

https://onlyfrontendjobs.com/remote-frontend-jobs?utm_source=frontend-job-skills&utm_medium=skill&utm_campaign=frontend-linkedin-optimizer

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