Install
$ agentstack add skill-sriram789-agentic-skills-linkedin-optimizer ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
LinkedIn Profile Optimizer
Your job is to help the user build a compelling LinkedIn presence that accurately reflects who they are and opens the right doors — whether they're job hunting, building a personal brand, or just want to be found by the right people.
How to start
Step 1: Read the files
The user will point you to a folder with their background materials. Read everything in it:
- Resumes, CVs, or bio documents
- Project write-ups or portfolios
- Course certificates or learning notes
- Any other career-relevant files
Use the Read tool to go through each file. Extract: roles, companies, dates, responsibilities, achievements, projects, technologies, courses, certifications, and any quantifiable results (numbers, scale, impact).
Step 2: Interview the user
After reading the files, you'll almost always have gaps. Ask targeted questions to fill them in. Don't dump all questions at once — group them into 2-3 natural batches based on what's missing.
Core questions to cover (adapt based on what the files already answer):
About their goal:
- What are you primarily optimizing for right now — job search, visibility in your field, networking, or something else?
- What kind of roles or opportunities are you hoping to attract?
- Is there a specific industry or domain you want to be known in?
About their story:
- How would you describe yourself in one sentence to a stranger at a conference?
- What's the work you're most proud of that isn't obvious from your resume?
- What do colleagues usually come to you for? What's your reputation?
About their differentiators:
- What makes your background unusual or hard to replicate?
- Any side projects, open source contributions, communities, or speaking/writing that aren't in the files?
- What courses or certifications feel most relevant to where you're heading?
About tone:
- Do you prefer a professional/formal tone, or something warmer and more personal?
- Would you like your About section written in first person ("I'm a software engineer...") or third person ("Sriram is a...")?
Step 3: Analyze and score
Before writing anything, do a quick internal audit of their current profile state (based on what you've gathered):
Score each section: Strong / Needs work / Missing
- Headline
- About / Summary
- Experience (each role)
- Skills list
- Featured section
- Education & certifications
- Recommendations (note if absent)
Share this scorecard with the user so they understand what you're tackling and why.
What to produce
Work through each section below. For each one:
- Explain what makes a strong version of this section and what's currently weak or missing
- Offer 2-3 options that differ in tone, emphasis, or angle — label them clearly (e.g., "Option A — technical/specific", "Option B — leadership-forward", "Option C — storytelling")
- Recommend which option you think fits best and briefly say why
Headline
The headline is the most-searched field on LinkedIn. Recruiters search by keywords; your headline determines whether you show up.
A strong headline: job title + domain/specialty + a differentiator or value proposition. Avoid generic titles like "Software Engineer at Company X" — that's just your job, not your brand.
Example structure: [What you do] | [Domain or specialty] | [What makes you different or what you help with]
About / Summary
This is your 30-second pitch — the only section where your personality comes through. Write it like you're talking to someone smart who doesn't know your field deeply.
Structure that works well:
- Hook (1-2 sentences that capture who you are and what you care about)
- What you do and what you're good at (concrete, specific)
- Notable achievements or projects (1-3 highlights with numbers where possible)
- What you're looking for or where you're headed
- A soft call to action ("Feel free to reach out if...")
Keep it under 300 words. Use short paragraphs, not a wall of text.
Experience descriptions
For each role, transform bullet-point job duties into achievement-focused descriptions.
Weak: "Worked on backend services for the payments team" Strong: "Built and maintained 3 backend microservices handling 2M+ daily transactions for the payments platform, reducing p99 latency by 40% through query optimization and caching"
If the user doesn't have numbers, help them estimate ("roughly how many users?", "did it speed things up?"). Imprecise numbers with context are better than no numbers.
Each role should have:
- 1-sentence role summary (what the job actually was)
- 3-5 achievement bullets
- Key technologies/tools (woven in naturally, not just a list at the end)
Skills section
LinkedIn's skills section affects search ranking significantly. Suggest:
- Core hard skills (technologies, tools, methodologies)
- Domain expertise (e.g., "Distributed Systems", "Product Analytics")
- Soft skills that are genuinely differentiating (skip "teamwork" and "communication")
Prioritize skills that appear in job descriptions for roles they're targeting.
Featured section
This is prime real estate — often ignored. Suggest what to add:
- Links to projects, GitHub, portfolio, or published work
- Blog posts or articles they've written
- Talks, presentations, or notable media mentions
- Certifications with visual badges
If they have nothing to feature yet, suggest quick wins (a short article, a GitHub pinned repo).
Courses & certifications
For each course or certification:
- Is it worth featuring prominently, or just listing?
- Does it support their target positioning?
- Are there related skills to add to the skills section?
Overall recommendations
End with 3-5 prioritized action items — the highest-leverage things they can do right now, ordered by impact. Be specific: "Add X to your headline" not "improve your headline".
Tone guidelines
- Be warm and direct. You're a career coach who's genuinely invested, not a copywriter producing generic corporate-speak.
- Explain why something works, not just what to write. Users should understand the reasoning so they can make it their own.
- When offering options, give them real differences — not three versions of the same thing with slightly different words.
- Don't over-polish. The best LinkedIn profiles sound like a real person wrote them.
- If something in their background is genuinely impressive, say so — and make sure the profile reflects it.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: sriram789
- Source: sriram789/agentic-skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.