One Request, and Text That Sounds Like Nobody
He connected the account, opened the chat, and typed: write me a script.
What came back was tidy, acceptable, faultless, and no use to him.
It contained sentences that could be said on any channel about any subject. It had an enthusiastic tone that wasn't his. It had general points unrelated to the idea in his head.
So he decided the tool doesn't understand what he wants.
The tool never knew what he wanted. He named no idea, no length, no tone, no audience. So it gave the best average answer to a question with no details.
When he reworded the request, "read this idea, write a draft in six cards, in a calm tone, for someone starting a channel for the first time", he got something he could build on.
The difference wasn't the tool, it was three lines.
How to Phrase a Good Request
A good request specifies three things: what the assistant is working on (a specific idea or a specific card), what it should do with it, and what constraint it must respect (length, tone, or audience).
Here are practical examples.
Reviewing the Idea Backlog
The request: "review my saved ideas and identify three suitable for production next month, with the reason for each choice."
This is useful when a large number of ideas has accumulated and prioritising is hard. The decision stays yours, but the assistant spares you rereading the whole list.
Generating Different Angles on One Idea
The request: "take the idea [title] and suggest three different angles for it: a personal angle, an analytical angle, and one built around a single character."
One idea may suit more than one video, and the angle is what determines which video you make from it.
Writing a First Draft of a Script
The request: "write a first draft of a script from the idea [title] in card form: hook, introduction, three main points, and ending."
A first draft isn't the final version, but it moves you from a blank page to text you can edit, which is usually the hardest part. The card structure is covered in: how to write a YouTube video script in Bardiyah, step by step.
Improving One Card Without Touching the Rest
The request: "the hook card in the script [title] is weak. Write me three alternative versions, each under thirty words."
This is among the most useful applications: a precise partial edit rather than regenerating the whole script and losing what you wrote yourself. Writing a hook is covered in: how to write a strong opening hook for an Arabic YouTube video.
Reviewing a Finished Script
The request: "read the script [title] and identify where the pacing sags or the same idea repeats."
Critical review is less risky than generative writing, because the output is notes you decide to take or ignore, not text replacing yours.
Where the Assistant Stops Being Useful
AI is good at organisation, alternative phrasing, and review, and weak at three things specifically: your personal experience, facts nobody has verified, and the particular voice your audience knows.
A viewer follows your channel because they want to see you, not neutral text that could have been produced for any other channel. Which is exactly what our friend at the top of this article received.
Use the assistant to shorten the mechanical work, and keep for yourself the part that makes the video yours.
A Suggested First Step
Start with the simplest use: ask the assistant to read your saved ideas and summarise them.
The output will tell you whether the connection works as it should, and give you a sense of how specific your requests need to be. The connection details are covered in: what is MCP and how to connect AI tools to your Bardiyah project.