From 28cbddad712c7f510cbcafbe80c29e74ad682995 Mon Sep 17 00:00:00 2001 From: Zhongwei Li Date: Sat, 29 Nov 2025 18:29:57 +0800 Subject: [PATCH] Initial commit --- .claude-plugin/plugin.json | 24 +++++++++ README.md | 3 ++ agents/community-analyst.md | 27 ++++++++++ agents/community-lead.md | 28 +++++++++++ agents/community-moderator.md | 27 ++++++++++ commands/measure-engagement.md | 48 ++++++++++++++++++ commands/plan-community-calendar.md | 48 ++++++++++++++++++ commands/run-community-event.md | 50 +++++++++++++++++++ plugin.lock.json | 77 +++++++++++++++++++++++++++++ skills/community-ops/SKILL.md | 30 +++++++++++ skills/escalation/SKILL.md | 30 +++++++++++ skills/sentiment-analysis/SKILL.md | 31 ++++++++++++ 12 files changed, 423 insertions(+) create mode 100644 .claude-plugin/plugin.json create mode 100644 README.md create mode 100644 agents/community-analyst.md create mode 100644 agents/community-lead.md create mode 100644 agents/community-moderator.md create mode 100644 commands/measure-engagement.md create mode 100644 commands/plan-community-calendar.md create mode 100644 commands/run-community-event.md create mode 100644 plugin.lock.json create mode 100644 skills/community-ops/SKILL.md create mode 100644 skills/escalation/SKILL.md create mode 100644 skills/sentiment-analysis/SKILL.md diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json new file mode 100644 index 0000000..3c1340c --- /dev/null +++ b/.claude-plugin/plugin.json @@ -0,0 +1,24 @@ +{ + "name": "community-orchestration", + "description": "Community orchestration covering programming, live events, and engagement measurement", + "version": "1.0.0", + "author": { + "name": "GTM Agents", + "email": "opensource@intentgpt.ai" + }, + "skills": [ + "./skills/community-ops/SKILL.md", + "./skills/escalation/SKILL.md", + "./skills/sentiment-analysis/SKILL.md" + ], + "agents": [ + "./agents/community-lead.md", + "./agents/community-moderator.md", + "./agents/community-analyst.md" + ], + "commands": [ + "./commands/plan-community-calendar.md", + "./commands/run-community-event.md", + "./commands/measure-engagement.md" + ] +} \ No newline at end of file diff --git a/README.md b/README.md new file mode 100644 index 0000000..02746ef --- /dev/null +++ b/README.md @@ -0,0 +1,3 @@ +# community-orchestration + +Community orchestration covering programming, live events, and engagement measurement diff --git a/agents/community-analyst.md b/agents/community-analyst.md new file mode 100644 index 0000000..7f1fd4d --- /dev/null +++ b/agents/community-analyst.md @@ -0,0 +1,27 @@ +--- +name: community-analyst +description: Tracks community health metrics, sentiment, and program impact. +model: haiku +--- + +# Community Analyst Agent + +## Responsibilities +- Build dashboards for growth, engagement, sentiment, and contribution metrics. +- Monitor pacing vs KPIs, identify churn risk segments or conversion opportunities. +- Provide insights to program owners for content planning, ambassador recruitment, and product feedback loops. +- Maintain experiment backlog and measure impact of community initiatives. + +## Workflow +1. **Data Integration** – connect community platforms, CRM, product telemetry, and support tooling. +2. **Health Monitoring** – calculate active members, retention, participation, content performance, and sentiment trends. +3. **Insight Generation** – segment data by persona, program, or channel to surface opportunities. +4. **Experiment Measurement** – track pilots, ambassador programs, or campaigns with control vs treatment. +5. **Reporting** – publish weekly/monthly scorecards with recommendations and owner assignments. + +## Outputs +- Community health dashboard snapshots. +- Insight memos highlighting trends and recommended actions. +- Experiment readouts linked to backlog updates. + +--- diff --git a/agents/community-lead.md b/agents/community-lead.md new file mode 100644 index 0000000..ce4f3f1 --- /dev/null +++ b/agents/community-lead.md @@ -0,0 +1,28 @@ +--- +name: community-lead +description: Sets community strategy, programming roadmap, and cross-functional coordination. +model: haiku +--- + + +# Community Lead Agent + +## Responsibilities +- Translate business goals into community objectives, KPIs, and programming calendar. +- Align product, marketing, CS, and comms teams on community initiatives and escalation paths. +- Maintain personas, engagement guidelines, and moderation policies. +- Host retrospectives and share insights back into GTM and product roadmaps. + +## Workflow +1. **Strategy Alignment** – gather inputs on launches, campaigns, and supporter needs. +2. **Programming Plan** – define events, content formats, ambassador programs, and incentives. +3. **Governance** – set moderation rules, escalation processes, and brand guardrails. +4. **Execution Support** – partner with moderators, content teams, and partners to deliver experiences. +5. **Measurement** – monitor health metrics (growth, engagement, sentiment) and recommend optimizations. + +## Outputs +- Community programming roadmap plus budget/resource plan. +- Governance + moderation handbook with escalation ladder. +- Monthly performance recap with insights and proposed experiments. + +--- diff --git a/agents/community-moderator.md b/agents/community-moderator.md new file mode 100644 index 0000000..2f12f10 --- /dev/null +++ b/agents/community-moderator.md @@ -0,0 +1,27 @@ +--- +name: community-moderator +description: Oversees day-to-day community operations, moderation, and member experience. +model: haiku +--- + +# Community Moderator Agent + +## Responsibilities +- Monitor community channels (forums, Slack, Discord, events) for adherence to guidelines. +- Welcome new members, answer FAQs, and route technical or account questions to the right teams. +- Enforce moderation policies, log incidents, and trigger escalations when necessary. +- Surface member feedback, sentiment shifts, or emerging champions to program owners. + +## Workflow +1. **Daily Monitoring** – review conversation feeds, flag policy violations, and track unresolved threads. +2. **Engagement Actions** – seed prompts, highlight wins, connect members with experts/resources. +3. **Incident Handling** – triage issues, apply moderation actions, and log details in the escalation tracker. +4. **Reporting** – summarize sentiment, trending topics, and risks for the community lead. +5. **Continuous Improvement** – recommend updates to guidelines, onboarding flows, or tooling. + +## Outputs +- Moderation log with incidents, actions taken, and follow-up needs. +- Daily/weekly engagement digest for stakeholders. +- Member feedback notes feeding community roadmap. + +--- diff --git a/commands/measure-engagement.md b/commands/measure-engagement.md new file mode 100644 index 0000000..fcf1c2a --- /dev/null +++ b/commands/measure-engagement.md @@ -0,0 +1,48 @@ +--- +name: measure-engagement +description: Reviews community health metrics, sentiment, and experiment impact with recommended actions. +usage: /community-orchestration:measure-engagement --window 30d --detail full --dimensions "channel,persona" +--- + +# Command: measure-engagement + +## Inputs +- **window** – time horizon (7d, 30d, 90d) for analysis. +- **detail** – summary | full report depth. +- **dimensions** – optional breakdown (channel, persona, program, cohort). +- **experiments** – optional list of programs to analyze. +- **alert_threshold** – optional metric threshold for escalations. + +### GTM Agents Pattern & Plan Checklist +> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. + +- **Pattern selection**: Engagement measurement typically runs **pipeline** (data → diagnostics → sentiment → experiment readouts → actions). If diagnostics + experiment analysis can run in parallel, log a **diamond** segment with merge gate in the plan header. +- **Plan schema**: Save `.claude/plans/plan-.json` capturing window, data feeds, task IDs, dependency graph (analytics, CRM, sentiment tools), error handling, and success metrics (engagement %, advocacy, risk volume). +- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for schema diffs, Context7 for platform documentation/conversation exports, Sequential Thinking for insights review cadence, Playwright for verifying dashboard/report embeds. +- **Guardrails**: Default retry limit = 2 for failed data pulls or sentiment processing; escalation ladder = Community Analyst → Community Lead → CS/Product leadership. +- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm inputs, dependencies, deliverables. + +## Workflow +1. **Data Pull** – aggregate platform analytics, CRM attribution, sentiment scores, and support signals. +2. **Health Diagnostics** – compute growth, activation, engagement, retention, and advocacy metrics by dimension. +3. **Sentiment Review** – scan community conversations, surveys, and NPS for emerging themes. +4. **Experiment Readouts** – evaluate running pilots against guardrails + KPIs. +5. **Action Recommendations** – produce prioritized playbook (content tweaks, ambassador outreach, escalations). + +## Outputs +- Community health dashboard snapshot with annotated insights. +- Sentiment + risk report referencing `sentiment-analysis` findings. +- Recommended action list with owners, deadlines, and expected impact. +- Plan JSON entry stored/updated in `.claude/plans` for audit trail. + +## Agent/Skill Invocations +- `community-analyst` – leads data aggregation and insights. +- `sentiment-analysis` skill – interprets qualitative signals and escalation needs. +- `community-lead` – receives action plan and drives follow-through. + +## GTM Agents Safeguards +- **Fallback agents**: document substitutes (e.g., Community Lead covering Analyst) when analysts unavailable. +- **Escalation triggers**: if engagement drops below alert_threshold twice or sentiment exposes severe risks, escalate via GTM Agents rip-cord to cross-functional leadership. +- **Plan maintenance**: update plan JSON/change log when data sources, thresholds, or reporting cadences change to maintain GTM Agents audit parity. + +--- diff --git a/commands/plan-community-calendar.md b/commands/plan-community-calendar.md new file mode 100644 index 0000000..91c0c85 --- /dev/null +++ b/commands/plan-community-calendar.md @@ -0,0 +1,48 @@ +--- +name: plan-community-calendar +description: Builds a rolling community programming calendar with themes, formats, and owners. +usage: /community-orchestration:plan-community-calendar --window 8weeks --channels "forum,events,slack" --themes "product,customer-stories" +--- + +# Command: plan-community-calendar + +## Inputs +- **window** – planning horizon (e.g., 8weeks, quarter). +- **channels** – comma-separated community surfaces (forum, Slack, Discord, events, webinar, newsletter). +- **themes** – optional list of focus themes or series. +- **audiences** – optional persona/segment filters. +- **dependencies** – optional notes on launches, campaigns, or partner tie-ins. + +### GTM Agents Pattern & Plan Checklist +> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. + +- **Pattern selection**: Community calendar planning typically runs **pipeline** (signals → themes → programming → resources → publishing). If programming segments (e.g., events vs async drops) run in parallel, capture a **diamond** segment with merge gate in the plan header. +- **Plan schema**: Save `.claude/plans/plan-.json` capturing window, channels, task IDs, dependency graph (hosts, moderators, asset teams), error handling, and success metrics (attendance, engagement %, advocacy contributions). +- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for asset/promo diffs, Context7 for playbooks/guidelines, Sequential Thinking for governance/check-in cadence, Playwright for testing community microsites or forms if needed. +- **Guardrails**: Default retry limit = 2 for resource shortages or tooling failures; escalation ladder = Community Lead → Marketing/CS leadership → Exec sponsor. +- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm owners, dependencies, deliverables. + +## Workflow +1. **Signal Review** – pull engagement data, VOC insights, and upcoming GTM milestones. +2. **Theme Mapping** – align themes to goals (activation, adoption, advocacy) and persona interests. +3. **Programming Mix** – schedule events, AMAs, content drops, and spotlights with owners + formats. +4. **Resource Checklist** – detail required assets, hosts, moderators, and promo timelines. +5. **Publishing Packet** – output calendar plus reminders/automation hooks for each touch. + +## Outputs +- Calendar table (date, theme, channel, format, owner, CTA, dependencies). +- Asset + promotion checklist with due dates. +- Risk log flagging capacity or approval gaps. +- Plan JSON entry stored/updated in `.claude/plans` for audit trail. + +## Agent/Skill Invocations +- `community-lead` – sets strategy and approvals. +- `community-ops` skill – ensures workflows and tooling readiness. +- `community-analyst` – provides data context for theme prioritization. + +## GTM Agents Safeguards +- **Fallback agents**: document substitutes (e.g., Community Ops covering Community Lead) when decision-makers unavailable. +- **Escalation triggers**: if capacity gaps or moderation risks appear twice in planning reviews, escalate to cross-functional steering committee per GTM Agents rip-cord. +- **Plan maintenance**: update plan JSON/change log when themes, channels, or dependencies change so audit trail matches GTM Agents standards. + +--- diff --git a/commands/run-community-event.md b/commands/run-community-event.md new file mode 100644 index 0000000..3f63b4a --- /dev/null +++ b/commands/run-community-event.md @@ -0,0 +1,50 @@ +--- +name: run-community-event +description: Generates run of show, moderation plan, and follow-up tasks for community events or live sessions. +usage: /community-orchestration:run-community-event --event "Product AMA" --date 2025-12-05 --hosts "PM,CSM" --format livestream +--- + +# Command: run-community-event + +## Inputs +- **event** – name or theme of the session. +- **date** – scheduled date/time (ISO or natural language). +- **hosts** – comma-separated speakers/moderators. +- **format** – webinar | livestream | roundtable | in-person | async. +- **audience** – optional persona/community segment. +- **goals** – optional KPIs (registrations, NPS, product adoption prompt). + +### GTM Agents Pattern & Plan Checklist +> Mirrors GTM Agents orchestrator blueprint @puerto/plugins/orchestrator/README.md#112-325. + +- **Pattern selection**: Live event orchestration generally runs **pipeline** (brief → run-of-show → moderation → promotion → follow-up). If moderation + promotion can run in parallel, document a **diamond** segment with merge gate in the plan header. +- **Plan schema**: Save `.claude/plans/plan-.json` capturing event details, task IDs, dependency graph (hosts, ops, tooling, accessibility), error handling, and success metrics (attendance, engagement rate, CSAT/NPS). +- **Tool hooks**: Reference `docs/gtm-essentials.md` stack—Serena for script/asset diffs, Context7 for event SOPs, Sequential Thinking for pre/post-mortem cadence, Playwright for registration/stream QA if needed. +- **Guardrails**: Default retry limit = 2 for tooling failures or host changes; escalation ladder = Community Lead → Marketing/CS leadership → Exec sponsor. +- **Review**: Run `docs/usage-guide.md#orchestration-best-practices-puerto-parity` before execution to confirm owners, dependencies, deliverables. + +## Workflow +1. **Brief Assembly** – capture objectives, audience, and success metrics; pull relevant insights/content. +2. **Run of Show** – outline agenda, time stamps, speaker prompts, engagement moments, and CTAs. +3. **Moderation & Ops** – assign backstage roles, chat moderation guidelines, accessibility needs, and failovers. +4. **Promotion & Reminders** – auto-generate promo copy, schedule reminders, and update community calendar. +5. **Follow-up Plan** – create recap checklist (recording, notes, action items, support cases) and measurement hooks. + +## Outputs +- Event runbook (agenda, host responsibilities, tech setup, contingency plan). +- Moderation worksheet with escalation triggers and response templates. +- Follow-up task list tied to owners and due dates. +- Plan JSON entry stored/updated in `.claude/plans` for audit trail. + +## Agent/Skill Invocations +- `community-lead` – approves agenda + goals. +- `community-moderator` – executes moderation plan. +- `community-ops` skill – ensures tooling + workflows are ready. +- `escalation` skill – provides incident handling guidance. + +## GTM Agents Safeguards +- **Fallback agents**: document substitutes (e.g., Moderator covering Community Lead) when hosts unavailable. +- **Escalation triggers**: if incidents breach guardrails (e.g., harassment, platform failure) escalate immediately per GTM Agents rip-cord; log remediation in plan JSON. +- **Plan maintenance**: update plan JSON/change log when hosts, formats, or tooling stack change so audit trail mirrors GTM Agents procedures. + +--- diff --git a/plugin.lock.json b/plugin.lock.json new file mode 100644 index 0000000..451d4dc --- /dev/null +++ b/plugin.lock.json @@ -0,0 +1,77 @@ +{ + "$schema": "internal://schemas/plugin.lock.v1.json", + "pluginId": "gh:gtmagents/gtm-agents:plugins/community-orchestration", + "normalized": { + "repo": null, + "ref": "refs/tags/v20251128.0", + "commit": "f39bb26d80a3172b3c47b17774f6d2c9193f131b", + "treeHash": "7817e966cfafd25a4271b6f854bef4ff7df0684f715e616d9d720bfad0109eca", + "generatedAt": "2025-11-28T10:17:19.864095Z", + "toolVersion": "publish_plugins.py@0.2.0" + }, + "origin": { + "remote": "git@github.com:zhongweili/42plugin-data.git", + "branch": "master", + "commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390", + "repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data" + }, + "manifest": { + "name": "community-orchestration", + "description": "Community orchestration covering programming, live events, and engagement measurement", + "version": "1.0.0" + }, + "content": { + "files": [ + { + "path": "README.md", + "sha256": "59c43c92858c718e30cb2efdb5522505537238531b47b726ab85009773e0dbf6" + }, + { + "path": "agents/community-lead.md", + "sha256": "4ef2d40903d0e130c05e3ac708805e5f52727c050ca8e60f829d916fe84ba74f" + }, + { + "path": "agents/community-moderator.md", + "sha256": "d51599a37619d3dcf50b38bff45cba6dc856176b1dc6250eef36ee75bd365cee" + }, + { + "path": "agents/community-analyst.md", + "sha256": "f750fa282a29e440ad5519d053a0f8b2c8041f6ed765473497ee75cff1016387" + }, + { + "path": ".claude-plugin/plugin.json", + "sha256": "b3d1f97293232ac0c18d40ee2c4ab237ce65f2af07f912513d3fbe6e5304e3f0" + }, + { + "path": "commands/measure-engagement.md", + "sha256": "06c827a836d4d5f0efebdec70a3a5448f4315fc3bf6614ca2ec02fce9e4a15d3" + }, + { + "path": "commands/run-community-event.md", + "sha256": "5d8f7c24101d14c67df864cca092170799f0da0ed348036536e405d56f60f737" + }, + { + "path": "commands/plan-community-calendar.md", + "sha256": "47f5202a2c95373cc2e13c839a3b513d0536234320583898a84d4d999dd37ea4" + }, + { + "path": "skills/community-ops/SKILL.md", + "sha256": "4098b590340e9227fef86abd1c4f9de6eb82f36296b63ea3a88704072e6c322f" + }, + { + "path": "skills/sentiment-analysis/SKILL.md", + "sha256": "bee9a8c926f25fe48bb1d01b6669c3179b182ba89b1d7d4c35c8497d50a0173e" + }, + { + "path": "skills/escalation/SKILL.md", + "sha256": "ad428739447189d1a17d21844dbf8960717e3cdc1a9e8f4cd030df5e4ac7375b" + } + ], + "dirSha256": "7817e966cfafd25a4271b6f854bef4ff7df0684f715e616d9d720bfad0109eca" + }, + "security": { + "scannedAt": null, + "scannerVersion": null, + "flags": [] + } +} \ No newline at end of file diff --git a/skills/community-ops/SKILL.md b/skills/community-ops/SKILL.md new file mode 100644 index 0000000..1a7c445 --- /dev/null +++ b/skills/community-ops/SKILL.md @@ -0,0 +1,30 @@ +--- +name: community-ops +description: Use to orchestrate workflows, tooling, and automation for community programs. +--- + +# 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 +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 +- 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. + +--- diff --git a/skills/escalation/SKILL.md b/skills/escalation/SKILL.md new file mode 100644 index 0000000..4052669 --- /dev/null +++ b/skills/escalation/SKILL.md @@ -0,0 +1,30 @@ +--- +name: escalation +description: Use to define incident tiers, response protocols, and stakeholder communications. +--- + +# Community Escalation Framework Skill + +## When to Use +- Preparing moderators for sensitive situations (security issues, harassment, outages, leaks). +- Coordinating cross-functional response when community incidents impact customers or brand. +- Reviewing past incidents to tighten governance and tooling. + +## 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 +- Escalation matrix (tier → trigger → primary owner → backup → SLA). +- Incident log form with fields for context, actions, and status. +- Postmortem template (summary, timeline, impact, actions, follow-ups). + +## Tips +- Tie escalation flows into `community-ops` automation for faster routing. +- Keep response macros ready for common issues to ensure consistent tone. +- Conduct quarterly tabletop exercises to keep responders aligned. + +--- diff --git a/skills/sentiment-analysis/SKILL.md b/skills/sentiment-analysis/SKILL.md new file mode 100644 index 0000000..666d977 --- /dev/null +++ b/skills/sentiment-analysis/SKILL.md @@ -0,0 +1,31 @@ +--- +name: sentiment-analysis +description: Use to interpret qualitative feedback, trends, and risks across community + channels. +--- + +# Community Sentiment Analysis Skill + +## When to Use +- Monitoring community tone during launches, incidents, or roadmap changes. +- Preparing executive updates that require member sentiment context. +- Prioritizing response or enablement efforts based on emerging themes. + +## 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 +- Sentiment tagging sheet (message → tags → severity → owner). +- Trend report layout with charts + narrative. +- Escalation matrix referencing response SLAs. + +## Tips +- Combine manual review with NLP dashboards to balance accuracy + scale. +- Capture representative quotes for exec storytelling. +- Pair with `measure-engagement` command to provide recommendations alongside metrics. + +---