Community Ops

Use to orchestrate workflows, tooling, and automation for community programs.

Published by @gtmagents·from gtmagents/gtm-agents·0 agent reads / 30d·0 saves·Updated June 14, 2026

Community Operations Playbook Skill

When to Use

Standing up new community channels, automation, or tooling.
Coordinating moderator schedules, onboarding flows, and partner access.
Auditing operations for consistency, compliance, or scale.

Framework

Channel Setup – naming conventions, permissions, integrations, and backup owners.
Workflow Automation – welcome flows, tagging, escalation triggers, and reporting pipelines.
Resource Management – moderator rosters, ambassador kits, and knowledge base updates.
Compliance & Security – access reviews, data retention, legal approvals, and crisis playbooks.
Continuous Improvement – retros, tooling evaluations, and experiment backlog.

Templates

Channel launch checklist (config, automation, QA, analytics hooks).
Moderator shift planner with coverage heatmap.
Automation registry (flow, trigger, owner, status, notes).

Tips

Keep SOPs in a shared workspace with version history.
Pair with escalation skill to ensure automation ties into incident paths.
Review automation logs weekly to catch failures before members notice.

More on the bench

Scriptwriting

Use when crafting scripts, storyboards, and messaging for video content.

marketing-growth-copy+2

Community Advocacy Toolkit

Playbook for activating current students, alumni, and partners as advocates.

sales-gtm-revops+1

Launch

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas.

marketing-growth-copy+2

Sharebench · Public bench

Connect via MCP.

Add the public bench to any AI tool. Your agents read every artifact you see — no signup needed.

1Pick your tool

# Add the public bench as an MCP server
claude mcp add --transport http sharebench-public https://mcp-public.sharebench.ai

# Settings → MCP → Add new MCP server
{
  "mcpServers": {
    "sharebench-public": {
      "url": "https://mcp-public.sharebench.ai"
    }
  }
}

# Custom GPT or Developer Mode
# Add a remote MCP connector with this URL:
https://mcp-public.sharebench.ai

# Append to ~/.codex/config.toml
[mcp_servers.sharebench_public]
url = "https://mcp-public.sharebench.ai"

2Ask your agent for an artifact

Once connected, just ask in plain language — your agent searches the bench and pulls in what it needs.“Pull the brand voice from sharebench and rewrite this draft.”