1---
2name: linkedin-profile-operator
3description: Audit, rewrite, and safely update a person's LinkedIn profile, posts, and professional networking through an authenticated browser. Use for profile positioning, About and Experience edits, Featured and Skills cleanup, LinkedIn posts, connection requests, recruiter replies, or a full account review.
4---
5 
6# LinkedIn profile operator
7 
8Manage LinkedIn as an evidence-led browser workflow. Keep the person's career goal, voice, privacy, and authorization boundaries visible throughout the task.
9 
10## Choose the mode
11 
12- **Audit or draft:** Read the current profile and return prioritized changes or paste-ready copy. This mode is read-only.
13- **Profile update:** Edit the profile sections the user named, then verify every saved value on the rendered profile.
14- **Content and networking:** Draft or publish posts, comments, invitations, and messages. Read [references/content-and-networking.md](references/content-and-networking.md) before taking this branch.
15- **Full review:** Build a positioning brief, audit every relevant section, agree on high-impact changes, apply authorized edits, and report remaining evidence gaps.
16 
17## Authorization boundary
18 
19Treat profile-field edits as authorized only when the user asks for those edits. Posts, comments, invitations, messages, endorsements, follows, applications, and changes to visibility or job-seeking settings each need explicit authorization for that action.
20 
21Never bypass a login challenge, CAPTCHA, platform limit, or account warning. Never export cookies, copy a browser profile, reveal session tokens, or move personal data into the skill bundle. Hand control to the user when LinkedIn requests identity, legal, payment, or sensitive demographic input.
22 
23## Build the positioning brief
24 
25Before a broad rewrite, establish:
26 
27- the outcome the person wants from LinkedIn;
28- the roles, clients, collaborators, or community they want to reach;
29- the work they want to be known for;
30- the strongest verified results and public proof;
31- topics or personal details they want omitted.
32 
33Ask one focused question when a missing answer would materially change the positioning. For a narrow edit, infer the brief from the request and current profile.
34 
35## Create a fact ledger
36 
37Use the current profile, user-provided materials, and sources the user authorized. Classify every meaningful claim as:
38 
39- **verified:** supported by a source or direct user confirmation;
40- **needs confirmation:** plausible, with a date, number, title, scope, or attribution still missing;
41- **planned:** future work that must use future-facing language.
42 
43Never invent metrics, dates, titles, team sizes, revenue, adoption, responsibilities, employers, credentials, or causal impact. Ask for the few missing facts that would strengthen the highest-priority section. When metrics are unavailable, describe the shipped system, adopted process, decision supported, or scope owned in concrete terms.
44 
45## Audit and draft
46 
47Read [references/profile-playbook.md](references/profile-playbook.md) for the section checklist and prioritization rules.
48 
49Draft in the person's language and recognizable voice. Keep the opening direct. Use stable names for products, roles, and domains. Label planned work clearly. Remove keyword piles, generic leadership claims, repeated sentence openings, inflated adjectives, and conclusions that repeat the profile.
50 
51Preserve useful specifics while keeping operational inventories out of the summary. Place detailed numbers in Experience, Projects, or Featured when they prove scale.
52 
53## Operate the browser
54 
55Use an authenticated browser session that the user has made available. Confirm the account identity and current page before editing. Read [references/browser-editing.md](references/browser-editing.md) before the first mutation.
56 
57Edit one section at a time:
58 
591. Record the current visible value and the intended replacement.
602. Open the edit form and wait for its fields to finish loading.
613. Replace the complete field value. Watch for `contenteditable` fields that append text.
624. Read the field back before saving. Fix duplication or truncation first.
635. Save once.
646. Reopen or reload the rendered profile and verify the saved text, dates, links, ordering, and visibility.
65 
66Treat the rendered saved page as the completion criterion. A successful click, closed modal, or tool response alone does not prove that LinkedIn stored the intended value.
67 
68## Report the outcome
69 
70Return:
71 
72- the sections inspected;
73- the exact changes made;
74- the saved values that were verified;
75- claims or metrics still awaiting confirmation;
76- LinkedIn or browser blockers that remain;
77- any authorized actions that still require the user's direct input.
78 
79Never claim an edit, post, invitation, or message succeeded without visible confirmation from LinkedIn.
80