uplika/uplika-plugin / skills/yt-comment
yt-comment
VerifiedTriage YouTube comments into four piles and reply in the creator's voice, sent after approval. For 'reply to my comments', a comment thread.
Adapted from Jakeschincariol/youtube-agent-skill (MIT). Not affiliated with the original author.
yt-comment
The comment section is a retention surface, not a chore. Replies in the first few hours are what decide whether a thread becomes a conversation other people read. Use it for "reply to my comments", "handle the comment section", "someone asked X", or a pasted comment thread.
Before you write
- Read
~/.uplika/<workspace-slug>/voice.mdif it exists. That is the person's voice profile: how they talk on camera, the words they never use, who they are talking to, what they will not claim. If it does not exist, create it with thevoice-profileskill; if they would rather not, ask its three questions (tone, ending style, words to avoid) and use the answers for this session. - Never invent a number, a result or a source. If a figure would strengthen it and you do not have one, ask for it or write the line without it.
With Uplika connected
- Find the video. Take the link from the person, or find the YouTube account in
list_accountsand pick the video fromlist_channel_posts(each item has apermalink). - Read the comments with
list_replieson the video link.truncatedmeans the list stopped before the end; say so. YouTube does not mark which comments are the creator's own, so skip the ones written under the channel's own name. If the answer iscomments_closed, comments are turned off on that video. - Triage and write as below.
- Show every reply and every hide (the comment and what you will do with it) and send only what the person approves:
replywith the video link asid, the comment's id fromlist_repliesasreplyTo, andwait: true. Bait the person wants out of sight goes throughhide_replywith the comment id and the video aspostId;hide: falseshows it again. - Pinning and hearting are not among Uplika's tools: name the comment to pin and the ones to heart, and the person does it in YouTube Studio.
- If a call answers
workspace_required, show the workspaces it lists, ask which one, and passworkspaceId. A channel that is not connected: https://uplika.com/dashboard/connections. Other errors:get_helpwith the code;reconsent_requiredandaccount_disconnectedgo to thetroubleshootskill. youtube_quota_exhaustedfromlist_repliesorhide_reply, or areplywhose target ends withyoutube_daily_cap: Uplika's daily YouTube limit, which everyone on Uplika shares, ran out: stop and do not repeat the call, tell the person when it refills (resetsAt, or the time in the message), and do not ask them to reconnect, because it is not their account (faq:youtube-daily-limit). Keep the approved replies and send them after that time.
Without Uplika
The person pastes the comment thread, and posts the approved replies themselves.
Triage first, always
Sort the comments into four piles and say how many are in each before writing anything:
- Questions: answer them. These are the next video's topics, so note the repeats.
- Corrections: if they are right, say so plainly and thank them. Never argue a fact you cannot check.
- Praise: reply to a few, briefly, with something specific from their comment. A wall of identical "thank you!" replies reads as automated because it is.
- Bait: do not reply. Say so and move on. Never write a comeback, however deserved.
Writing the reply
- Under 30 words. A long reply in a comment thread is a blog post nobody asked for.
- Answer the actual question in the first sentence.
- One question back, only when it is real.
- No emoji unless the person's own replies use them. Check their voice file.
- Never promise a video they have not agreed to make.
The heart and the pin
Say which ONE comment to pin and why. Pin the question the most people also have, not the nicest one. Heart generously: it costs nothing and it is visible.
The gate
Nothing goes out until the person says yes. Every output ends in a block they can copy, and the last line of every run is the question: ship it, or change it? With Uplika connected, "ship it" means you send the approved replies with reply.
Tools
list_accounts: the YouTube account idlist_channel_posts: the channel's videos and their linkslist_replies: the comments under a videoreply: post an approved reply under a commenthide_reply: hide a comment the person wants out of sight, or show it againget_help: the answer for an error code
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |