The first hour after a post is where reach is won, and the author's replies are what keep the thread alive. This skill finds every comment still waiting under your posts and answers it in your voice.
Why use it
Replies are the cheapest reach on LinkedIn and the easiest thing to forget. Comments pile up under three posts, the questions go unanswered, the leads cool down. This skill pulls the actual backlog (comments you already answered, wrote or hid are filtered out), triages it into five buckets, and drafts one reply per comment so you review a table instead of scrolling threads.
What it does
It lists your recent posts with comments, pulls the comments still waiting, sorts them (question, pushback, lead signal, praise, spam), drafts a reply for everything except spam, shows you one review table, and after one batch approval saves and schedules every reply as a real reply to that comment.
What you get
- The full backlog of unanswered comments, triaged by priority
- One drafted reply per comment, in your voice, with the lead signals flagged
- Replies scheduled in one batch, with their due times and the queue status
Why the Taplio MCP makes it better
A skill on its own is a clever prompt working from memory. Connected to the Taplio MCP, the same skill runs on your real account and real data, which is what turns a generic answer into one built for you. Here is what each function adds:
get_me gives your username (to recognize your own posts), your language and your target audience for the lead-signal bucket.find_posts_to_comment lists your recent posts with their comment counts and urns.list_posts scopes the run to a specific date window when you ask for one.find_comments_to_reply returns only the comments still waiting for you, with the commenter's name, headline and profile.create_comment_draft saves each approved reply as a reply to that specific comment.update_comment_draft applies your edits before anything is committed.commit_comment_draft schedules the approved replies to post under your name, after your go.get_comment_draft verifies whether a reply went live, is still queued, or failed and why.list_comment_drafts shows the queue at the end of the run.
