okhp3-openclaw-linkedin-drop

Topics in the source

• LinkedIn Drop
• Input
• What to do
• Output
• What this skill never does
• About

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Turning finished work into posts is the documented bottleneck in the OKHP3 LinkedIn pipeline. This skill exists to shrink the gap between "I did a thing" and "there's a draft sitting in a folder ready to review," using only the local model, no Frontier call needed for a first pass. Whatever Jamie pastes: a raw idea, a paragraph of notes, a finished deliverable he wants turned into a post, or a complaint/rant he wants reframed as a lesson-learned post. 1. Identify the angle: what's the one idea worth a post here. Don't try to cover everything he said; ROY applies (understanding produced divided by explanation invested) -- pick the sharpest single thread. 2. Draft in the established brand voice: punchy standalone lines as rhythm devices where they land naturally, no em dashes, paragraphs consolidated for LinkedIn's double-line-break renderer, hard close on the last line with no softening question tacked on afterward. 3. Write the draft plus two or three alternate angles as a short list at the bottom (titles only, one line each) in case the main draft misses. 4. Save it to /.openclaw/workspace/linkedin-drafts/ - .md (create the fo

This is an excerpt. Refer to the complete source and its current requirements.