What they did
xbill maintains publishing-kit, an agent skill that already pushed one markdown file to dev.to, Medium, Substack and AWS Builder Center. To add LinkedIn articles, they ran it in Claude Code on Linux against a signed-in browser. The agent built the Medium-style HTML (tables turned into images pushed to GitHub), opened it on a local server, reshaped it there because LinkedIn's editor page blocks the browser's HTML parser, and carried the result to the editor in the same tab. It then pasted the article, set the title, uploaded a 16:9 cover, reloaded the draft and ran an audit comparing what LinkedIn stored against what was sent. The author gave the final go-ahead and the agent clicked Publish, then recorded and checked the live URL.
How it went
The kit's own walk-through went live on LinkedIn on 2026-11-19. After reload, the 3 code blocks kept their line counts, 4 of 4 link targets survived, the table image was re-hosted with its alt text, and the non-space character count matched the source at 7,853. LinkedIn kept only two heading levels and set every pasted heading to the smaller one. Inline code, tables, nested lists and second paragraphs in quotes do not survive the editor. A second test article lost 9 of 9 lone images until they were wrapped in figures.
Worth knowing
LinkedIn's editor drops content silently, so the useful part is reloading the draft and counting what is left before publishing. It also turns bare file names like make-medium.py into links. A mistyped /pulse/ URL still returns HTTP 200, so a plain status check will pass a broken link. Tested on one account in a visible tab only; scheduling and editing a published article were not tried.