agentleFS
AlekseiULAlekseiUL/sprut-agent-kit/skills/youtube-seo/SKILL.md

youtube-seo

Skill66 starsChanged 17 days agoMITView on GitHub

Generate YouTube titles, descriptions, timecodes and hashtags from video transcripts.

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use local-seo.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • huiferSkill

    local-seo

    本地 SEO 分析和优化专家。自动检测项目是否需要本地 SEO,分析 NAP(Name, Address, Phone)一致性、本地关键词优化、Google Business Profile (GBP) 优化和本地结构化数据生成。提供本地商家搜索引擎排名优化建议,包括 NAP 标准化、本地关键词策略、GBP 完整性检查、评论策略、地图嵌入和本地 SEO 审计。

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 4

    Distinctive

    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
  1. Distinctive:

    If user provides transcript text: Use directly.

    line 50
  2. Distinctive:

    Use numbers when relevant ("7 принципов...")

    line 145
  3. Distinctive:

    Add mid/low-frequency queries

    line 187
  4. Distinctive:

    Avoid all YouTube stop-words and restricted topics

    line 204

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

YouTube SEO Generator

Generate click-worthy, SEO-optimized titles, descriptions, timecodes and hashtags for YouTube videos.

✍️ Правила текста (стиль владельца)

Обязательно:

  • Дефис (-) вместо длинного тире (—). ВСЕГДА
  • Сильные глаголы, короткие предложения
  • Личный опыт, метафоры из жизни
  • Хук в заголовке, интрига в первых 2 строках описания

Запрещено:

  • Длинное тире (—) - заменять на дефис (-)
  • "Конечно", "Безусловно", "Стоит отметить", "Является"
  • Канцелярит и пассивный залог
  • Больше 1 эмодзи в описании

Полные правила: skills/copywriter/SKILL.md


Workflow

Step 1: Get transcript

If user provides video/audio file:

# Extract audio if needed (video → audio)
ffmpeg -i video.mp4 -vn -acodec libmp3lame audio.mp3

# Transcribe via OpenAI Whisper API
{skillsDir}/openai-whisper-api/scripts/transcribe.sh audio.mp3 --language ru --json --out transcript.json

If user provides transcript text: Use directly.

Step 2: Analyze transcript

  1. Identify main topic and goal
  2. Extract key insights, numbers, facts
  3. Map narrative structure (for timecodes)
  4. Determine content type:
    • Tutorial → focus on value and steps
    • Case study / research → focus on results and insights
    • Review / comparison → focus on comparison and choice
    • Interview → focus on expert and their opinion

Step 3: Generate metadata


Style Guide

  • First person (as channel author)
  • Tone: sincere, professional, not pushy
  • ONE emoji maximum in entire description
  • Avoid clichés: "В этом видео я расскажу..."
  • Natural keyword integration, no spam

Target Keywords (use contextually)

  • Автоматизация, n8n, AI-агент
  • Искусственный интеллект / AI
  • Промпт / prompt engineering
  • Additional keywords from transcript content

Avoid (YouTube demonetization triggers)

  • Violence, weapons, drugs, gambling
  • Forex/crypto (unless educational)
  • Profanity, discrimination
  • Misleading clickbait
  • Pushy "подпишись/лайкни" — use neutral alternatives

Output Format (STRICT)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📹 НАЗВАНИЕ И ОПИСАНИЕ ДЛЯ YOUTUBE-РОЛИКА
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 ПЯТЬ ВАРИАНТОВ НАЗВАНИЯ:

Вариант 1: [Название]
Обоснование: [Текст]

Вариант 2: [Название]
Обоснование: [Текст]

[... до 5 вариантов]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

✅ РЕКОМЕНДУЕМОЕ НАЗВАНИЕ:
[Твой выбор]

Обоснование выбора: [Почему именно это название]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📝 ОПИСАНИЕ РОЛИКА:

[Полный текст описания]

🔗 ОБЩАЕМСЯ ТУТ: https://t.me/YOUR_CHANNEL

⏱ Тайм-коды:
0:00 - Введение
[...]

#SPRUT #SPRUTAI [остальные хештеги]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🏷 ХЕШТЕГИ ДЛЯ ЗАГРУЗКИ РОЛИКА (через запятую, до 500 символов):
[список без решёток, через запятую]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Title Requirements

  • 70-75 chars optimal, max 100
  • First 70 chars = most engaging part
  • Include 1-2 target keywords
  • Use numbers when relevant ("7 принципов...")
  • Intrigue + specificity + value
  • Each variant needs rationale: SEO value, clickability, emotional trigger

Description Requirements

Structure (in order):

  1. Hook — powerful first sentence, NO "В этом видео..."
  2. What viewer learns — key insights, methods, specific value
  3. Topic blocks — structured content overview
  4. Soft CTA — non-pushy
  5. Community link: 🔗 ОБЩАЕМСЯ ТУТ: https://t.me/YOUR_CHANNEL
  6. Timecodes
  7. Hashtags for description

Timecode Requirements

Format: ММ:СС - Название секции

  • Based on actual transcript content and timestamps
  • Clear, informative section names (Russian)
  • 8-15 sections depending on length
  • First: 0:00 - Введение or similar

Hashtag Requirements

Основные хештеги (для описания)

  • Format: #хештег1 #хештег2 ...
  • Mandatory branded: #SPRUT #SPRUTAI
  • Thematic based on content
  • 15-20 hashtags total
  • Mixed language (Russian + English for reach)

Example:

#SPRUT #SPRUTAI #искусственныйинтеллект #ai #автоматизация #n8n #prompting #GPT4 #нейросети #aiagent #promptengineering

Хештеги для загрузки (upload tags)

  • Format: comma-separated, NO # symbol
  • Max 500 characters
  • Can overlap with description hashtags
  • Add mid/low-frequency queries
  • Mixed language

Example:

искусственный интеллект, автоматизация, n8n, AI, агент, промпт инженеринг, ChatGPT, GPT-4, нейросети, AI автоматизация, prompt engineering

Key Reminders

  • Specificity and value over abstract promises
  • First 70 chars of title = strongest part
  • Description should be "tasty" but not pushy
  • ONE emoji in entire description (max!)
  • Timecodes must match actual video structure
  • Avoid all YouTube stop-words and restricted topics

🔗 Связанные скиллы

СкиллЗачем
analyticsПеред оптимизацией SEO - посмотри yt-deep-stats.py: какие видео в топе, откуда трафик (поиск vs рекомендации), ср. удержание. Оптимизируй под реальные данные
copywriterОписание и заголовок в стиле владельца
creator-marketingСтратегия продвижения видео

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.