From youtube-team-os
Use when building a publish plan, repurposing content, writing community posts, reviewing analytics, or running a postmortem for a completed video. Invoke with /youtube-team-os:growth. Do not use for scripting, editing, or thumbnail work.
How this skill is triggered — by the user, by Claude, or both
Slash command
/youtube-team-os:growthThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Maximize video reach through a structured publish plan, repurposing workflow, community engagement, and analytics capture.
Maximize video reach through a structured publish plan, repurposing workflow, community engagement, and analytics capture.
$ARGUMENTS: project ID, analytics data, or distribution requeststate/roles/growth/inbox.mdstate/projects/<id>/brief.mdstate/projects/<id>/script.mdstate/projects/<id>/thumbnail-options.mdstate/projects/<id>/publish-plan.mdstate/projects/<id>/postmortem.md (at 30-day mark)state/records/analytics-<id>.mdCreate state/projects/<id>/publish-plan.md:
# Publish Plan: <Title>
Project: <id>
Planned publish date: <YYYY-MM-DD HH:MM timezone>
## Upload Checklist
- [ ] Final video file uploaded
- [ ] Thumbnail selected and uploaded (Concept <X> from thumbnail-options.md)
- [ ] Title set: "<chosen title>"
- [ ] Description written (see below)
- [ ] Tags added (see below)
- [ ] End screen configured
- [ ] Cards added (if applicable)
- [ ] Chapters/timestamps added to description
- [ ] Premiere or publish scheduled
## YouTube Description
<Title>
<2–3 sentence hook that mirrors the thumbnail promise>
Chapters:
<paste from edit-notes.md chapter markers>
Links:
- Subscribe: <channel link>
- <Resource 1>: <URL>
<Primary keyword> | <Secondary keyword> | <Category keyword>
## Tags
<tag1>, <tag2>, <tag3>, ... (10–15 total, mix broad and specific)
## Repurposing Plan
| Format | Platform | Key moment | Status |
|---|---|---|---|
| Short (60s) | YouTube Shorts / TikTok / Reels | <timestamp – moment> | pending |
| Quote card | Twitter/X / Instagram | "<pull quote>" | pending |
| Community post | YouTube Community | <teaser question> | pending |
| Email blurb | Newsletter | <one-line value prop> | pending |
## Community Post Draft
<Question or teaser tied to the video's hook, ≤150 words>
## Email Blurb Draft
Subject: <curiosity-gap subject line>
Body: <2–3 sentences, CTA to watch>
For each format in the repurposing plan, draft the copy inline or in a linked note. Shorts/clips should have: hook (first 3 seconds), value delivery, CTA.
Append to state/notes/content-calendar.md:
| <id> | <Title> | <publish date> | PUBLISH |
When called after publishing, create state/records/analytics-<id>.md:
# Analytics Snapshot: <Title>
Project: <id>
Captured: <date> (<N> days after publish)
| Metric | Value | vs. channel avg |
|---|---|---|
| Views (30d) | | |
| CTR | | |
| Avg view duration | | |
| Watch time (hours) | | |
| Subscribers gained | | |
| Comments | | |
| Likes | | |
Create state/projects/<id>/postmortem.md:
# Postmortem: <Title>
Project: <id>
Published: <date>
Reviewed: <date>
## Performance vs. Goals
| Metric | Target | Actual | Delta |
|---|---|---|---|
| Views | | | |
| CTR | | | |
| Retention | | | |
## What Worked
-
## What Didn't
-
## Lessons for Next Video
-
## Channel Learning
<Any finding worth persisting to state/notes/channel-learnings.md>
Append key learnings to state/notes/channel-learnings.md.
Update state/projects/<id>/status.md → Stage: POSTMORTEM → complete.
| Failure | Correction |
|---|---|
| No chapters in description | Pull directly from edit-notes.md; do not skip |
| Repurposing plan left pending | Set a schedule note in state/notes/ |
| Postmortem skipped | Flag in orchestrator weekly planning review |
| Analytics not captured | Note as missing in records; prompt on next session |
npx claudepluginhub boldfacetype/youtube-team-osCreates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.