Automate LinkedIn Post Creation From Topics to Publishing

Generates LinkedIn posts from trending topics in your network, automatically scoring each draft against your writing standards and publishing only posts that pass QA gates. Instead of manually scraping competitor posts, brainstorming topics, drafting, revising, and filing tasks, Clio handles the full pipeline in a conversation with your team on Slack.

Once set up, you run the pipeline via Slack commands or scheduled jobs. 1. Run @Clio propose to scrape LinkedIn profiles you specify, identify weekly trending topics with generated angles and questions, and post proposals to a Slack thread. 2. Reply with feedback or context in the thread. 3. Run @Clio generate to write the post, QA-score it (0-10 scale, 8.1 minimum), and auto-rewrite up to 3 times if it falls short. 4. On pass, Clio creates a ClickUp task with the draft; on fail, it blocks and notifies you in Slack. Output: weekly LinkedIn posts, published to ClickUp with full drafts, sourced from your network and grounded in your ICP and voice.

Weekly LinkedIn content shipped with zero manual drafting, because topics come from real trending posts and each draft is QA-checked against your exact writing standards.

Requires Python 3.9+ because the project uses modern async and f-string features. Anthropic API calls use claude-opus-4-6 for topic analysis and post writing, which incurs higher costs than smaller models but improves coherence. RapidAPI's fresh-linkedin-profile-data endpoint has rate limits; scrape lookback is set to 14 days by default to stay within typical free tier limits. Slack Socket Mode requires an App Token with connections:write scope for the listener to maintain a persistent connection. ClickUp API requests require your workspace List ID and User ID, which you extract from the app UI and retrieve via curl.

Requires five external accounts and API keys (Anthropic, RapidAPI with LinkedIn data access, Slack, ClickUp), and depends on regular updates to your ICP, style guide, and call context files for quality. QA gate uses a factual integrity veto that caps posts at 5.0 if they invent specific numbers or company names not in your context, which can delay publishing on certain topics. Slack Socket Mode requires your bot to be invited to your content channel.