hive.linkedin-automation

1# LinkedIn Automation
2 
3LinkedIn is the hardest mainstream site to automate because it combines **shadow DOM** (`#interop-outlet` for messaging), **strict Trusted Types CSP** (silently drops `innerHTML`), **heavy React reconciliation** (injected nodes get stripped on re-render), **native `beforeunload` draft dialogs** (hang the bridge), and **aggressive spam filters**. Every one of those has bit us at least once. This skill documents what actually works.
4 
5**Always activate `browser-automation` first.** This skill assumes you already know about CSS-px coordinates, `browser_type`/`browser_type_focused`, and `browser_shadow_query`. The guidance below is LinkedIn-specific; general browser rules are there.
6 
7## Rule #0: screenshot + coordinates, not selectors
8 
9LinkedIn changes class names aggressively and hides composers inside shadow roots AND iframes. **Selectors break constantly.** Your default strategy on every LinkedIn page should be:
10 
111. `browser_screenshot()` — see the page visually
122. Pick the target's position from the image
133. `browser_coords(image_x, image_y)` → get CSS pixels
144. `browser_click_coordinate(css_x, css_y)` — reaches shadow DOM, iframes, and React elements indifferently
155. `browser_type(use_insert_text=True, text=...)` — types into whatever is focused, including Lexical composers
16…