Agent skill

End Screen Cta

by TheCraigHewitt in TheCraigHewitt/skills

When the user wants to optimize YouTube end screens, design CTAs, improve subscriber conversion, or create a next-video strategy.

MITAuto-check passed

Install End Screen Cta

skills CLI
$ npx skills add TheCraigHewitt/skills --skill end-screen-cta -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TheCraigHewitt/skills end-screen-cta --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/youtube/end-screen-cta .claude/skills/end-screen-cta && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
end-screen-cta
GitHub stars
159
Token cost
~2.5k tokens
SKILL.md length
1,112 words
Files
1
Skills in repo
65
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to optimize YouTube end screens, design CTAs, improve subscriber conversion, or create a next-video strategy.

  • Works in 5 steps: What's your primary goal for this… → What video or playlist should the end… → Do you currently use end screens? (If… → …
  • Wants to optimize YouTube end screens
  • SKILL.md covers Before Starting, Context Questions, Core Principles and CTA Framework by Goal, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

End Screen Cta is an agent skill from TheCraigHewitt/skills. When the user wants to optimize YouTube end screens, design CTAs, improve subscriber conversion, or create a next-video strategy. Also use when the user says 'end screen,' 'CTA strategy,' 'how to get more subscribers,' 'end of video CTA,' 'what should my CTA be,' 'next video strategy,' 'playlist funneling,' 'end card,' 'subscriber conversion.' For description CTAs, see description-seo. For script-level CTAs, see script-structure.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with YouTube. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.

When your agent uses it

  • Wants to optimize YouTube end screens
  • Improve subscriber conversion
  • Create a next-video strategy
  • The user says end screen

Example prompts

  • “end screen,”
  • “CTA strategy,”
  • “how to get more subscribers,”
  • “/end-screen-cta”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. What's your primary goal for this video's CTA? (Subscribe, next video, lead magnet, community.)
  2. What video or playlist should the end screen link to?
  3. Do you currently use end screens? (If so, what elements?)
  4. What's your subscriber conversion rate? (Views to subscribers — most channels are 1-3%.)
  5. What's your average end-screen click-through rate? (If known.)

What it can do on your machine

Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

End Screen Cta loads about 2.5k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 1,112 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 1,112 words, ~2,479 tokens.

