external-comms

Draft and post GitHub community responses after mandatory human review.

7|Updated Oct 24, 2020

Search Tags:#workflow #templates #community #auditing #issues #discussions #pao

Ready to run

npx skills add https://github.com/snow-jallen/HomeSpeaker --skill external-comms-snow-jallen

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PAO streamlines the process of monitoring and responding to community questions by drafting responses and routing them through a mandatory human review gate, reducing response time and ensuring quality.

Core Features & Use Cases

Scans open issues and discussions to identify unanswered items across repositories.
Drafts responses using templates and a humanizer, with a built-in human review gate.
Classifies responses into categories such as Welcome, Troubleshooting, Feature Guidance, Redirect, Acknowledgment, Closing, Technical Uncertainty, Empathetic Disagreement, Information Request.
Maintains an auditable trail under .squad/comms/audit and posts only after approval.
Supports manual triggering in Phase 1 and consumption of thread context for accurate replies.

Quick Start

Run PAO to scan open community items and generate draft responses 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 drafting responses for unanswered GitHub Issues and Discussions?▼

Automating community responses for GitHub Issues and Discussions involves scanning open items, classifying response types, and drafting messages with templates. This Skill requires GitHub API access, manual triggering, and a human review gate before posting any approved drafts.

What is the best workflow for ensuring quality control when replying to community questions?▼

A quality workflow for community replies routes drafts through a mandatory human review gate. It classifies messages into categories like Troubleshooting or Acknowledgment, maintains an audit log under .squad/comms/audit, and posts only after explicit human approval.

Can I classify and template community support replies before posting them?▼

Classifying and templating community replies before posting is supported. Responses are categorized into types such as Welcome, Redirect, or Empathetic Disagreement, and drafts are generated using a humanizer-based workflow with templates for human review.

Does this community response workflow require GitHub API access to scan discussions?▼

GitHub API access is required to scan open discussions and issues across repositories. The workflow also requires manual triggering in Phase 1 and maintains an auditable trail under .squad/comms/audit to ensure all actions are tracked before posting.

What categories are available for classifying community responses in a draft workflow?▼

Community responses are classified into categories including Welcome, Troubleshooting, Feature Guidance, Redirect, Acknowledgment, Closing, Technical Uncertainty, Empathetic Disagreement, and Information Request during the drafting process before human review.

Why do I need a human review gate for automated community responses?▼

A human review gate for automated community responses ensures quality control and reduces response time. Drafts are generated using thread context and templates, but an auditor must approve actions before they are posted to the community platform.