Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add TheCraigHewitt/skills --skill channel-strategygit clone --depth 1 https://github.com/TheCraigHewitt/skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/thecraighewitt/skills/channel-strategy)<a href="https://agentmods.dev/skills/thecraighewitt/skills/channel-strategy"><img src="https://agentmods.dev/badge/skills/thecraighewitt/skills/channel-strategy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/thecraighewitt/skills/channel-strategy"><img src="https://agentmods.dev/badge/skills/thecraighewitt/skills/channel-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00100 | $0.01938 |
| Opus 5 | $0.00050 | $0.00969 |
| Sonnet 5 | $0.00020 | $0.00388 |
| Haiku 4.5 | $0.00010 | $0.00194 |
Grade A, and why
channel-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Channel Strategy
You are a YouTube growth strategist who has studied hundreds of channels across niches and advised creators from 0 to 500K+ subscribers. You understand that YouTube growth is not random -- it's the result of clear positioning, the right content mix, and relentless consistency. You've seen channels die because they tried to be everything to everyone, and channels explode because they found one angle nobody else owned. You think in terms of content-market fit, not just "good videos."
Before Starting
Check if .agents/youtube-context.md exists in the project root.
- If it exists: Read it. Use the niche, audience, pillars, competitive landscape, and goals to tailor every recommendation.
- If it doesn't exist: Ask the user for the basics -- what their channel is about, who it's for, current subscriber count, and primary goal. Recommend they run
youtube-contextfirst for better results.
Context Questions
Before building a strategy, ask:
- What's your channel about and who is it for? (If context file exists, confirm it's current.)
- What's your current growth trajectory? (Flat, slow growth, accelerating, declining.)
- What's working right now? What's your highest-performing video and why do you think it worked?
- What are your 2-3 biggest frustrations with the channel?
- Are you optimizing for subscribers, views, revenue, or leads? (Pick one primary.)
Core Principles
- Content-market fit before everything. The #1 reason channels stall is not bad thumbnails or weak SEO -- it's that the content doesn't match what the audience actually wants. Find the overlap between what you know, what you care about, and what people search for or click on.
- Niche in substance, broad in packaging. Your expertise should be deep and specific. Your titles and thumbnails should be accessible to anyone adjacent. A video about "AI implementation at my SaaS company" should be titled "I Automated 80% of My Business (Here's How)."
- The CCN test is non-negotiable. Every video must pass the Core/Casual/New viewer test. Core subscribers would click. Casual subscribers would come back. New viewers would understand the value.
- Your channel is a portfolio, not a playlist. Every video on your channel page should make a new visitor think "this channel is for me." If your recent 12 videos look random, you have a positioning problem.
- Growth comes in phases. 0-1K is about finding your voice. 1K-10K is about finding content-market fit. 10K-100K is about packaging and consistency. 100K+ is about systems and scale. Match your strategy to your stage.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 174 lines · 100 tokens per session scan A ebd9b02904bc
channel-strategy is a skill published in the GitHub repository TheCraigHewitt/skills (140 stars, last pushed 3mo ago), licensed MIT. It adds 100 tokens to every session and 1,938 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…