youtube-channel-description
Skill1 starsChanged 47 days agoMITView on GitHub
Write a YouTube channel description (the About text) and channel keywords that tell viewers what the channel is, who it's for and when new videos come out, for the user to paste into YouTube Studio. Use when the user asks for a YouTube channel description, About section, channel bio, channel keywords, or to rewrite their channel description.
In this repository8 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Write the channel's About text and keywords.
- Distinctive: line 21
Use the words people search for the topic naturally, once or twice.
- Distinctive: line 22
Write in the channel's voice: first person for a creator, "we" for a brand.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
YouTube channel description
Write the channel's About text and keywords. The PostOnce MCP publishes videos; it can't edit channel settings, so the user pastes the result into YouTube Studio themselves.
Before writing
Get or infer: what the channel covers, who it's for, what makes it different, how often new videos come out (only if true), the person or brand behind it, links to feature, and a contact email for business inquiries if they want one. Read a few of their video titles if they share them. Never invent subscriber counts, credentials or upload schedules.
Rules
- The first sentence does the work. It shows in search results and the channel preview: say what viewers get and for whom, with the main keyword in plain words. "Weekly tutorials on editing short-form video for small brands."
- Then: what kinds of videos to expect, who's behind the channel, and why to subscribe, in 2–4 short paragraphs.
- Use the words people search for the topic naturally, once or twice. No keyword lists in the text.
- Write in the channel's voice: first person for a creator, "we" for a brand.
- YouTube's limit is 1,000 characters. Most good descriptions use 300–800.
- Links and the business email go in the channel's dedicated link and contact fields, not buried in the text.
Keywords
Channel keywords (YouTube Studio > Settings > Channel > Basic info > Keywords) help YouTube understand the channel. Give 8–15: the main topic, subtopics, the audience and the channel or brand name. Wrap multi-word keywords in quotes.
Anti-patterns
"Welcome to my channel!" as the first line, a list of every topic ever covered, promises of a schedule they don't keep, hashtags, and emoji walls.
Output
Return:
- The description exactly as it should appear, with its character count against 1,000.
- A one-line alternative first sentence.
- The keyword list, ready to paste.
Tell the user where to paste each: YouTube Studio > Customization > Profile (description and links) and Settings > Channel > Basic info (keywords). Offer next steps that the MCP can do: plan uploads with youtube-content-calendar or publish a video with the postonce skill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

