Index of every page on this site: llms.txt
All skills
sergebulaev avatar

/yt-community-post-writer

@f422cea
Run it yourself

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).

Use this Skill: https://skilld.dev/gh/sergebulaev/youtube-skills/yt-community-post-writer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈134 tokens for metadata: the name and description. ≈1.5k when used: this file. ≈2k more on demand in 3 files.

Description uses 6.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈536 characters, or 6.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill helps YouTube creators write community posts and polls. It includes logic for voice profiling, image generation through internal libraries, and URL parsing. The skill operates with a human-in-the-loop requirement, where all generated content must be reviewed and manually published by the user. No security vulnerabilities were detected.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at f422cea. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago

README badge

README badge for sergebulaev/youtube-skills/yt-community-post-writer