external-comms

Name: external-comms
Availability: InStock
Author: Quaid

Scan GitHub issues and discussions, draft responses, and require human review before posting.

3|3|Updated Apr 13, 2026

Search Tags:#github #issue-triage #community-management #human-review #pao #communication-workflow

Ready to run

npx skills add https://github.com/quaid-app/quaid --skill external-comms-quaid-app

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the workflow for external communications by scanning community items, drafting responses, and routing them through a mandatory human review gate to protect organizational voice and prevent missteps.

Core Features & Use Cases

Scan open issues and discussions to identify candidates for community responses.
Draft responses using a humanizer pattern and present them for human approval.
Maintain an audit log of all actions and ensure posts go through a review gate before posting.
Patterns guide for classification, triage, and posting decisions across community threads.

Quick Start

Run the PAO external communications workflow to scan recent issues and prepare 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 GitHub issue responses for community management?▼

Automating GitHub issue responses involves scanning open issues, generating draft replies using a humanizer pattern, and routing them through a mandatory human review gate before posting to protect organizational voice.

What is a human review gate in external communication workflows?▼

A human review gate in external communication workflows is a mandatory approval step where drafted responses to community issues must be reviewed and approved by a person before posting, preventing missteps and maintaining an audit log.

How do I triage open GitHub discussions to find candidates for community replies?▼

Triageing GitHub discussions for community replies uses automated scanning to identify suitable candidate threads, applying classification patterns to select issues for drafting responses with a humanizer before human review.

Can I use GitHub MCP tools and GH CLI to post automated community responses?▼

Yes, external communication workflows rely on GitHub MCP tools and the GH CLI to read issues, draft candidate responses, and post them, but only after the drafts successfully pass the mandatory human review gate.

Does automated issue triage work for both open-source projects and internal teams?▼

Automated issue triage and communication workflows apply to both open-source projects and internal teams, scanning issues and discussions, drafting responses, and enforcing a human review gate prior to posting.

What are the limitations of automating external community responses on GitHub?▼

The primary limitation is the strict human review gate; no drafted response posts automatically, meaning a human must always review and approve the communication workflow output to maintain organizational voice.