← ClaudeAtlas

linkedin-postlisted

Use when Chan Meng wants to write an English LinkedIn post for personal-brand marketing — an "idea" post (her own framework/opinion), a "take" post (a short reaction to a tech article or news she read), or a post-event "recap" (reflecting on an offline tech meetup, crediting speakers/organizers/companies to grow her network). Researches and verifies the people to credit, writes on-brand copy with emoji + hashtags, adds a Caldera-branded visual only when one genuinely earns its place (recaps use Chan's own event photos; many posts ship text-only), and hands back ONE markdown file — copy, who to @mention, and photo notes. Chan posts it herself; the skill never opens LinkedIn.
ChanMeng666/linkedin-post-skill · ★ 0 · AI & Automation · score 67
Install: claude install-skill ChanMeng666/linkedin-post-skill
# LinkedIn post writer (Chan Meng / Caldera brand) Write English LinkedIn posts that build Chan Meng's personal brand and expand her network, and hand them back as **one markdown file** she can copy straight into LinkedIn. ## Hard boundary: you never drive a browser **This skill has no browser step.** Do not call `claude-in-chrome`, Playwright-as-automation, chrome-devtools, or any other page-driving tool. Do not open LinkedIn. Do not open a composer, type into one, resolve @mention chips, attach files, or click Post — not even "just to stage a draft for review." This is a deliberate removal, not an oversight. LinkedIn's editor cannot be driven reliably: it swallows the space after a resolved mention chip, lands backspaces at the wrong caret position and corrupts text that was already correct, and exposes no usable file input for photos. Every attempt costs more time than it saves and risks mangling copy Chan has already approved. **Chan does the LinkedIn half entirely by hand** — she pastes the copy, converts each name into a tag from the live dropdown, attaches her own photos, and publishes. Your entire deliverable is a markdown file that makes those thirty seconds frictionless. Still allowed, because they aren't browser automation: - **WebSearch / WebFetch** for research and verification — this is how you get names, titles and facts right, and it matters more now that Chan tags from your table rather than from a URL. - **The render scripts** (`render-card.mjs`, `re