Help us improve
Share bugs, ideas, or general feedback.
From creator-stack
Orchestrates YouTube community post creation using research and write skills, handling episode context, lifecycle phases for video promotion, polls, and audience engagement.
npx claudepluginhub kenneth-liao/ai-launchpad-marketplace --plugin creator-stackHow this skill is triggered — by the user, by Claude, or both
Slash command
/creator-stack:community-postThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This orchestrator creates YouTube community posts by sequencing `creator-stack:research` for strategic context and `creator-stack:write` for content generation. It handles episode awareness, post type selection, and output management — all actual content generation and strategy are delegated to the foundation skills.
Generates YouTube Community tab posts that promote uploads, tease content, or spark conversation, matched to the channel's voice.
Repurposes completed YouTube videos into newsletters, Twitter threads, LinkedIn posts, and Substack Notes using episode research, plans, and transcripts. Invoke for content distribution workflows.
Guides users through a structured, iterative process to create detailed YouTube video briefs step-by-step, with suggestions, decisions, and locks before scripting.
Share bugs, ideas, or general feedback.
This orchestrator creates YouTube community posts by sequencing creator-stack:research for strategic context and creator-stack:write for content generation. It handles episode awareness, post type selection, and output management — all actual content generation and strategy are delegated to the foundation skills.
Core Principle: This is a thin orchestrator. Strategy lives in creator-stack:research (via its references/youtube-community-strategy.md). Templates and formatting live in creator-stack:write (via its references/youtube-community-post.md). This skill manages the workflow sequence, episode context, and user decisions only.
Both foundation skills own their own reference files. When you invoke creator-stack:research and specify "youtube community post" as context, it loads its strategy reference. When you invoke creator-stack:write with content type "youtube community post", it loads its template reference. Those files live in each skill's directory, not here.
Use this skill when:
Optional: An episode directory at ./youtube/episode/[episode_number]_[topic_short_name]/ with a plan.md file. This is only needed for video-linked posts (pre-release, launch day, post-launch). Between-video engagement posts do not require an episode directory.
Execute all steps below in order.
Check if the user has specified an episode or if an episode directory exists at ./youtube/episode/[episode_number]_[topic_short_name]/.
If episode directory exists:
plan.md for video title, topic, and contextIf no episode directory:
Invoke creator-stack:research with the community post context to determine strategy.
Provide:
The research skill applies the strategy framework to determine:
NOTE: This is a lighter research invocation — asking research to apply the strategy framework to the user's context, not to do full competitor analysis.
Based on the research output, present the ranked post type options to the user:
Include the research skill's recommendation for which type best fits the context. User selects their preferred type.
Default to polls when unsure — they have the lowest friction and highest engagement.
Invoke creator-stack:write with content type "youtube community post" to draft the post.
Provide:
The writing skill automatically invokes creator-stack:voice for voice consistency. Its reference file contains all templates, formatting rules, and the 288-character hook rule.
Verify the drafted post against all eight criteria before presenting to the user:
If any criterion fails, request a revision from creator-stack:write before presenting to the user.
Present the final post to the user for approval.
If episode directory exists:
./youtube/episode/[episode_number]_[topic_short_name]/community-posts.mdIf no episode directory:
When saving to community-posts.md, use this structure:
# Community Posts - Episode [Number]: [Topic]
## [Phase] Post - [Date]
**Type:** [Poll / Teaser / GIF / Image / Quiz / Text]
**Phase:** [Pre-release / Launch Day / Post-Launch / Between Videos]
**Goal:** [Engagement / Promotion / Research / Conversion]
### Post Content
[Final post text]
### Notes
- Suggested timing: [from research]
- CTA type: [question / poll / link]
Multiple posts for the same episode are appended to the same file with a horizontal rule separator (---) between entries.
Verify completion before finalizing:
creator-stack:research invoked — strategic context determinedcreator-stack:write invoked — post draftedreferences/youtube-community-post.md — don't duplicate them here.references/youtube-community-strategy.md — don't hardcode timing, cadence, or algorithm advice here.