Who it is forA creator who has a finished video and wants a stronger click surface before publishing.
The problemTitles and thumbnails written separately often say the same thing twice, which wastes part of the click surface.
The outcomeA review of the title and thumbnail as a pair, with notes on repeated wording and gaps.
What you need first
- ChatGPT or the Codex app that loads skills from ~/.codex/skills/
- git installed, if you use the clone option
- Python 3 to run the bundled scripts (the README says they need no packages)
- Your own channel data, such as an audience-retention export, for the analysis skills
Steps
- Install the skills from the README link or with the git clone and copy commands.
- Restart the app.
- Paste your draft title and describe or attach your thumbnail.
- Ask the yt-package skill to lint the title and thumbnail as one pairing.
- Run
python title.pyon your title text for a quick local check. (inferred, check the README)
Prompt for your agent
Using the chatgpt-youtube-agent-skill repo, run the yt-package skill on the title <title-text> and the thumbnail description <thumbnail-description>. Expected output: a pairing review that flags any wording the title and thumbnail share. Verify that the review addresses both the title and the thumbnail.
Caveat. The README covers linting the pairing but does not say the skill checks the thumbnail image itself, so describe it in words when you ask.
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page