external-comms

Draft and review community responses with human approval before posting.

2|3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/sytone/botnexus --skill external-comms-sytone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-comms
Source: https://github.com/sytone/botnexus/tree/main/.copilot/skills/external-comms
Command: npx skills add https://github.com/sytone/botnexus --skill external-comms-sytone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PAO external communications workflow helps teams draft, triage, and publish community responses with a mandatory human review gate to prevent automated miscommunication.

Core Features & Use Cases

  • Scan and triage unanswered issues and discussions using MCP-style templates and a human-in-the-loop workflow.
  • Classify responses into Welcome, Troubleshooting, Feature Guidance, Redirect, Acknowledgment, or Information Request, with structured templates.
  • Maintain audit trails and allow manual posting via CLI or API, with an opt-in for human review before publication.

Quick Start

Provide a guardrailed response draft using the PAO workflow to prepare a reply for a new community discussion.

Frequently Asked Questions about external-comms

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

FAQPage Schema
How do I draft community responses with a mandatory human review gate?

External communications workflows draft community responses by scanning open issues, classifying them into structured templates, and routing drafts for mandatory human approval before posting. This prevents automated miscommunication by ensuring a human reviews every reply.

What is the best way to triage unanswered GitHub issues and discussions for external reply?

The best way to triage unanswered GitHub issues for external reply is to scan open items, classify responses into categories like Troubleshooting or Redirect, and apply structured templates. This workflow automates scanning and classification while maintaining an audit trail for manual posting.

Can I classify community support requests into structured response categories?

Yes, you can classify community support requests into structured categories. The workflow supports classifying responses into Welcome, Troubleshooting, Feature Guidance, Redirect, Acknowledgment, or Information Request, applying structured templates to ensure consistent community replies.

How do I audit external communications and maintain a trail of community response drafts?

You audit external communications by leveraging the workflow's built-in audit trail functionality. It logs the drafting, triage, and manual posting processes for community responses, maintaining a comprehensive record of all external communications and human review approvals.

Does this external communications workflow support manual posting via CLI or API?

Yes, the external communications workflow supports manual posting via CLI or API. It maintains audit trails and allows an opt-in for human review before publication, ensuring automated drafts are never posted without explicit manual approval and oversight.

When do I need a human-in-the-loop workflow for community responses?

You need a human-in-the-loop workflow for community responses when preventing automated miscommunication is critical. This workflow applies manual activation, structured templates, and a mandatory human review gate to safely draft, triage, and publish replies to open issues and discussions.