community-orchestration

Community orchestration covering programming, live events, and engagement measurement

View on GitHub
Author GTM Agents
Namespace @gtmagents/gtm-agents
Category orchestration
Version 1.0.0
Stars 64
Downloads 3
self.md verified
Table of content

Community orchestration covering programming, live events, and engagement measurement

Installation

npx claude-plugins install @gtmagents/gtm-agents/community-orchestration

Contents

Folders: agents, commands, skills

Included Skills

This plugin includes 3 skill definitions:

community-ops

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

View skill definition

Community Operations Playbook Skill

When to Use

Framework

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

Templates

Tips


escalation

Use to define incident tiers, response protocols, and stakeholder communications.

View skill definition

Community Escalation Framework Skill

When to Use

Framework

  1. Tiering – classify incidents (info request, policy violation, critical escalation) with examples.
  2. Ownership – map responders per tier (moderators, comms, legal, security, exec sponsor).
  3. Response Playbooks – outline steps, messaging, approvals, and timelines per tier.
  4. Tooling & Evidence – define logging requirements, screenshots, data retention, and ticketing.
  5. Post-incident Review – document root cause, remediation, and preventive actions.

Templates

Tips


sentiment-analysis

Use to interpret qualitative feedback, trends, and risks across community

View skill definition

Community Sentiment Analysis Skill

When to Use

Framework

  1. Signal Sources – forums, chat transcripts, surveys, social listening, support tickets.
  2. Tagging Schema – categorize by emotion, topic, product area, persona, and severity.
  3. Trend Analysis – track frequency over time, correlate with launches or incidents.
  4. Risk Scoring – define thresholds for escalation (negative volume, influencer involvement, compliance).
  5. Action Loop – translate findings into comms responses, content updates, or product feedback tasks.

Templates

Tips


Source

View on GitHub

Tags: orchestration communityengagementadvocacy