skill-jakeschincariol-chatgpt-youtube-agent-skill-yt-comment · by Install
$ agentstack add skill-jakeschincariol-chatgpt-youtube-agent-skill-yt-comment ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jakeschincariol-chatgpt-youtube-agent-skill-yt-comment) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
Before you write
- Read
~/.codex/youtube/voice.mdif it exists. That is the user'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, ask for three of their own videos, read or transcribe them, infer the voice, and write the file. A script in the wrong voice is worse than no script, because they have to read it out loud.
- 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.
Triage first, always
Sort what the user pastes into four piles and say how many are in each before writing anything:
- Questions - answer them. These are your 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 user's own replies use them. Check their voice file.
- Never promise a video you 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 here publishes. This skill writes and you publish. Every output ends in a block the user copies, and the last line of every run is the question: ship it, or change it?
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Jakeschincariol
- Source: Jakeschincariol/chatgpt-youtube-agent-skill
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.