linkedin-content

Outline a long-form technical article (1500–2500 words) about the current repository, with each section mapped to verified claims and repo file references. Use this AFTER proof-pack when the user wants a long-form article or blog post (NOT a short LinkedIn post — for that use series-plan). Requires content/claims.md from proof-pack.

Copy a finished LinkedIn post draft to the macOS clipboard with formatting preserved (HTML via pandoc + pbcopy-html.swift). Use AFTER draft-post N when the user wants to paste the post into the LinkedIn editor with bold/italic intact. Requires pandoc.

Copy a finished LinkedIn post draft to the macOS clipboard as plain UTF-8 text (via pbcopy-text.swift). Use AFTER draft-post N when the user wants the raw markdown on the clipboard with Mathematical Bold/Italic Unicode (U+1D400–U+1D7FF) intact. Use this instead of macOS pbcopy, which mangles 4-byte UTF-8 sequences.

Write the publish-ready long-form article (1500–2500 words) from the article plan, with inline code snippets and direct repo links. Use this AFTER article-plan when the user wants the final article text — this skill produces the actual prose, not the outline.

Draft the actual copy for a specific LinkedIn post (1 of 5 in the series) — produces 3 style variants (technical, business, founder), 5 opening hooks, and hashtags. Use this AFTER series-plan when the user wants to write the real text of post N. Requires the series plan from series-plan.