external-comms

Scan unanswered issues and discussions, draft PAO responses, and queue them for human review.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill external-comms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-comms
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/external-comms
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill external-comms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PAO workflows can be slow or inconsistent when addressing community inquiries. This skill provides a structured process to scan for unanswered issues and discussions, generate draft responses with a humanizer, and route them through a mandatory human review gate with audit logging to ensure quality and policy alignment.

Core Features & Use Cases

  • Unanswered-item scanning: identifies open issues and discussions lacking a squad response.
  • Draft generation with humanizer: creates response drafts while preserving tone, context, and policy constraints.
  • Human review gate & audit logging: requires human validation before posting and records actions for compliance and traceability.

Quick Start

Scan open issues and discussions, draft a response using the humanizer, and queue it 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 community discussions?

To automate drafting responses for unanswered GitHub community discussions, this skill scans open issues and discussions, classifies them, and generates humanized drafts. It ensures policy alignment by queuing drafts for mandatory human review before posting.

What is a human-in-the-loop triage workflow for repository issues?

A human-in-the-loop triage workflow is a process where automated scanning identifies unanswered repository items and drafts responses, but a mandatory human gate validates and approves them. This ensures compliance and maintains tone before any public communication occurs.

Do I need MCP tooling to run the PAO community workflow?

Yes, running the PAO community workflow requires the MCP tooling suite and the PAO workflow rules outlined in RFC #426. These dependencies enable the environment for scanning, drafting, audit logging, and post-approval governance.

How do I audit and track drafted responses for open source community inquiries?

You audit and track drafted responses for community inquiries using built-in audit logging and post-approval governance. This records human review actions and approvals, ensuring full traceability and compliance for every drafted response.

Can I use this workflow to classify and triage GitHub issues at scale?

Yes, you can use this workflow to classify and triage GitHub issues at scale across multiple repositories. It identifies open issues lacking a squad response and applies structured scanning to prepare them for humanized drafting and review.