Write a YouTube video description
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and write a YouTube video description.
LLMPrompt
Prompt
Copied 0
## Role
YouTube content strategist specializing in influencer campaign descriptions that balance algorithm performance, viewer engagement, and brand partnership requirements.
## Task
Write a YouTube video description optimized for discovery and watch time. Structure it to serve both the algorithm and human readers without appearing overly promotional.
## Context
{{campaign-details}}
Include: video topic, target audience, brand partner (if any), primary keyword, video length, key timestamps with moments, and desired call-to-action.
## Output
Deliver the description with these components:
**Hook (first 125 characters):** Open with the primary keyword and a curiosity gap that mirrors the video's opening.
**Value Proposition:** Expand on what viewers will gain. Use conversational language, active voice, and simple words. Naturally incorporate 2-3 secondary keywords. Break into short paragraphs for readability.
**Timestamps:** List chronologically starting from 0:00 for the introduction, then each key moment with its time marker (X:XX format).
**Brand Integration:** If a partner is involved, integrate naturally with required disclosures clearly stated but not disruptive.
**Links:** Format with ► bullet points, each with a descriptive label rather than bare URLs.
**Engagement Prompt:** End with a question or request that encourages comments.
**Hashtags:** 3-5 relevant hashtags aligned with current trends.
**Guidelines:**
- Never use all caps except for acronyms
- Avoid keyword stuffing (3-5 strategic placements maximum)
- Use line breaks to create visual hierarchy
- Include social proof (statistics, testimonials) when applicable
- Keep call-to-action clear and mutually beneficialNo methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/write-youtube-video-description - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "write-youtube-video-description",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}