external-comms

Scan GitHub issues and discussions to draft responses for human review.

49|6|Updated Aug 24, 2021

Search Tags:#workflow #community #auditing #issues #discussions #human-review #pao

Ready to run

npx skills add https://github.com/webmaxru/bpm-counter --skill external-comms-webmaxru

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: external-comms
Source: https://github.com/webmaxru/bpm-counter/tree/main/.copilot/skills/external-comms
Command: npx skills add https://github.com/webmaxru/bpm-counter --skill external-comms-webmaxru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PAO scans issues and discussions, drafts responses with the humanizer skill, and presents a review table for human approval. The human review gate is mandatory — PAO never posts autonomously. Every action is logged to .squad/comms/audit/ and activation is manual.

Core Features & Use Cases

Scan open issues and discussions to identify unanswered items for potential responses.
Draft responses with the humanizer skill and present a review table for human approval.
Post-approval, PAO supports posting through the appropriate GitHub APIs and logs actions for auditing.

Quick Start

Trigger the external-comms workflow to scan open issues and discussions, draft responses, and queue them for human review.

Frequently Asked Questions about external-comms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate scanning GitHub issues and discussions for unanswered community replies?▼

Automating community replies is done by manually triggering a workflow that scans open GitHub issues and discussions to identify unanswered items, drafts responses, and queues them for human review before posting. All actions are logged for auditing.

Does the community reply workflow post responses to GitHub automatically without human review?▼

No, human review is mandatory and the workflow never posts autonomously. It drafts responses and presents a review table for human approval, supporting posting through GitHub APIs only after approval is granted.

How do I audit community engagement actions on GitHub issues and discussions?▼

Auditing community engagement is handled by logging every workflow action to a designated audit directory. This ensures controlled, auditable tracking of all drafted and posted replies across repositories.

Can I use this workflow to manage community engagement across multiple GitHub repositories?▼

Yes, the workflow applies to open issues and discussions across repositories. It scans them to find candidate items for responses and supports posting through the appropriate GitHub APIs after human approval.

What's the best way to draft humanized responses for open GitHub discussions?▼

Drafting humanized responses is achieved through the workflow's integrated humanizer skill. It processes candidate items from open discussions, drafts replies, and presents them in a review table for mandatory human approval before posting.