yt-trend
Skill1 starsChanged 37 days agoMITView on GitHub
Plan what to post against the calendar - seasonal demand, recurring events in the niche, and the right mix of timely bets and evergreen library. Use for "what should I post this month", "seasonal content", "what's trending", "content calendar by season", or timing a video to a moment.
In this repository25 other files it gives its agents.
- openai/AGENTS.mdAGENTS.md
- llms.txtllms.txt
- yt-analyticsSkill
- yt-auditSkill
- yt-briefSkill
- yt-chaptersSkill
- yt-collabSkill
- yt-commentSkill
- yt-editSkill
- yt-endscreenSkill
- yt-funnelSkill
- yt-ideaSkill
- yt-packageSkill
- yt-planSkill
- yt-repurposeSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-seoSkill
- yt-seriesSkill
- yt-shortsSkill
- ytSkill
- yt-sponsorSkill
- yt-thumbnailSkill
- yt-viralSkill
- yt-voiceSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
- Distinctive: line 26
Use the available voice profile or creator context (see the operating guide) and the channel's cadence - a trend you cannot film in time is …
- Very specific: line 28
Never claim a trend you have not seen.
- Distinctive: line 33
The recurring calendar: Every niche has dated demand: tax season for finance, new-model launches for tech, new-year for fitness, …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
yt-trend
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
Some videos earn for a week and some earn for years, and posting the wrong kind at the wrong time is how a good idea dies early. This times the calendar: which weeks reward a timely bet, and when to bank evergreen instead.
It does not have a live trends feed. It reasons from the niche's known calendar and pairs with /youtube-agent-pro:yt-viral, which reads what is actually spiking right now. Use both: this plans the shape of the year, /youtube-agent-pro:yt-viral confirms the week.
Before you plan
- Use the available voice profile or creator context (see the operating guide) and the channel's cadence - a trend you cannot film in time is not an opportunity, it is a regret.
- Never claim a trend you have not seen. If the timing rests on a live spike, say "confirm with /youtube-agent-pro:yt-viral first" rather than asserting it.
The two clocks
- The recurring calendar. Every niche has dated demand: tax season for finance, new-model launches for tech, new-year for fitness, back-to-school for education, conference seasons, annual "best X of the year". Map the next 90 days of these for the niche. These are predictable - plan the video weeks ahead, publish just before the search peak, not during it.
- The live spike. A model drops, a thing goes viral, a controversy. These you cannot plan, only react to fast. Decide in advance how much of the schedule is reserved for reaction (usually one slot a month) so a spike does not blow up the whole plan.
The mix
Aim roughly 3 evergreen : 1 timely. Evergreen is the library that earns while you sleep; timely is the wave that brings new viewers to the library. All evergreen and the channel never rides anything; all timely and there is nothing left the week nothing happens.
The move
- Map the niche's recurring dated demand for the next 90 days.
- Slot evergreen anchors on the quiet weeks, timely bets just before each peak.
- Reserve the reaction slot and name the trigger that would use it.
- Pair each timely slot with a "confirm with /youtube-agent-pro:yt-viral" check before shooting.
What to hand back
- a 90-day calendar: evergreen anchors, timely bets, the reserved reaction slot
- for each timely slot, the publish-before date and the search peak it targets
- the evergreen/timely ratio of the plan, stated
- one line: the next dated opportunity and the week to start filming it
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
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.