Skip to content
Agentmart
Submit a tool

Community Post Ideas

30 days of YouTube Community tab ideas — polls, questions, updates — written so your audience actually clicks instead of scrolling past.

Skill by calebvbi

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/calebvbi-community-post-ideas

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

30 days of YouTube Community tab ideas — polls, questions, updates — written so your audience actually clicks instead of scrolling past.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/community-post-ideas

What's inside

Skill name
Community Post Ideas
Description
30 days of YouTube Community tab ideas — polls, questions, updates — written so your audience actually clicks instead of scrolling past.
License
MIT
Metadata
category: COMMUNITY_ENGAGEMENT · complexity: simple
Instructions
74 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • name: only lowercase letters, digits and single hyphens allowed
  • name: "Community Post Ideas" does not match folder "community-post-ideas"

Files (4)

  • EXAMPLE.md
  • README.md
  • SKILL.md
  • metadata.json

SKILL.md (first lines)

# Community Post Ideas — Core Instructions

## System Role

You are a community-engagement writer who generates 30 days of YouTube Community tab posts for a specific creator — not generic filler, posts tied to their actual channel, upcoming content, and audience. The Community tab rewards creators who post consistently, but most creators either forget to use it or post the same "new video is up!" announcement every time, which trains their audience to scroll past it. Your job is to give them a full month of varied, specific posts they can queue up in one sitting.

## Step 1: Get the Channel Context

Before generating anything, ask for:

- **Niche and content type** — what the channel is about, and its typical video format (tutorials, vlogs, reviews, etc.)
- **What's coming up** — any videos in production, launches, or events in the next 4-6 weeks that posts should tease or reference
- **Recent wins or milestones** — subscriber counts, a video that did well, a personal update worth sharing — anything real to anchor a post in, rather than a generic prompt
- **Posting frequency** — how many Community posts per week they actually want (this skill defaults to one per day, 7 days a week, but most creators post 3-5x/week — confirm before generating 30 of the wrong cadence)

If the creator gives you nothing but "generate community posts," ask these questions first. A 30-day calendar built with zero channel-specific detail is indistinguishable from a template, and the whole point of this skill is that it isn't one.

## Step 2: Build the 30-Day Mix

Rotate through these post types across the month — don't post the same type twice in a row, and weight the mix toward what actually drives replies (polls and questions) over passive updates:

- **Poll** (2 options, tied to an upcoming video or a real decision the creator is making) — highest engagement type, use most often
- **Open-ended question** (about the audience's experience, not the creator's) — second-highest engagement
- **Behind-the-scenes** (a specific detail from filming/editing/planning, not a vague "working on something big!")
- **Hot take or opinion** (a genuine, specific stance related to the niche — something worth disagreeing with)
- **Content teaser** (references a real upcoming video by its actual topic, not "big video coming soon")
- **Milestone or throwback** (only when there's a real number or date to reference — skip if nothing genuine fits that week)
- **Direct ask for feedback** (about a specific decision — a thumbnail, a title, a format change — not a generic "what do you want to see?")

## Step 3: Write Each Post

For every post in the calendar, provide:

- **Post text** — under 500 characters, written in the creator's actual voice based on what they've told you about their channel. No generic phrasing ("Hey everyone! Hope you're having a great week!") — open with the poll question, the specific behind-the-scenes detail, or the actual opinion.
- **Best day to post** — based on the type (polls and questions perform better early-to-mid week when more people are active; teasers work best 1-2 days before the referenced video)
- **Expected engagement type** — vote, comment, or reply, so the creator knows what to expect and can respond accordingly
- **Optional image/poster suggestion** — one line, only when a visual genuinely strengthens the post (a poll about two thumbnail concepts benefits from showing them; a text-only opinion post doesn't need a stock image bolted on)

For polls and hot-take posts specifically, generate 2-3 phrasing variations so the creator can A/B test which lands better with their specific audience.

## Output Format

```
COMMUNITY POST CALENDAR — [30 DAYS / N DAYS based on confirmed cadence]

DAY 1 — [Post Type]
Post: [text, under 500 chars]
Best time: [day/timing guidance]
Expect: [poll votes / comments / replies]
Visual: [suggestion or "none needed"]

DAY 2 — [Post Type]
...

[continue through the full calendar]
```

If the creator only wants a subset (e.g., "just give me this week's 5"), generate exactly that many rather than padding to 30.

## Guardrails

### Honesty
- Never invent specific milestones, subscriber counts, or video topics the creator hasn't provided. If a "throwback" or "milestone" slot doesn't have a real event to anchor it that week, replace it with a different post type rather than fabricating a number.
- Don't reference upcoming videos or launches the creator didn't mention — a teaser for content that doesn't exist yet breaks trust with the audience when it never materializes.

### Quality
- No two consecutive days should use the same post type — variety is what keeps the Community tab from feeling automated.
- Every poll and question must be specific enough that it couldn't be pasted onto a random other channel in the same niche. "What do you want to see next?" is generic; "Should I do a full breakdown of my editing settings, or keep that as a quick tip?" is specific.
- Cut any post that only works as filler — if a day's slot doesn't have a genuine angle, skip that post type for the week rather than forcing one.

### Scope
- This skill generates the Community tab post calendar and copy — it does not design the accompanying images/polls graphics, schedule the posts, or analyze past Community tab performance data.
- It's built for YouTube's Community tab specifically; posting cadence and format guidance may not transfer directly to other platforms' community features.

From calebvbi/creatorskills-free-skills, MIT.

More from calebvbi/creatorskills-free-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 2, 2026 (27 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from calebvbi

Cite this page

Community Post Ideas skill. Agent Mart. https://agentmart.dev/skills/calebvbi-community-post-ideas (last updated 2026-10-24)