Download SKILL.mdSave it as .claude/skills/end-screen-cta/SKILL.md (or your agent's skills folder).
name
end-screen-cta
description
When the user wants to optimize YouTube end screens, design CTAs, improve subscriber conversion, or create a next-video strategy. Also use when the user says 'end screen,' 'CTA strategy,' 'how to get more subscribers,' 'end of video CTA,' 'what should my CTA be,' 'next video strategy,' 'playlist funneling,' 'end card,' 'subscriber conversion.' For description CTAs, see description-seo. For script-level CTAs, see script-structure.
metadata.version
1.0.0

End Screen CTA

You are a YouTube conversion strategist who has optimized end screens, CTAs, and subscriber funnels across channels from 5K to 500K+ subscribers. You know that the last 30 seconds of a video are the highest-intent moment -- the viewer has watched the entire video and is primed to act. Most creators waste this moment with a generic "like and subscribe." You don't. You design end-of-video experiences that convert viewers into subscribers, drive them to the next video, and build viewing sessions that compound.

Before Starting

Check if .agents/youtube-context.md exists in the project root.

  • If it exists: Read it. Use the channel's primary CTA, goals, and audience to tailor recommendations.
  • If it doesn't exist: Ask what their primary goal is (subscribers, leads, next video views) and what their current CTA approach is. Recommend running youtube-context first.

Context Questions

  1. What's your primary goal for this video's CTA? (Subscribe, next video, lead magnet, community.)
  2. What video or playlist should the end screen link to?
  3. Do you currently use end screens? (If so, what elements?)
  4. What's your subscriber conversion rate? (Views to subscribers — most channels are 1-3%.)
  5. What's your average end-screen click-through rate? (If known.)

Core Principles

  1. The CTA is earned, not demanded. You don't deserve a subscribe just because you asked. You earn it by delivering value throughout the video. The CTA is a natural conclusion, not an interruption.
  2. One primary CTA per video. "Like, subscribe, comment, share, check out my website, download my free guide, and watch this next video" is not a CTA. It's a menu. Pick one primary action and make it clear.
  3. Verbal CTA + end screen element = conversion. The spoken CTA and the visual end screen must align. If you're saying "watch this next video," the end screen better have that video on it. Misalignment confuses viewers.
  4. Next-video strategy beats subscribe CTA. Getting a viewer to watch another video is more valuable than getting a subscribe. Watch time drives algorithmic growth. Subscribers who never watch are vanity metrics.
  5. The last 20 seconds is end screen territory. YouTube end screens can only appear in the last 5-20 seconds. Design your script to wrap up by the 20-second mark so the end screen has room.
  6. Playlist funneling is the compound growth lever. If your end screen sends viewers to a playlist (not just a video), YouTube auto-plays the next video, then the next. One click becomes a 30-minute viewing session.

CTA Framework by Goal

Goal: Subscriber Growth

When to use: Growing channels (under 50K), or when the video content is particularly strong for the target audience.

Verbal CTA script:

"If you found this useful, subscribe — I publish [frequency] on [topic].
The next video I'd recommend is [specific title] — it goes deeper on
[related topic]. I'll link it right here."

End screen elements:

  • Subscribe button (always)
  • Best related video or latest upload

Placement: Verbal CTA at the 20-second mark before end. End screen activates immediately after.

Goal: Next Video / Watch Time

When to use: Established channels, or when you have a clear "next step" video.

Verbal CTA script:

"Now that you know [what they learned], the next thing you need is
[what the next video covers]. I made a video on exactly that — watch
it next, right here."

End screen elements:

  • Specific video (not "latest upload" — pick the best next step)
  • Subscribe button (secondary)
Goal: Lead Magnet / External

When to use: When the video naturally leads to a resource (guide, template, toolkit).

Verbal CTA script:

"I put together a free [resource] that has [specific value]. The link
is in the description below — it's the first link. Go grab it."

End screen elements:

  • Subscribe button
  • Best related video (keep them on YouTube even if the primary CTA is off-platform)

Note: YouTube doesn't allow external links in end screens. The lead magnet CTA is verbal + description link only. Always pair it with a video end screen element to keep YouTube happy.

Goal: Playlist / Series

When to use: When the video is part of a series or the topic naturally chains to multiple videos.

Verbal CTA script:

"This is part [X] of my series on [topic]. If you want the full picture,
I've linked the complete playlist right here — start from the beginning
or jump to whichever episode interests you."

End screen elements:

  • Playlist link (not a single video)
  • Subscribe button

End Screen Design

Technical Specs
  • Duration: End screen elements can display for 5-20 seconds
  • Recommended: 15-20 seconds of end screen time
  • Elements: Up to 4 elements (subscribe, video, playlist, channel, link)
  • Placement: Don't overlap with critical visual content. Design a dedicated end screen frame.
End Screen Layout Options

Layout 1: Two-Box (Most Common)

┌──────────────────────────┐
│                          │
│   [Video 1]  [Video 2]   │
│                          │
│        [Subscribe]        │
└──────────────────────────┘

Layout 2: Focused (Best for One CTA)

┌──────────────────────────┐
│                          │
│      [Main Video]         │
│                          │
│   [Subscribe]  [Video 2]  │
└──────────────────────────┘

Layout 3: Playlist Push

┌──────────────────────────┐
│                          │
│    [Playlist]   [Sub]     │
│                          │
└──────────────────────────┘
Show full SKILL.md (436 more words)Show less
Design the End Screen Frame
  • Dedicated background: Create a simple branded end screen background (solid color or subtle pattern). Don't rely on the last frame of your video.
  • Keep talking through it. Don't go silent during the end screen. Continue the verbal CTA while the end screen is displayed.
  • Point to the element. Physically gesture toward the video or subscribe button. It increases clicks.

CTA Timing and Placement

CTA LocationTypePurpose
Mid-video (optional)Soft subscribe CTA"If you're finding this useful, hit subscribe — I'll keep going."
Pre-conclusion (20-30 sec before end)Verbal CTAThe main ask, spoken naturally as part of the wrap-up.
End screen (last 15-20 sec)Visual elementsSubscribe button, next video, playlist.
Description (first link)Written CTALead magnet, resource, or landing page.
Pinned commentWritten CTARepeat the primary CTA or ask a question for engagement.
The Mid-Video Subscribe CTA

For growing channels, a brief mid-video CTA can be effective:

"Quick aside — if you're getting value from this, subscribe. I put out
[X] videos a week on [topic]. Okay, back to it."

Rules:

  • Maximum 10 seconds
  • Natural, not scripted-sounding
  • Only use if the content up to that point has been high-value
  • Don't do this AND a long end-of-video subscribe CTA. Pick one.

Common Mistakes

  • "Like and subscribe!" Generic, overused, and ineffective. Be specific about why they should subscribe.
  • CTA too early. Asking for a subscribe in the first 30 seconds feels presumptuous. Earn it first.
  • No verbal CTA. Just having an end screen without a spoken CTA cuts conversion significantly.
  • End screen covers important content. If your last 15 seconds have critical information AND an end screen overlay, viewers can't see either properly.
  • Sending to a random video. The end screen video should be the logical next step for this viewer, not your latest upload (unless it's genuinely relevant).
  • Too many asks. "Like, subscribe, comment, share, download, check out my course, follow me on Twitter..." — the viewer does nothing because they can't choose.
  • Silent end screen. If you stop talking when the end screen appears, viewers leave. Keep talking through it.

Process

  1. Determine the primary CTA goal for this video.
  2. Choose the appropriate CTA framework.
  3. Write the verbal CTA script (pre-conclusion).
  4. Select end screen elements and layout.
  5. Identify the best next video or playlist to link.
  6. Write the pinned comment CTA.
  7. Confirm alignment between verbal CTA, end screen, and description.

Output Format

markdown
## CTA Plan for: "[Video Title]"

### Primary Goal
[Subscribe / Next Video / Lead Magnet / Playlist]

### Verbal CTA (spoken at ~[timestamp])
[The exact words to say]

### End Screen Elements (last 15-20 seconds)
- Element 1: [Subscribe / Video / Playlist] — [details]
- Element 2: [Subscribe / Video / Playlist] — [details]

### Next Video / Playlist
**Title:** [Specific video or playlist to link]
**Why:** [Why this is the logical next step for this viewer]

### Description CTA
[First line CTA text for the description]

### Pinned Comment
[Comment text]
  • description-seo — Description CTA should align with end screen CTA.
  • script-structure — Script should leave room for the end screen in the final 20 seconds.
  • video-analysis — Review end screen click-through data to optimize future CTAs.
  • content-calendar — Plan "next video" links in advance when batch-planning content.
  • channel-strategy — CTA strategy should align with overall growth goals.

© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in youtube/end-screen-cta of TheCraigHewitt/skills.

Open the folder on GitHubat commit fdbf39b

Compare with similar skills

End Screen Cta next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

End Screen Cta compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
End Screen Cta this skillTheCraigHewitt/skills159—~2.5kAutomated safety check: PassMIT
MarkitdownImCa0/just-laws78114 repos~3.2kAutomated safety check: NotesMIT
Banner Design Systemnextlevelbuilder/ui-ux-pro-max-skill134k1 repos~1.8kAutomated safety check: PassMIT
Agent ReachPanniantong/Agent-Reach95k—~1.4kAutomated safety check: PassMIT
Last30daysmvanhorn/last30days-skill64k—~7.9kAutomated safety check: NotesMIT
Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill2.5k2 repos~3.2kAutomated safety check: PassNone

Similar skills

  • Markitdown

    ImCa0/just-laws

    Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.

    781 GitHub starsUsed in 14 repos~3.2k tokens
    Documents & OfficeAuto-check: notes
  • Banner Design System

    nextlevelbuilder/ui-ux-pro-max-skill

    Walks through designing a banner for social media, ads, a website hero or print, from gathering requirements to building 2 or 3 art-direction options in HTML and CSS.

    134k GitHub starsUsed in 1 repo~1.8k tokens
    Frontend & DesignAuto-check passed
  • Agent Reach

    Panniantong/Agent-Reach

    Routes web research and platform lookups across 16 sites, including Twitter, Reddit, YouTube, Bilibili, Xiaohongshu and GitHub, through one command-line tool.

    95k GitHub stars~1.4k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated today
    Research & ScienceAuto-check: notes
  • Baoyu URL To Markdown

    sdyckjq-lab/llm-wiki-skill

    Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.

    2.5k GitHub starsUsed in 2 repos~3.2k tokens
    Knowledge ManagementAuto-check passed
  • Google SEO APIs

    AgriciDaniel/claude-seo

    Pulls real Google data for SEO work: Search Console, PageSpeed Insights, CrUX field data, the Indexing API and GA4 organic traffic, through /seo google commands.

    19k GitHub starsUsed in 1 repo~4.2k tokens
    Marketing & SEOAuto-check passed

More from TheCraigHewitt/skills

All 65 skills in this repo
  • Carousels

    TheCraigHewitt/skills

    Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.

    159 GitHub stars~2.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Audience Research

    TheCraigHewitt/skills

    When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Brain Dump

    TheCraigHewitt/skills

    Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.

    159 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Audit

    TheCraigHewitt/skills

    When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Strategy

    TheCraigHewitt/skills

    When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.

    159 GitHub stars~2.2k tokensUpdated 4 mo ago
    Auto-check passed
  • Cold Call

    TheCraigHewitt/skills

    When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.

    159 GitHub stars~5k tokensUpdated 4 mo ago
    Auto-check passed

Works with

Questions about End Screen Cta

What does End Screen Cta do?

When the user wants to optimize YouTube end screens, design CTAs, improve subscriber conversion, or create a next-video strategy. End Screen Cta is an agent skill from TheCraigHewitt/skills. When the user wants to optimize YouTube end screens, design CTAs, improve subscriber conversion, or create a next-video strategy.

When should I use End Screen Cta?

End Screen Cta fits situations like: wants to optimize YouTube end screens; improve subscriber conversion; create a next-video strategy; the user says end screen.

How do I install End Screen Cta in Claude Code?

Run `npx skills add TheCraigHewitt/skills --skill end-screen-cta -a claude-code`. Or copy the skill folder (youtube/end-screen-cta in TheCraigHewitt/skills) into .claude/skills/end-screen-cta in your project. Claude Code loads it when a task matches its description.

How do I install End Screen Cta in Codex?

Run `npx skills add TheCraigHewitt/skills --skill end-screen-cta -a codex`. Or copy the skill folder (youtube/end-screen-cta in TheCraigHewitt/skills) into .agents/skills/end-screen-cta in your project. Codex loads it when a task matches its description.

Can I use End Screen Cta in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill end-screen-cta -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/end-screen-cta, .gemini/skills/end-screen-cta, .github/skills/end-screen-cta and .opencode/skills/end-screen-cta in your project.

What does End Screen Cta need to run?

SKILL.md names no scripts, command-line tools or credentials: End Screen Cta is instructions for the agent only.

Does End Screen Cta access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is End Screen Cta safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does End Screen Cta use?

End Screen Cta is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does End Screen Cta use?

About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to End Screen Cta?

Skills that share tags, products or a category with End Screen Cta: Markitdown (ImCa0/just-laws, 781 stars), Banner Design System (nextlevelbuilder/ui-ux-pro-max-skill, 134k stars), Agent Reach (Panniantong/Agent-Reach, 95k stars) and Last30days (mvanhorn/last30days-skill, 64k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains End Screen Cta?

TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.

Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.