← ClaudeAtlas

linkedin-profile-editorlisted

Edit or reconcile a LinkedIn profile (headline, About, Experience, Publications, Projects, Skills, Featured) through browser automation, driving the profile owner's own logged-in Chrome session via the claude-in-chrome MCP tools. Captures LinkedIn-specific UI quirks discovered through hands-on editing sessions: which sections have real bilingual per-language edit tabs and which silently only support one language, the tab-switch trap that discards unsaved edits, the "update profile headline" checkbox that overwrites a carefully written headline when you add a new position unless you catch it, native <select> dropdowns that ignore coordinate clicks, and a recurring text-corruption pattern where typed input drops characters (especially the second of a double letter) that requires chunked typing with zoom-verification. Also carries a positioning/copywriting layer — headline formulas, About-section structure, section-by-section benchmarks, and a ruthless-pruning framework for deciding what a profile should actuall
Zaious/a1expert-linkedin-coach · ★ 1 · AI & Automation · score 72
Install: claude install-skill Zaious/a1expert-linkedin-coach
# 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