← ClaudeAtlas

claude-linkedin-profilerlisted

Edit, reconcile, or build a LinkedIn profile (headline, About, Experience, Publications, Projects, Skills, Featured) through browser automation via the claude-in-chrome MCP tools, driving the profile owner's own logged-in Chrome session. Handles LinkedIn's real UI traps — bilingual per-language edit tabs, a headline that gets silently auto-overwritten, native dropdowns, a recurring text-corruption bug — plus a positioning layer (headline/About formulas, section benchmarks, a pruning framework) for deciding what the profile should say, and a materials-intake path for drafting from raw resume/paper/repo material when there's no source of truth yet. Use whenever the user wants to update, sync, reconcile, rewrite, or build their LinkedIn profile — e.g. "make LinkedIn match my resume", "add this paper to LinkedIn", "rewrite my headline", "review my profile", "here's my resume, build me a LinkedIn profile". Requires the claude-in-chrome MCP tools — load via ToolSearch if deferred.
Zaious/claude-linkedin-profiler · ★ 1 · AI & Automation · score 72
Install: claude install-skill Zaious/claude-linkedin-profiler
# LinkedIn Profile Editor (via claude-in-chrome) This skill covers three layers of a LinkedIn profile editing task, and most real requests need at least two of them: - **Where the content comes from, if there's no ready source of truth yet** — the user has a pile of resumes/papers/repos/chat-typed facts but nothing structured. Read `references/material-intake.md` for how to draft from that without needing a formal fact database first. - **What the profile should say** — positioning, headline/About structure, what to prune, section-by-section benchmarks. Read `references/positioning-framework.md` for the judgment layer (deciding content) and `references/section-benchmarks.md` for the structural/data layer (character budgets, checklists, what "good" looks like per section). - **How to actually get it onto the live page safely** — the claude-in-chrome mechanics, and the LinkedIn-specific UI traps that will otherwise cost you a retyping cycle or silently overwrite something the user cares about. Read `references/mechanics.md` before touching the browser. ## How to sequence a real task 1. **Figure out what's actually being asked.** "Update my LinkedIn" after a resume/dossier change is a *reconciliation* task (diff against a source of truth, mechanics-heavy). "Rewrite my headline" or "review my profile" is a *positioning* task (judgment-heavy, `positioning-framework.md` first). "Here's a pile of my papers/resume/repos, build me a profile" is a *mat