Prompts for a YouTube Channel: Ideas, Scripts, and Revisions

Prompts for a YouTube channel work best when they draw from a real channel brief: who you make videos for, what makes your take distinctive, which topics you cover, and which formats work for your audience. Without that foundation, an AI will produce ideas that sound like good YouTube content in general rather than a good next video for your channel specifically. Tools like fenbs let you store the channel brief, approved content directions, and successful prompt patterns in one place, so every drafting session — whether you open a new chat or switch to a different model — starts from the same foundation.

The prompts below cover four stages: building a channel brief that anchors everything else, generating ideas from that brief, drafting a script with audience and source checks, and revising a draft for clarity and pacing.

Why your channel brief is the most important prompt input

A channel brief is the document that answers: who is this channel for, what does it promise them, and what does it not do? A channel that promises to explain complex topics in plain language makes a different kind of video than one that goes deep on technical detail for an expert audience. An AI that does not know this distinction will produce ideas and scripts that fit neither.

Write your channel brief once and keep it current. It should include: the target viewer (not just a demographic — a specific type of person with a specific problem or interest), the channel's distinctive angle, the topics it covers and those it deliberately avoids, the tone and presentation style, and the average video length and format. Three paragraphs is enough. A brief that is vague produces vague ideas.

For more on writing scripts specifically, see prompts for YouTube script writing, which covers hooks, outlines, and Shorts adaptations in more detail.

Prompts for generating ideas from your brief

Idea generation prompts should produce options you can evaluate, not content you publish directly. Ask for a range of ideas across different formats or angles, then pick the one that fits best rather than taking the first suggestion.

Here is my channel brief: [paste brief]

Generate ten video ideas that fit this channel. For each idea:
— Write the proposed video title (under 60 characters, specific rather than vague)
— Describe the viewer problem or question this video answers in one sentence
— Explain why this fits our channel's distinctive angle in one sentence
— Suggest the format (tutorial, explainer, opinion, case study, etc.)

Do not suggest ideas that belong to a channel focused on [topic outside your scope]. Flag any idea that might overlap with our existing popular videos.

I want to develop this video idea: [paste the idea from the list above]

Give me:
1. Three possible angles for this topic (three ways to approach it that would each produce a different video)
2. The main thing the viewer should understand by the end
3. Two or three existing videos on this topic I should watch before scripting (describe what a good reference would cover — do not invent titles)
4. A suggested video length and structure

Prompts for drafting a script

Script prompts need a developed brief before the AI writes a word. If you jump straight from "here is the topic" to "write the script," the model will fill in what it thinks good YouTube content looks like. Give it the video concept, the viewer, the main argument, the sources you are drawing from, and the format.

Write a first draft script for this video:

Channel brief: [paste brief or key points]
Video concept: [describe the specific angle you chose]
The one thing the viewer must understand by the end: [single sentence]
Main sources or evidence: [list what you are drawing from — do not invent facts]
Format: [e.g., talking head with examples, voice-over explainer, interview format]
Target length: [e.g., 8–12 minutes at speaking pace of roughly 130 words per minute]
Tone: [describe]

Write the script in sections: hook (30–60 seconds), setup, main content, and close with call to action. After each section, add a brief note on what it is trying to achieve.

The instruction to add a brief note after each section is useful for revision. When you read a section and the note does not match what the section actually does, you have found a gap to fix. It is faster to revise with a target than without one.

Prompts for audience and source checks

Before finishing a script, two checks prevent the most common problems: an audience check that confirms the content fits the viewer you described, and a source check that flags any claim that is not supported by what you provided.

Here is our channel brief: [paste]
Here is the draft script: [paste]

Check the script for audience fit:
1. Is there any section where the level assumes more background knowledge than our target viewer has? Quote the phrase and explain the gap.
2. Is there any section that talks about something our viewer is unlikely to care about? Quote it and explain.
3. Does the hook clearly address a problem or question our specific viewer has? If not, why not?

Here are the sources I am working from: [list them or paste relevant sections]
Here is the draft script: [paste]

Check the script for claims that are not in the source material I provided:
— For each such claim, quote the phrase and note that it needs a source or should be removed.
— Do not add sources of your own — only flag what cannot be verified from what I gave you.

Prompts for revising a draft

Revision prompts should ask for specific improvements rather than a general rewrite. A general rewrite instruction ("make this better") gives the model permission to change everything, including parts you intended to keep. Specific prompts change only what needs to change.

Here is a section of my YouTube script: [paste section]

The pacing feels slow. Suggest cuts that reduce the length by roughly 20% without removing the main argument. For each suggested cut, quote the phrase to remove and explain why it is not essential. Do not add new content.

After revising, read the section aloud. A script that reads well on screen does not always sound natural when spoken. Pacing issues that survive a text read often become obvious immediately when you say the words. Keep a note of what you cut and why — recurring cuts from the same type of section often point to a structural issue worth fixing in your outline template, rather than one you revise again in every script.

How to do this with fenbs

1. Create a free account and add a project for your YouTube channel.
2. Paste your channel brief — target viewer, distinctive angle, topics, tone, and format — into a context note in the project.
3. Save your idea-generation prompt, script template, audience-check prompt, and source-check prompt as Skills.
4. Add any editorial decisions — topics you have decided not to cover, format rules, tone guidelines — as Decisions and rules in the project.
5. Connect your AI app over MCP from Integrations. At the start of each drafting session, ask the assistant to read the project context before generating anything.

fenbs does not upload videos or manage a YouTube account. It keeps your brief and prompts that make each session produce work that fits your channel rather than generic suggestions. Updating your channel brief in fenbs when your audience or focus shifts means every future session reads the current version, not what was true six months ago. For a deeper set of YouTube script-specific prompts covering hooks, outlines, and Shorts, see prompts for YouTube script writing.