---
name: yt-community-post-writer
description: "Write YouTube community-tab posts: text updates, polls, image-caption posts, and questions that drive comments and bring subscribers back between video uploads. Tuned to the community tab's role as a low-friction touchpoint that keeps a channel warm and feeds session signals. Returns a copy-paste block (community posts have no publishing API, so this is always manual by design). Use to write a community post or poll. Not for video titles or descriptions (use yt-title-optimizer and yt-description-writer)."
title: yt-community-post-writer
canonical_url: https://skilld.dev/gh/sergebulaev/youtube-skills/yt-community-post-writer
last_updated: 2026-10-29T10:46:08.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/post-types.md](https://skilld.dev/api/skills-raw/sergebulaev/youtube-skills/yt-community-post-writer/references/post-types.md), [sub-skills/illustration.md](https://skilld.dev/api/skills-raw/sergebulaev/youtube-skills/yt-community-post-writer/sub-skills/illustration.md), [sub-skills/voice-profile.md](https://skilld.dev/api/skills-raw/sergebulaev/youtube-skills/yt-community-post-writer/sub-skills/voice-profile.md).
>
> If the user asked to install this Skill, run `npx skilld install sergebulaev/youtube-skills/yt-community-post-writer`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/yt-community-post-writer`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/sergebulaev/youtube-skills/yt-community-post-writer) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/yt-community-post-writer`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/yt-community-post-writer --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/yt-community-post-writer --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# YouTube Community Post Writer

The community tab is the channel's between-uploads touchpoint. A good post keeps
subscribers engaged, seeds comments, and warms the audience for the next video.
This skill writes those posts and polls.

## When to use

- User says "write a community post" or "make a poll for my channel"
- User wants to tease, build hype for, or follow up on a video
- User wants to keep the channel active between uploads
- User wants a poll to source ideas or settle a debate with the audience

## Why this is always copy-paste

YouTube community posts and polls have **no Publora endpoint and no public
publishing API**. So this skill always returns a finished post as a copy-paste
block for you to publish in the Community tab yourself. That is by design, not a
limitation of the draft tier. (Videos and Shorts do auto-upload through Publora.)

## Post types this skill writes

| Type | Best for |
|---|---|
| **Text update** | a quick thought, a tease, a behind-the-scenes note |
| **Poll** | sourcing ideas, settling a debate, low-effort engagement |
| **Image + caption** | a teaser frame, a before/after, a result screenshot |
| **Question prompt** | a direct ask that fills the comments |

## Steps

**Never invent the specifics.** The rules below ask for a concrete number, a date and a named entity, because that is what separates a real post from a generated one. Take them from what the user actually said in this conversation. **Do not invent a figure, a date, a client name or a result, and do not soften a vague claim into a plausible-looking number.** If the user has nothing concrete for a beat, ask them once, and if they still have nothing, drop the claim rather than decorate it. A published invented number is a retraction; a missing one is only a weaker post.

1. **Gather inputs, goal first.** Ask (or infer) what the post should earn
   before picking a format, then map goal to format: tease a video -> image or
   text teaser with a curiosity gap; source ideas / decide content -> poll;
   follow up on a video -> text post replying to top comments; keep warm
   between uploads -> behind-the-scenes image or quiz. Then gather the topic,
   the channel's voice, and confirm the post type fits the goal. If the post relates
   to a specific video, take the URL and parse it with `lib/url_parser.py`.
2. **Pick the type.** A poll for input or low-effort engagement; a text update
   for a tease or note; an image caption for a visual teaser; a question to drive
   comments.
3. **Write the post.**
   - Lead with the hook; the first line carries it (the community feed truncates).
   - One clear ask: vote, comment a specific thing, or watch the linked video.
   - For a poll: a clear question plus 2 to 4 tight options. No false dilemmas.
   - Keep it short. The community tab rewards low-friction, not essays.
4. **Humanizer pass.** Scrub 2026 AI vocabulary by density (one marker such as
   "leverage" or "significant" is fine; three in one post means rewrite the
   post), cap em dashes (a community post is short, so at most one, never
   swapped for a period), break stacked or hollow rule-of-three, strip reveal
   bridges ("The result?", "Here's what") and sincerity openers ("not gonna
   lie", "let me be honest"). Never add a hedge or a confession the creator did
   not write. Sound like the creator, not a brand account.
5. **Approval card.** Show the post (and poll options) and the target Community
   tab URL.
6. **On approval.** Call `lib.publish(kind="community", draft_text=<post>,
   target_url=<community tab url>)`. The wrapper returns the copy-paste block;
   the user posts it in the Community tab.

## Hard rules

Global voice rules: see root `SKILL.md` Voice rules. Additional skill-specific
rules:

- The first line carries the hook (the community feed truncates long posts).
- One clear ask per post. Two asks split the response.
- Polls: 2 to 4 options, mutually exclusive, no loaded framing.
- Keep it short. A community post is a touchpoint, not a blog.
- No engagement bait ("comment 1 for yes"); ask a real question.

## Anti-patterns (skill will refuse)

- A wall of text where the community tab wants one or two lines.
- Two competing asks in one post.
- A poll with a false dilemma or 6+ options.
- Engagement bait ("like if you agree, comment if you don't").
- More than one em dash in a post, or an em dash swapped for a period.
- Announced candor ("let me be honest", "not gonna lie") with no dated fact behind it.
- "Don't forget to smash subscribe" dead phrasing.

## Resources

- `../../references/voice-rules.md` - the canonical voice rules
- `../../references/algorithm-heuristics.md` - comments and session signals
- `references/post-types.md` - templates for each community post type

## Voice profile mode (`--mode profile`)

`yt-community-post-writer --mode profile` builds or updates the user's Voice & Brand Profile at `../../references/voice-profile.md` from 3-6 of their real YouTube posts pasted in (portable, no token) or, if a read token is set, from pulled activity. Once filled, every writing skill in this bundle drafts in the user's voice automatically. See `sub-skills/voice-profile.md`. Triggers: "build my voice profile", "learn my voice".

## Optional illustration

Offer a generated image when a visual would lift reach. Draft a prompt and call
`lib.illustrate(prompt, kind="thumbnail")`, pulling brand handle/color from Voice &
Brand Profile section 6 for a pixel-exact overlay. Show the returned `url` + `cost`,
the community tab has no media API, so upload the approved image yourself with the post (it cannot be auto-attached). Full workflow (incl. quote-cards):
`sub-skills/illustration.md`. No Pixfaro key -> it drafts the prompt for you to generate manually.
## Related skills

- `yt-content-planner` - schedule community posts between uploads
- `yt-title-optimizer` - when the post is teasing a specific video
