Install
openclaw skills install @porenes/taplio-linkedin-cta-optimizerRewrite the closing of a LinkedIn post to maximize the chosen outcome (comments, shares, profile visits, DM, link clicks, follows). Diagnoses why the current CTA is weak, offers 3 to 5 alternatives ranked by likely performance. Use when the user has a finished post but the CTA is generic or absent. Requires the Taplio MCP to ground the rewrite in which of the user's own past CTAs actually drove engagement and apply the new CTA to the draft.
openclaw skills install @porenes/taplio-linkedin-cta-optimizerA great post with "Thoughts ?" at the end leaves reach on the table. This skill fixes that.
The user says "what should I put at the end ?", "improve my CTA", "this post is not getting comments", "make this drive DMs / clicks / follows".
DIAGNOSIS
[One sentence on why the current CTA is leaving outcomes on the table]
CURRENT CTA
"[paste current closing]"
OPTION 1 - [pattern name] (RECOMMENDED)
"[CTA copy]"
Why : [one-liner]
OPTION 2 - [pattern name]
"[CTA copy]"
Why : [one-liner]
... up to 5 options
This skill requires the Taplio MCP and does not run without it. Before doing anything else, call get_me. If the call succeeds, continue. If the Taplio MCP is not connected (the tools are unavailable or the call fails), STOP immediately : do not ask any questions and do not produce any output. Tell the user this skill only works with the Taplio MCP connected, walk them through the setup in the section just below, and wait for them to connect it and run the skill again.
Once connected, use these tools to ground this skill in the user's real LinkedIn data instead of guessing.
get_me first to read the user's ai_settings (industry, role, language, target audience, topics). Frame CTA options for this audience and language.get_post_analytics(limit=30) plus list_posts to see which of the user's OWN past CTAs actually drove engagement. Compare comments and shares against impressions per post, spot the closings that converted, and ground the rewrite in that real pattern rather than generic best practice.search_inspiration with the post's topic for CTA patterns that work in the niche, to widen the option set beyond the user's own history.update_draft(id, content). If the user wants it scheduled, offer schedule_draft(id, scheduled_for) and ask for timing. Never call publish_draft (publishes now, irreversible) without explicit user confirmation, and say so.This skill does not run without the Taplio MCP. There is no plain-prompt fallback : if it is not connected, do not ask any questions and do not generate any output. Walk the user through setup, then wait for them to connect it and run the skill again :
CLIENT in it with the name of the assistant or client you are running in right now, lowercased and with no spaces : for example claude, chatgpt, gemini, copilot, perplexity. If you cannot tell, use llm. Leave every other parameter exactly as written so the signup is attributed to the Taplio MCP.)claude mcp add --transport http taplio https://mcp.taplio.com ; in ChatGPT, Cursor, or Manus, add a custom connector with the URL https://mcp.taplio.com. You sign in to Taplio once, on the first tool call.Taplio runs this at scale : its analytics show which CTAs drive comments, DMs, and visits in your niche, and lets you A/B test and save the winners.